On 09/09/10 21:35, Sebastian Rahtz wrote:
> I reckon I misunderstood @copyOf. early, apologies.
> "An application program should replace whatever is the actual content
> of an element bearing a<att>copyOf</att> attribute with the content of
> the element specified by it"
> so actually the use of it for "XInclude" _is_ right
>> One of the major changes in P5 was the change of ID/IDREF(S) to
>> xsd:anyURI and I think we need to recognise that any of these hundreds
>> of pointing attributes now may have slightly changed semantics (in that
>> they are able to point outside the document).
> I dont see that this changes the semantics?
Well, I think what I mean by this is that the description of some of
these attributes seem to assume that the reference is pointing
internally to the document so, an example just stumbled across,
occupation/@scheme is data.pointer and its definition is:
"identifies the classification system or taxonomy in use by supplying
the identifier of a taxonomy element elsewhere in the header."
But why, oh why, are we enforcing that this taxonomy has to be
'elsewhere in the header'? What if I want to store my taxonomies
centrally with a group of other projects somewhere on the net?
Especially when the @scheme attribute on socecStatus just says
"identifies the classification system or taxonomy in use." It isn't
that these becoming URIs has really changed the semantics, but that we
maybe should go through and standardise the way we describe them. I'm
unconvinced that any uri datatype in the TEI should be required to only
Dr James Cummings
Research Technologies Service, University of Oxford