All,
I’m in the process of integrating the latest DTD and
Schema changes into the copies we have in our install tree for the next
release, and I think I’ve found some bugs in the schemas.
Firstly, schema-based maps are showing errors about not
being able to find xml:space and xml:lang top-level attributes from
commonElementsGrp.xsd. I notice in the latest changes, Eric removed the
schemaLocation attribute from the import for the XML namespace. Is there
a reason it was dropped? It’s there other places the namespace is
imported (utilitiesDomain, programmingDomain, softwareDomain, and
uiDomain). Adding it back causes our Editor to stop complaining.
Also, learningMapDomain.xsd misspells
‘locktitle’ (‘loctitle’). Looks like this dates back to
when it was first added in January, so it’s not a new bug.
Finally, the learning schemas have some class attribute bugs.
The class attribute on lcLom is incorrectly defined as “+ topic/metadata
learning-d/lcLom” instead of “+ topic/metadata
learningmeta-d/lcLom”, and learningSummaryRef uses "- map/topicref
learningmap-d/learningSummaryRef " instead of "+ map/topicref
learningmap-d/learningSummaryRef " (- instead of +).
None of these problems are in the DTD versions. I
don’t know what the implications are for changing the schemas at this
point in the process, but I wanted to raise the issue.
Chris
P.S. Arbortext Editor has a Specialization Validation tool (historically,
incorrect customer specializations is one of our major tech support headaches).
It uncovered all but the first issue. Going forward, I’m happy to
volunteer to run it on future changes as they’re made as a sanity check.
|
|
|
|
