Importer Manual / Version 2406.0
Table Of ContentsThe following example shows the construction of a CoreMedia XML file:
<coremedia> <document name="MyDocument" id="1" type="Text" path="/News/Financial/"> <version number="1"> <string name="Headline" value="New market on downward trend"/> <text name="Text"> <div> <p>Nemax closed with losses.</p> </div> </text> <linklist name="Images"><link idref="pic1"/></linklist> <action name="approve"/> </version> </document> <document name="NemaxChart" id="pic1" type="Image" path="/News/Financial/Charts"> <version number="1"> <blob name="original" mimetype="image/jpeg" href="nemaxchart.jpg"/> </version> </document> </coremedia>
Example 4.1. CoreMedia XML
CoreMedia XML files essentially match the CoreMedia DTD but the importer does not support the full extent of the DTD. There are both limitations and expansions.
The root element is <coremedia>
. As child elements, multiple <document> elements
can arise. Each <document> element describes a document. The <document> elements
contain in turn one or more <version> elements. The <version> elements contain
child elements which can be divided into two groups: field elements and action elements.
They describe the content and status of the document.
Section 4.1.4, “Field Elements” describes the field elements and
Section 4.1.5, “Action Elements” the action elements in detail.