|
|
|
| Untersuchte Arbeit: Seite: 20, Zeilen: 8-21 |
Quelle: W3C 1999 Seite(n): online, Zeilen: 0 |
|---|---|
| The W3C Consortium envisions XML applications where a single XML document may contain markup vocabulary (elements and attributes) that are defined for and used by multiple software modules. One motivation for this is modularity; if such a markup vocabulary exists which is well-understood and for which there is useful software available, it is better to re-use this markup rather than re-invent it. But such documents, containing multiple markup vocabularies, pose problems of recognition and collision. Software modules need to be able to recognize the tags and attributes which they are designed to process, even in the face of collisions occurring when markup intended for some other software package uses the same element type or attribute name. XML Namespaces (W3C 1999a) avoid the collision of different semantics, when using different XML documents. XML namespaces provide a simple method for qualifying element and attribute names used in Extensible Markup Language documents by associating them with namespaces identified by URI (Uniform Resource Identifiers) references.
W3C (eds) 1999a, Namespaces in XML, W3C Recommendations, |
XML namespaces provide a simple method for qualifying element and attribute names used in Extensible Markup Language documents by associating them with namespaces identified by URI references.
[...] We envision applications of Extensible Markup Language (XML) where a single XML document may contain elements and attributes (here referred to as a "markup vocabulary") that are defined for and used by multiple software modules. One motivation for this is modularity; if such a markup vocabulary exists which is well-understood and for which there is useful software available, it is better to re-use this markup rather than re-invent it. Such documents, containing multiple markup vocabularies, pose problems of recognition and collision. Software modules need to be able to recognize the tags and attributes which they are designed to process, even in the face of "collisions" occurring when markup intended for some other software package uses the same element type or attribute name. |
The source is given but it is not made clear that the text is so extensively copied. |
|