Skip to content

two subsequent elementSpec declarations of standOff... why? #14

Open

Description

@bansp

I'm trying to investigate the issues mentioned in ticket #13 , because I indeed do not get the problem with "vanilla" TEI schemas, and so I'm looking closer at this ODD, and one of the first striking things is the doubled declaration-redeclaration of <standOff>. Is this caused by some internal ODD processing glitch (perhaps not existent any longer)? Or, can the two get conflated into a single declaration (with @mode="add")?

I mean, it's AFAIK not an error, but it's confusing. OK to conflate? (I've tested the conflated ODD already).

<elementSpec ident="standOff" mode="add" ns="http://standoff.proposal" module="standOff">
                    <desc>Container element for standoff annotations</desc>
                    <classes>
                        <memberOf key="model.resourceLike" mode="add"/>
                        <memberOf key="att.global" mode="add"/>
                        <memberOf key="att.datcat" mode="add"/>
                        <memberOf key="att.ascribed" mode="add"/>
                        <memberOf key="att.datable.w3c" mode="add"/>
                        <memberOf key="att.responsibility" mode="add"/>
                        <memberOf key="att.pointing" mode="add"/>
                        <memberOf key="att.typed" mode="add"/>
                    </classes>
                    <content>
                        <rng:optional>
                            <rng:ref name="teiHeader"/>
                        </rng:optional>
                        <rng:zeroOrMore>
                            <rng:ref name="model.resourceLike"/>
                        </rng:zeroOrMore>
                        <rng:zeroOrMore>
                            <rng:ref name="listAnnotation"/>
                        </rng:zeroOrMore>
                        <rng:zeroOrMore>
                            <rng:ref name="standOff"/>
                        </rng:zeroOrMore>
                    </content>
                </elementSpec>

                <elementSpec ident="standOff" module="standOff" mode="change"
                    ns="http://standoff.proposal">
                    <constraintSpec ident="StandOffNamespace" scheme="isoschematron" mode="add">
                        <constraint>
                            <ns xmlns="http://purl.oclc.org/dsdl/schematron" prefix="stdf"
                                uri="http://standoff.proposal"/>
                        </constraint>
                    </constraintSpec>
                    <constraintSpec ident="SecondLevelStandOffTyping" scheme="isoschematron"
                        mode="add">
                        <constraint>
                            <assert xmlns="http://purl.oclc.org/dsdl/schematron"
                                test="@type or not(ancestor::stdf:standOff)">This <name/> element
                                must have a @type attribute, since it has an ancestor
                                <name/></assert>
                        </constraint>
                    </constraintSpec>
                </elementSpec>

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions