#92 Need Header element to reference or embed schema/odd

RED
closed-accepted
5
2012-04-27
2007-02-01
No

We need a header element to reference or embed a schema or odd that the document is meant to validate against.

This should be able to cope with different namespaces... i.e. I should be able to reference the relaxNG schema for elements starting with rng: the tei: schema I'm using, the svg: schema I'm using, etc.

I should be able just to point to an ODD, an RNG, etc. or embed my ODD etc.

-james

Discussion

  • Lou Burnard

    Lou Burnard - 2007-02-17
    • assigned_to: nobody --> rahtz
     
  • Sebastian Rahtz

    Sebastian Rahtz - 2007-04-02

    Logged In: YES
    user_id=95949
    Originator: NO

    After discussion on the TEI Council list, and related discussion on the RELAXNG list, my judgement is that we are not ready for this. I have transferred the task to the list of open projects for TEI P5 1.1

     
  • Sebastian Rahtz

    Sebastian Rahtz - 2007-04-02
    • status: open --> closed
     
  • James Cummings

    James Cummings - 2010-11-19
    • milestone: --> RED
    • status: closed --> open
     
  • James Cummings

    James Cummings - 2010-11-19

    Re-opening for re-consideration given Laurent's discussion on TEI-L of 2010-11-19.

    The idea is that there should be some place in the header in which one can embed schemaSpec* allow embedding of ODD instances inside document instances and/or pointing to external encoding declaration vocabularies. Simultaneously we want a method to point to an external ODD (or similar schema or meta-schema source), but this has now been answered with @source on schemaSpec.

    So my proposal is that schemaSpec as a child of encodingDesc. i.e. make it a member of model.encodingDescPart and that the guidelines make some mention of this possibility. The recommendation for when you just want to point to an external ODD then would be to use schemaSpec as an empty element with a @source attribute pointing to the source.

    While there is not necessarily one canonical ODD for any particular document instance, and schemas may vary at different points in any workflow, it seems that this feature may be desirable in some form.

    But this is marked as 'RED' because it needs to be discussed more.

    -James

     
  • Laurent Romary

    Laurent Romary - 2010-11-19

    You mean the W3C is using ODD and has a good implementation for this?

     
  • Sebastian Rahtz

    Sebastian Rahtz - 2011-02-26
    • assigned_to: rahtz --> nobody
     
  • Lou Burnard

    Lou Burnard - 2012-04-17

    Use xml:mode to document where youre schema is. Add schemaDesc to model.encodingPart

     
  • Lou Burnard

    Lou Burnard - 2012-04-17
    • assigned_to: nobody --> martindholmes
    • status: open --> pending-accepted
     
  • Sebastian Rahtz

    Sebastian Rahtz - 2012-04-17

    the reference to "xml:mode" is cryptic; what it means is that the W3C have defined a PI-based recommendation for this already, http://www.w3.org/TR/xml-model/, which would encompass linking to an ODD file.

    also note that "schemaDesc" should be "schemaSpec", and model.encodingPart should be model.encodingDescPart

     
  • Sebastian Rahtz

    Sebastian Rahtz - 2012-04-17

    with reference to Laurent's comment, yes, the W3C model would allow for referencing an ODD; but no, there is no implementation.

     
  • Martin Holmes

    Martin Holmes - 2012-04-26

    Added schemaSpec to model.encodingDescPart in rev 10308, per Council's decision in Michigan. If this builds OK, I'll proceed with adding documentation/explanation of both this and xml-model to the Guidelines.

     
  • Martin Holmes

    Martin Holmes - 2012-04-26

    Added a section to the HD <encodingDesc> section with a brief explanation of why you might want to include <schemaSpec> in <encodingDesc>. Next is the recommendation to use the xml-model processing instruction -- not quite sure where to put that, yet.

     
  • Kevin Hawkins

    Kevin Hawkins - 2012-04-27

    Martin's addition is revision 10311. Kevin copyedited at revision 10312.

     
  • Martin Holmes

    Martin Holmes - 2012-04-27

    Done in revs 10314-10317. Closing the ticket.

     
  • Martin Holmes

    Martin Holmes - 2012-04-27
    • status: pending-accepted --> closed-accepted
     

Get latest updates about Open Source Projects, Conferences and News.

Sign up for the SourceForge newsletter:





No, thanks