Skip to content

xsd generated from TEILex0-ODD with UPA errors #223

@kisram

Description

@kisram

We had a similar issue to #66. Creating an xsd using the TEI ODD to XML Schema transformation scenario on oXygen (v 26.0, build 23100905) results in an xsd file with 23 "Unique Particle Attribution" errors.
Below is the complete list for reference.
Since we're using ODD chaining, we fixed these on our side, as you can see here.
It seems that not that many people still use xsd, but since this might be useful for someone else... I tried to identify the reasons for the errors in this issue.

"http://www.tei-c.org/ns/1.0":xr and "http://www.tei-c.org/ns/1.0":xr (or elements from their substitution group) violate "Unique Particle Attribution". During validation against this schema, ambiguity would be created for those two particles.
"http://www.tei-c.org/ns/1.0":xr and "http://www.tei-c.org/ns/1.0":xr (or elements from their substitution group) violate "Unique Particle Attribution". During validation against this schema, ambiguity would be created for those two particles.
"http://www.tei-c.org/ns/1.0":note and "http://www.tei-c.org/ns/1.0":note (or elements from their substitution group) violate "Unique Particle Attribution". During validation against this schema, ambiguity would be created for those two particles.
"http://www.tei-c.org/ns/1.0":lbl and "http://www.tei-c.org/ns/1.0":lbl (or elements from their substitution group) violate "Unique Particle Attribution". During validation against this schema, ambiguity would be created for those two particles.
"http://www.tei-c.org/ns/1.0":lbl and "http://www.tei-c.org/ns/1.0":lbl (or elements from their substitution group) violate "Unique Particle Attribution". During validation against this schema, ambiguity would be created for those two particles.
"http://www.tei-c.org/ns/1.0":hi and "http://www.tei-c.org/ns/1.0":hi (or elements from their substitution group) violate "Unique Particle Attribution". During validation against this schema, ambiguity would be created for those two particles.
"http://www.tei-c.org/ns/1.0":hi and "http://www.tei-c.org/ns/1.0":hi (or elements from their substitution group) violate "Unique Particle Attribution". During validation against this schema, ambiguity would be created for those two particles.
"http://www.tei-c.org/ns/1.0":hi and "http://www.tei-c.org/ns/1.0":hi (or elements from their substitution group) violate "Unique Particle Attribution". During validation against this schema, ambiguity would be created for those two particles.
"http://www.tei-c.org/ns/1.0":hi and "http://www.tei-c.org/ns/1.0":hi (or elements from their substitution group) violate "Unique Particle Attribution". During validation against this schema, ambiguity would be created for those two particles.
"http://www.tei-c.org/ns/1.0":hi and "http://www.tei-c.org/ns/1.0":hi (or elements from their substitution group) violate "Unique Particle Attribution". During validation against this schema, ambiguity would be created for those two particles.
"http://www.tei-c.org/ns/1.0":hi and "http://www.tei-c.org/ns/1.0":hi (or elements from their substitution group) violate "Unique Particle Attribution". During validation against this schema, ambiguity would be created for those two particles.
"http://www.tei-c.org/ns/1.0":hi and "http://www.tei-c.org/ns/1.0":hi (or elements from their substitution group) violate "Unique Particle Attribution". During validation against this schema, ambiguity would be created for those two particles.
"http://www.tei-c.org/ns/1.0":hi and "http://www.tei-c.org/ns/1.0":hi (or elements from their substitution group) violate "Unique Particle Attribution". During validation against this schema, ambiguity would be created for those two particles.
"http://www.tei-c.org/ns/1.0":hi and "http://www.tei-c.org/ns/1.0":hi (or elements from their substitution group) violate "Unique Particle Attribution". During validation against this schema, ambiguity would be created for those two particles.
"http://www.tei-c.org/ns/1.0":hi and "http://www.tei-c.org/ns/1.0":hi (or elements from their substitution group) violate "Unique Particle Attribution". During validation against this schema, ambiguity would be created for those two particles.
"http://www.tei-c.org/ns/1.0":hi and "http://www.tei-c.org/ns/1.0":hi (or elements from their substitution group) violate "Unique Particle Attribution". During validation against this schema, ambiguity would be created for those two particles.
"http://www.tei-c.org/ns/1.0":hi and "http://www.tei-c.org/ns/1.0":hi (or elements from their substitution group) violate "Unique Particle Attribution". During validation against this schema, ambiguity would be created for those two particles.
"http://www.tei-c.org/ns/1.0":hi and "http://www.tei-c.org/ns/1.0":hi (or elements from their substitution group) violate "Unique Particle Attribution". During validation against this schema, ambiguity would be created for those two particles.
"http://www.tei-c.org/ns/1.0":hi and "http://www.tei-c.org/ns/1.0":hi (or elements from their substitution group) violate "Unique Particle Attribution". During validation against this schema, ambiguity would be created for those two particles.
"http://www.tei-c.org/ns/1.0":hi and "http://www.tei-c.org/ns/1.0":hi (or elements from their substitution group) violate "Unique Particle Attribution". During validation against this schema, ambiguity would be created for those two particles.
"http://www.tei-c.org/ns/1.0":hi and "http://www.tei-c.org/ns/1.0":hi (or elements from their substitution group) violate "Unique Particle Attribution". During validation against this schema, ambiguity would be created for those two particles.
"http://www.tei-c.org/ns/1.0":hi and "http://www.tei-c.org/ns/1.0":hi (or elements from their substitution group) violate "Unique Particle Attribution". During validation against this schema, ambiguity would be created for those two particles.
"http://www.tei-c.org/ns/1.0":availability and "http://www.tei-c.org/ns/1.0":availability (or elements from their substitution group) violate "Unique Particle Attribution". During validation against this schema, ambiguity would be created for those two particles.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions