Changes between Version 6 and Version 7 of SophieFormat

Timestamp:

11/07/09 18:12:07 (16 years ago)

Author:

mira

Comment:

--

SophieFormat

@@ -17 +17 @@
   Cool Book
 </title>
-}}}[[BR]] [[BR]]
- * There could be a child ‘template’ that contains a reference to another resource. It is saved like this: [[BR]] 
+}}}
+There could be a child ‘template’ that contains a reference to another resource. It is saved like this: [[BR]] 
 {{{
 <template>
   <ref location="../Resource Jd88Us"/>
 </template>
-}}} [[BR]] [[BR]]
+}}} 
 This means that the referenced resource is located in the parent directory of the current one and is called “Resource Jd88Us”. Notice that this is the actual name of the resource, not its title. [[BR]] 
- * There could be a ‘comment’ child that has a string value. [[BR]] [[BR]]
- * There could be an ‘import-origin’child that has a string value. It represents the URI of the import origin of this resource. [[BR]] [[BR]]
+There could be a ‘comment’ child that has a string value. [[BR]] [[BR]]
+There could be an ‘import-origin’child that has a string value. It represents the URI of the import origin of this resource. [[BR]] [[BR]]
 Those children nodes are common for all resources. Most of them are not mandatory, though. So the ‘resource’ node could have some or all of them. When a property`s value is null there is no point in having empty tags for it. [[BR]] [[BR]]
-There are many other children nodes that could be found in a _resource.xml depending on the kind of the persisted resource. Here we are presented most of them specifying where you could see them. Basically all properties of a resource are saved in this xml file in appropriate form depending on the type of the kept value. [[BR]] [[BR]]
+ * There are many other children nodes that could be found in a _resource.xml depending on the kind of the persisted resource. Here we are presented most of them specifying where you could see them. Basically all properties of a resource are saved in this xml file in appropriate form depending on the type of the kept value. [[BR]] [[BR]]
 When the persisted resource is a book its _resource.xml could have ‘page-size’ node that holds the size of the page- width and height:  [[BR]] 
 {{{
@@ -35 +35 @@
   <width>640.0</width>
 </page-size>
-}}} [[BR]] [[BR]]
- 
+}}} 
+
 Book resources could also have 3 additional child nodes - ‘pages’, ‘page-templates’ and ‘frame-templates’. The value of these properties is a list of references to resources just like the template one. These child nodes have attribute ‘size’ that is integer number indicating how many elements this list holds. Each element of the list is persisted separately in a child node called accordingly ‘page’ or ‘template’. Those elements have attribute ‘index’ since the order of those elements is important to the way the book is presented. In xml files order of the children with the same name on the same level of the xml is not regarded. That way the list of pages for example page elements could change their place in the xml representation but we won`t lose the information for the order in which they were arranged in the book. [[BR]] [[BR]]
 Pages, groups and page extras (set of annotations on a page for example) could have ‘elements’ child node whose value is basically a list of references. There are a few differences, here the elements nodes are named ‘element’, the ref is persisted in ‘elementRef’ tag and there is an additional ‘entries’ child node that is used by the timelines. [[BR]] [[BR]]