#19 metDecl Problem

closed
5
2008-01-20
2007-05-11
No

I have two things, one problem, one hint. Hint goes first: The docu says, concerning metDecl@type

<cit>
Values are:
met (met attribute) declaration applies to the abstract metrical form recorded on the met attriubte
real (real attribute) declaration applies to the actual realization of the conventional metrical structure recorded on the real attriubte
met (rhyme attribute) declaration applies to the rhyme scheme recorded on the rhyme attriubte
</cit>

Here we have 'met' two times, I believe the second one should read 'rhyme'?

And here's the problem: I only found the forementioned problem because I generated an xsd using Roma. This is my definition:

<schemaSpec ident="tei-transcr" xml:lang="en" prefix="">
<moduleRef key="core"/>
<moduleRef key="tei"/>
<moduleRef key="header"/>
<moduleRef key="textstructure"/>
<moduleRef key="analysis"/>
<moduleRef key="figures"/>
<moduleRef key="gaiji"/>
<moduleRef key="linking"/>
<moduleRef key="transcr"/>
</schemaSpec>

I needed to add "linking" to this customization in order to have <seg> in the schema but additionally to that I received the problem that my validator (XMLSpy, sorry!) now throws the error that 'met real' doesn't match the type of xs:Name:

<cit>
Der Value Constraint 'met real' des Attributs 'type' ist hinsichtlich seiner Typdefinition 'ns1:data.enumerated' nicht gültig.
Fehlerpfad: xs:schema / xs:attributeGroup / xs:attribute / @
cvc-pattern-valid: 'met real' entspricht nicht den Regular Expressions der Typdefinition 'xs:Name'.
cvc-datatype-valid.1.1: Bei der Typdefinition 'ns1:data.enumerated' ist der String 'met real' nicht pattern-gültig.
cvc-simple-type.1: Bei der Typdefinition 'ns1:data.enumerated' ist der String 'met real' nicht gültig.
a-props-correct.2: Der Value Constraint 'met real' des Attributs 'type' ist hinsichtlich seiner Typdefinition 'ns1:data.enumerated' nicht gültig.
</cit>

What's going wrong here? Do I need to include more modules or change my set in any other way?

Best, Torsten

Discussion

  • Lou Burnard

    Lou Burnard - 2007-05-12
    • labels: 627821 --> TEI: Text of the Guidelines
     
  • Lou Burnard

    Lou Burnard - 2007-05-12

    Logged In: YES
    user_id=1021146
    Originator: NO

    I've fixed the typos which caused the first problem, but the XSD problem looks more serious. The ODD says that the value for @type can be repeated 1 to 3 times, but obviously this isn't getting through to the XSD version of the schema.

     
  • Sebastian Rahtz

    Sebastian Rahtz - 2007-07-09

    Logged In: YES
    user_id=95949
    Originator: NO

    The "maxOccurs limit of 3" concept is not supported by
    the Roma tools at the moment. I will look at fixing this
    shortly.

     
  • Lou Burnard

    Lou Burnard - 2008-01-13
    • assigned_to: nobody --> rahtz
     
  • Sebastian Rahtz

    Sebastian Rahtz - 2008-01-20

    Logged In: YES
    user_id=95949
    Originator: NO

    I have to reluctantly say that I think XMLspy is at fault. The
    XSD schema appears to be correct according to other
    validators.

     
  • Sebastian Rahtz

    Sebastian Rahtz - 2008-01-20
    • status: open --> closed
     

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

Sign up for the SourceForge newsletter:





No, thanks