James Cummings wrote:
> 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'?
We're not enforcing it. If it's data.pointer it can point anywhere and
there is no additional schematron rule to restrict it.
I think the phrase you're quoting is a bug. Fill in a ticket!
> unconvinced that any uri datatype in the TEI should be required to only
> point internally.
I think we made that decision long ago!