Am 23.02.2015 13:39, schrieb James Cummings:
On 23/02/15 10:22, Majewski Stefan wrote:
- don't overuse @xml:id. Only use @xml:id for referencing fragments of a document. The value of @xml:id shall not be parsed into components during document processing
I know I'm probably wrong but because I'm lazy I tend to prefer over-use of @xml:id.
I can't see that this is lazy. Actually, I figure my description was ambiguous. I tried not to say, use only few @xml:id, but don't use @xml:id for other purposes than identifying elements. I think that is an actual recommendation we can make. If there is some semantics within the ID string, this is for the sole purpose of making it easier to handle for a human agent. It should be such that it might be replaced by a random string (honouring the constraints of ID) without breaking anything. Identifying via IDs is very powerful and has all the benefits you described.
The concept of IDs is generally one of the week spots in the XML world. While for other kinds of references, e.g. xlink:href, mechanisms as @xml:base have been introduced to cleanly resolve references, a similar mechanism for @xml:id and references to IDs are missing as IDs have to be unique beyond their immediate scope.
Isn't this easy to implement in schematron? And should we be doing so for TEI generally? If a data.pointer attribute starts with '#' should we be checking that an @xml:id exists with that id? Or do we already do that?
This is a question of the scope in which we have to look for this @xml:id. As far as I can see, probably I have just not found it, does not define how to on which basis relative URIs are to be resolved.
the included documents with these values. But then, fragmental approaches where IDs are referenced that are known to resolve only after inclusion are a problem and might, in e.g. tei:ptr/@target only be resolved and replaced with the generated ID if it is known which document the referenced content resides in.
Use case for private URI syntax?
Any teiCorpus that is created by using xi:include for the aggregation of TEI documents from different sources.
I'd feel more comfortable moving to a recommendation of xlink if it had received widespread adoption.
that is true, the adoption of xlink is not great. But METS uses it, for example. -- Mag. Stefan Majewski Projektmanager Abteilung Forschung und Entwicklung Österreichische Nationalbibliothek Josefsplatz 1, 1015 Wien Tel.: (+43 1) 534 10-434 E-Mail: stefan.majewski@onb.ac.at Skype: stefan.majewski.onb.ac.at