Difference between revisions of "ODD-dev"
Jump to navigation
Jump to search
(Initial creation of article) |
m |
||
Line 26: | Line 26: | ||
=== Problem: attribute/content interdependency === | === Problem: attribute/content interdependency === | ||
* '''Desc:''' Attributes and content interdependency means that you can have either attribute or content but not both. | * '''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:''' none so far | ||
+ | * '''Points for discussion:''' | ||
+ | ** None so far | ||
+ | |||
+ | |||
+ | |||
+ | |||
+ | === Problem: Referencing ODD from Document Instance === | ||
+ | * '''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:''' none so far | * '''Suggested solutions:''' none so far | ||
* '''Points for discussion:''' | * '''Points for discussion:''' |
Revision as of 01:10, 6 August 2009
This page has been set up to record underlying problems with the TEI ODD language and look at methods for improving them.
Contents
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: none so far
- 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:
- None so far
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: none so far
- 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: none so far
- Points for discussion:
- None so far
Problem: Referencing ODD from Document Instance
- 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: none so far
- Points for discussion:
- None so far