[tei-council] Disambiguation of <ident> and <idno> (and also <gi>)

[Laurent Romary]

I would support Martin's wording here. This is a real progress, and other threads have shown that we need to secure other pieces of the surrounding (cf. <ref>/<ptr>).
I would suggest that Martin implements this now. And that the council carries on defining a clear identification-pointing-referencing scheme.
Cheers,
Laurent

Le 26 nov. 2011 à 08:13, Martin Holmes a écrit :

> On 11-11-25 03:47 PM, stuart yeates wrote:
>> On 26/11/11 10:06, Martin Holmes wrote:
>> 
>>> ----------
>>> <ident>   should be used for tokens such as variable names, class names,
>>> type names, function names etc. in formal programming languages. (It
>>> should not be used for element and attribute names in XML, for which the
>>> special elements<gi>   and<att>   are provided.)
>>> 
>>> <idno>   should be used for labels which uniquely identify an object or
>>> concept in a formal cataloguing system such as a database or an RDF
>>> store, or in a distributed system such as the World Wide Web.
>>> ----------
>> 
>> These definitions give no indication which to use when a textual string
>> meets both of those criteria.
> 
> I'd suggest that nothing should meet both these criteria. If you're a 
> variable or function name, you're definitely not part of a formal 
> cataloguing system, surely>?
> 
>> I suggest that<idno>  be given precedence,
>> since I imagine it's more widely used.
> 
> I don't really understand what "precedence" means here. If I've failed 
> to disambiguate the two tags, then I should try again, but I don't think 
> we should ever be in the position of saying "these two tags are 
> basically the same, but you should prefer this one because we have a 
> feeling that more people use it than the other one".
> 
> Cheers,
> Martin
> 
> 
>> 
>> cheers
>> stuart
> -- 
> tei-council mailing list
> tei-council at lists.village.Virginia.EDU
> http://lists.village.Virginia.EDU/mailman/listinfo/tei-council
> 
> PLEASE NOTE: postings to this list are publicly archived

Laurent Romary
INRIA & HUB-IDSL
laurent.romary at inria.fr