Hi!
I want to suggest a feature to export more information about node - not only node itself but links to related nodes too. In this case separately exported node doesn't become orphan, but it's possible to restore the whole book starting from this node.
It can be very useful for exporting pages for reading on non-browser devices: specific applications for PDAs may be flash readers.
I can develop code and necessary changes to xml schema.
Dxml file may look like:
<?xml version='1.0'?>
<!DOCTYPE book PUBLIC "-//Drupal//DTD DXML V1.0//EN" "http://drupal.org/xml/dxml.dtd">
<node id="node-9">
<nodeinfo md5_body="7061a9387f3f08a8543d7e9e9f8798e1" weight="0" depth="2" type="book" author="admin" uid="1" created="1193920531" changed="1194433788" status="1" format="3" sticky="0" promote="1"/>
<title>The page title</title>
<teaser>The teaser</teaser>
<content> Page content </content>
<navigation>
<link rel="prev" href="/book/export/dxml/8">Chapter 8</link>
<link rel="up" href="/book/export/dxml/5"> Chapter 5</link>
<link rel="next" href="/book/export/dxml/10">Chapter 10</link>
</navigation>
<links>
<link href="/book/export/dxml/10">Chapter 10</link>
<link href="/book/export/dxml/11">Chapter 11</link>
<link href="/book/export/dxml/12">Chapter 12</link>
....
<links>
</node>
Really it is standard book navigation transcripted to XML.
Another way is to use xlink for marking this links. I think whats better?
First is simpler but second is more standard.
Yours,
Eugene
Comments
Comment #1
nancydruWould this potentially break anything? How would it impact the Import side of this?