JATS data, non-JATS data, and XML Namespaces
Wendell Piez
-
Outline [slide 1]
-
Why XML namespaces are beastly [slide 2]
-
Why we need namespaces in XML [slide 3]
-
The solution: prefixes for names [slide 4]
-
Problems with the solution [slide 5]
-
A prefix is just a label for a namespace [slide 6]
-
This makes the syntax complicated [slide 7]
-
Bindings between namespaces and prefixes are loose [slide 8]
-
Namespaces make XML syntax more opaque [slide 9]
-
DTDs don’t know about namespaces [slide 10]
-
Namespaces seem to be on the Internet [slide 11]
-
Control over names and namespaces is hard [slide 12]
-
How to tame namespaces [slide 13]
-
A spec for a “clean namespace” XML document [slide 14]
-
How to make your documents namespace-clean [slide 15]
-
How to validate that your documents are namespace-clean [slide 16]
-
Living with namespaces [slide 17]
-
Why JATS doesn’t want a namespace [slide 18]
-
Why JATS doesn’t need a namespace [slide 19]
-
Why JATS may need a namespace (soon?) [slide 20]
-
The strategic outlook: a summary [slide 21]
-
What should we do? [slide 22]
-
Demonstrations [slide 23]