On 06/10/15 21:50, Syd Bauman wrote:
My instinct (which I might be talked out of) is that releasing <xenoData> without @scope is more harmful than not releasing it. That is, I'd prefer to remove <xenoData> from P5 than have it there without a TEI-defined mechanism for distinguishing "about the source" from "about the TEI document". (Although that mechanism need not be @scope.)
My suggested rewording for the <desc> of scope would do this, I claim, without going to the lengths of specifying values for @scope. I think it would be a shame not to include xenoData in this release at all.
We know it is often important to know whether a bit of metadata is about the TEI document (as with <fileDesc> or <correspDesc>) or about the source of that TEI document (as with <sourceDesc> or <revisionDesc>).
This is just nitpicking, but surely the <revisionDesc> is about the TEI document, not its source? And <correspDesc> is definitely not about the TEI document but about the real world events reflected by it.
Why let the world devolve into 2 dozen different ways of saying the same thing?
Ah well, that's the TEI way...
Note ---- [1] For now you'd have to put each set of <place>s that had different metadata in the GeoJSON into its own <div> so said <div> could have an @decls that points to the <xenoData>. That said, can someone explain to me why <listPlace> is in att.declarable but not att.declaring?
I was quite baffled by this question for a while. Declarable elements are provided so that declaring elements like <div> can independently select from a number of possibly relevant chunks of metadata provided together in the header. The mechanism is for fine tuning the standard rule that says "what's in the header applies to everything that the header is attached to". It's not for doing the sorts of things you seem to be considering here, if I understand correctly. Certainly I don't see how a hierarchy of declarability (which you seem to be suggesting) would work.