#141 Placement of schematron rules

Lou Burnard

At various times it's been suggested that an ODD specification should include somewhere additional constraints on the usage of an element expressed in terms of schematron rules. It's not however clear where within an elementSpec these rules should be supplied, or if. We need to decide this for our own internal use, but it would also be helpful at least to document the options in TD, or possibly to provide a definitive location in a revision of the content model. See discussion at http://lists.village.virginia.edu/pipermail/tei-council/2008/009798.html and preceding thread.


  • Syd Bauman

    Syd Bauman - 2008-08-17

    Logged In: YES
    Originator: NO

    SR> can you expand on this? can you list all the places you want to
    SR> put <s:pattern>?

    I'm thinking <s:pattern> should be permitted as a child of:
    <schemaSpec>? Maybe that's too gneral.
    I have not yet thought about whether there are some class
    generalizations of which we might take advantage.

  • Lou Burnard

    Lou Burnard - 2008-08-17
    • milestone: --> 871209
  • James Cummings

    James Cummings - 2008-08-18
    • priority: 5 --> 6
  • Lou Burnard

    Lou Burnard - 2009-03-22
    • milestone: 871209 --> 871207
  • Lou Burnard

    Lou Burnard - 2009-03-22

    Although everyone agrees we need this, we still don't have any concrete proposals. I'm making it RED.

  • Lou Burnard

    Lou Burnard - 2009-04-02

    New <constraint> element has been defined as child of elementSpec, attDef, schemaSpec.
    Could be added also to classSpec?
    Should they be separately addressed?
    We need to look at the spec.

  • Lou Burnard

    Lou Burnard - 2009-04-02
    • milestone: 871207 --> AMBER
  • Sebastian Rahtz

    Sebastian Rahtz - 2009-06-05

    This is now resolved for the June 2009 release, with a <constraint> element and its
    <data> child;

  • Sebastian Rahtz

    Sebastian Rahtz - 2009-06-05
    • status: open --> closed

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

Sign up for the SourceForge newsletter:

No, thanks