ODD-dev

From TEIWiki

Jump to: navigation, search


This page has been set up to record underlying problems with the TEI ODD language and look at methods for improving them.

Contents

Areas of concern for ODD-Dev-meetingDH2012

The following areas of concern were collated by Sebastian Rahtz for discussion at the DH2012 ODD meeting:

Areas of ODD2 which are not expressive enough but which can be fixed without a new paradigm

  • Module inter-dependency (if you ask for module X, also bring in module Y)
  • Bertrand's model classes questions

Areas of ODD2 which are not well-enough defined

  • the processing model. what order are things worked on?
  • there is no defined test suite for an ODD processor
  • is the DTD/RELAXNG/XSD output defined or can a processor choose different methods?
  • what documentation generation options are supported? how to document customizations

ODD-processing which is unimplemented at present

  • Chaining of ODDs (a customization of a customization)
  • Per-element attribute-based customisation at source (specialized @type on div)
  • Supporting multiple customizations of the same element (in different areas)
  • Declaring an attribute class and then customizing it straightaway
  • Generating XSD natively

Problems which do not seem amenable to ODD as it stands and need a new version

  • Durand Conundrum: Express content models as native TEI? : DONE
  • Subclasses (element <foo> has a simpler content model if its in the header)
  • Attribute/content interdependency (if <foo>, then attribute @y must be used)
  • Alternation of attribute/element (either child <y> or attribute @y)
  • Expressing XPath-based constraints (Schematron) in a TEI language with embedded documentation
  • Short-cut content models based entirely on model classes (<classes><containerOf key="model.foo"/></classes>)

Other problems / earlier discussions

Problem: Module inter-dependency

  • Desc: In some cases elements in one TEI module (A) require that another TEI module (B) is loaded because the content models of an element in A directly requires something that is defined in B (e.g. a class or element) but no method exists indicate this module inter-dependency. This sort of dependency can, of course, happen inside a single module as well with a content model explicitly referring to a particular element which is then removed. Some concept of dependency of references needs to be implemented.
  • Suggested solutions:

This is largely mitigated by ensuring that content models reference model classes rather than explicit elements. A further prosecution of class warfare might therefore be useful.

  • Points for discussion:
    • None so far

Problem: Subclasses

  • Desc: The ability to add subclass membership to an element to, for example, grant it some extra attributes in a particular location. e.g. “I want the head inside figure to be the real <tei:head> element but have it be a member of att.mySpecialAttributes to give it some extra attributes, but only when it is inside <figure>”. This may also relate to Per-element attribute-based customisation in specific circumstances mentioned below.
  • Suggested solutions: none so far
  • Points for discussion:
  1. I (Syd) am under the impression that the problem cannot occur exactly as described. If you add attributes to the <head> element (whether directly or by adding it to the class att.mySpecialAttributes), it will not validate against tei_all, and has to be placed in another namespace. I.e., it cannot be <tei:head>.
        1. Reply: Perhaps poorly phrased in the description. How about we reverse it: let's say you want to remove @n from <figure> globally, but then allow it back when inside <figure>. Obviously you can test that with schematron, but not (I think) simply by adding <figure> to a new attribute class. James 10:23, 1 September 2009 (EDT)
  1. That said, the desire to have special attributes on <my:head> when it is a child of <figure> and not otherwise is a very reasonable one.
  2. RELAX NG permits co-occurrence constraints like this, but ODD and DTDs do not. W3C Schema 1.0 does not. Rumor has it that XSD 1.1 will, but I haven't looked carefully.
  3. As it stands it would be very reasonable to add the attributes to <my:head> in the ODD tagdoc, and then add a “don't use these attributes unless a child of <figure>” as a <constraintSpec>, i.e., in Schematron.

It seems to me that this is very much in schematron country, because of the element content/context dependency.

Problem: Per-element attribute-based customisation

  • Desc: The ability to customise the desc, valList, and other aspects of an attribute inherited from a class on a per-element basis. For example giving different suggested values for @type on an element, or a more specific description of an attribute when used on a certain element.
  • Suggested solutions: This is probably the request of http://purl.org/tei/fr/337683, allowing specialization of elements back at source level rather than in a customization
  • Points for discussion:
    • None so far

Problem: attribute/content interdependency

  • Desc: Attributes and content interdependency means that you can have either attribute or content but not both.
  • Suggested solutions: none so far
  • Points for discussion:
    • None so far


Problem: Chaining of ODDs

  • Desc: ODD should be able to be based not on the full TEI but on another ODD customisation of ODD.
  • Suggested solutions: I think the new @source attribute makes a major step in this direction
  • Points for discussion:
    • None so far

Problem: Referencing ODD from Document Instance

NOTE: This was discussed by Counci in Ann Arbor in April 2012, and will be going ahead. The ticket for this is [[1]].

  • Desc: The best place to reference an ODD in a document instance that creates the schema that the document instance is meant to validate against. Equally, whether an ODD can be embedded (or XIncluded) into a document instance. This would create a truly portable TEI document which held the document itself, and the means to create the schema and schema documentation all in a single document. This is potentially useful as an archival format.
  • Suggested solutions:
  • Doesn't Roma now include details of the ODD from which a schema was generated as a comment inside the schema? That is probably as far as we should go in this direction.
    • But Lou, a mere link to a TEI source, whilst an improvement isn't a consistently machine-processable way of storing that information. If I want to process a bunch of TEI document instances and find out what ODD they were created against, I have no good method of doing so. Somewhere in the header (in encodingDesc? tagsDecl?) should be an appropriate place for someone to, at very least, store a <ptr/> to the ODD file. XML comments inside generated schemas are not reliable and you may not have a copy of the schema, but want to regenerate it from the ODD. The simple case of embedding a link in the teiHeader somewhere seems quite a trivial bug in that the TEI doesn't make any recommendation of where to put it (so a prose change and maybe allowing <ptr/> somewhere). Comments in XML can be and are thrown away by XML processors according to the spec. The more difficult case of embedding the entire ODD with the document as an archival format is admittedly more extreme... I mean I have an example ODD which does this by allowing instances to embed it in encodingDesc, but a better solution might be more useable for archival formats of the TEI.

Problem: Classification of Elements as belonging to one or more category to aid interoperability

  • Desc: This may be already possible in TEI ODD, but not clearly documented for this purpose. The idea is that any form of customization inside a <schemaSpec> or any element/attribute/class should be able to be categorized as to its nature(s). This categorization can then be used to know whether this item is considered important for interchange/interoperability on one or more lossy exports of the document for interchange or interoperable uses. Thus for various uses elements of a certain category could just be silently ignored, whereas others could be processed following their 'equiv', and other preserved as essential, etc.
Personal tools