You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The way to use VIAF seems to be like <author ref="viaf:34551336">Trollope, Frances Milton (1780-1863)</author>. But if the value @ref has a prefix, surely it must be qualified by <prefixDef>?
Yet the English ELTeC has no prefixDef, what is worse, <listPrefixDef> is not allowed in the ELTeC teiHeader. Maybe it should be? (also because other reigistries might be used, for which the mapping to URI is not so well-known).
The text was updated successfully, but these errors were encountered:
Sorry... this slipped through the net. XML validators don't bother to check that a URL value actually goes somewhere, of course, and so don't object to a URL which uses a prefix like this -- it's syntactically valid whether the prefix is defined or not. So I think the "invalid" label is a bit harsh.
Well, it might be XML-valid, but surely it isn't TEI valid, no? Or functionally valid, given that any TEI reference resolver will pick up on the colon and try to find a prefixDef.
Just to note, issue #3 appears relevant on this matter as well. I'd prefer a more verbose / redundant version without the need for a prefix, <prefixDef> and <prefixDefList>.
The way to use VIAF seems to be like
<author ref="viaf:34551336">Trollope, Frances Milton (1780-1863)</author>
. But if the value@ref
has a prefix, surely it must be qualified by<prefixDef>
?Yet the English ELTeC has no prefixDef, what is worse,
<listPrefixDef>
is not allowed in the ELTeC teiHeader. Maybe it should be? (also because other reigistries might be used, for which the mapping to URI is not so well-known).The text was updated successfully, but these errors were encountered: