Learn how easy it is to sync an existing GitHub or Google Code repo to a SourceForge project! See Demo

Close

#75 Examples of custom elements within ODD

GREEN
closed-fixed
None
5
2009-03-15
2009-03-11
Elena Pierazzo
No

When a new customised element is created within ODD as belonging to a specific custom namespace (e.g. <cch:oList>) there isn't at present an appropriate element to record examples of usage for such custom element, as <egXML> accepts only elements from the TEI namespace and <eg> element accepts only texts.

Therefore neither:
<exemplum>
<egXML xmlns="http://www.tei-c.org/ns/Examples">
<cch:oList>
<item>First Item</item>
<item>Second Item</item>
<item>Third Item</item>
</cch:oList>
</egXML></exemplum>

and

<exemplum>
<eg>
<cch:oList>
<item>First Item</item>
<item>Second Item</item>
<item>Third Item</item>
</cch:oList>
</eg>
</exemplum>

are valid.

I suggest one of the following solutions:

1. enlarge <egXML> to accept any piece of well formed XML

2. allow <eg> to accept any piece of well formed XML

3. create a new element (e.g. <egXMLcustom>) to accept any piece of well formed XML

Discussion

  • Lou Burnard
    Lou Burnard
    2009-03-14

    • milestone: --> GREEN
    • assigned_to: nobody --> rahtz
     
  • Lou Burnard
    Lou Burnard
    2009-03-14

    As defined. <egXML> should accept any well-formed XML (it uses a macro "anyXML" for that purpose). If you build a schema which includes the tagdocs module unchanged, you will find that this works as you expect. There is currently a bug in schemas generated by Roma however, which erroneously redefines <egXML> to use instead the macro anyTEI -- which doesn't permit any non-TEI elements. So this is a bug in Roma, not in the definition of <egXML>, and I am re-assigning it accordingly.

    The content of <eg> is defined as text only, since you may want to use it for non-XML data. If you want to put XML inside an <eg> you are recommended to wrap it in a CDATA marked section.

     
  • the schema with Roma is now set to allow any well-formed XML inside <egXML>

     
    • status: open --> closed-fixed