A bunch of hugely simple questions :
why type the reference string? why not type that to which it
refers/points? I ask because one could be marking up a string that is not
in itself a URL
> > <rs type="url" key="FOO">
> > Where FOO can be looked up somehow in the header, without use of poxy
> > entities.
Why use the header and not say <gi>back</gi> or <gi>front</gi> which could
be a <gi>tei.2</gi> in a <gi>tei.Corpus</gi> ? Didn't someone intimate in
this thread (Peter, I believe) that they wanted to separate out the
logical from the physical designators?
> If I understand you correctly, in the header I'll have something like
> <xptr url="foo-url" id="foo"/>
> while in the text using
> <rs type="url" key="foo" from="id(...)">
> This seems all right. The 'from="id(...)"' is not the most beautiful of
> markup constructs, but we'll need something with its functionality to
> achieve the purpose of defining the url only once but using it repeatedly.
Is there a difference between "defining" a URL and pointing to a location
in a file that houses a URL? Am I correct in believing that it is not
necessary to modify the DTD so that the <attr>key</attr> could be typed as
IDREF and thereby formalize the relation to the value of the
<attr>ID</attr> (and thereby ensure that upon validation that no
<attr>key</attr> values did not match some <attr>id</attr> value?
What are the advantages of the proposed approach over one built upon :
<gi>ref</gi> with <attr>target</attr>
when the target value is of type IDREF and points to the ID value of an
element that houses the targetted URL?
Francois Lachance, Scholar-at-large
mnemonic is to analytic
mimetic is to synthetic