Search Mailing List Archives
waku at idi.ntnu.no
Fri Jan 19 15:23:15 PST 2007
> this discussion may not apply, however, to the cases where the same term
> is used to represent different things rather than different versions of
> the same thing ('bud', even if not in go right now). in this cases it
> may still be reasonable to use 'sensu ... research community' (and much
> more this than 'sensu ...'), at least temporarily.
on second thought: even in these cases (say, 'bud'; there is 'bud' in
go in the sense of an emerging daughter cell, and there are terms that
refer to 'bud' in a completely different sense, e.g., 'ureteric bud
branching', 'golgi vesicle bud') it might be better to have just 'bud'
as the name of different nodes (terms; 'term name' is an ugly
terminological convention, by the way) associated with different taxa
(and having different definitions). for even if two such nodes have the
same name, there does not need to be a confusion. for the computer, the
nodes are ditinct (by id). for a human user, term names may be modified
on-the-fly to contain the corresponding (and easily kept up to date)
taxon names. searching for a bud, the user is kindly asked whether he
means bud as in cell budding, or as something else.
otherwise, 'bud' should perhaps be renamed to some '... bud', as it
unfairly uses a name that should be reserved for a much more general
node. (surely out of the scope of go).
but this solution is unrealistic with the current go specification that
requires terms to have unique names. this may never come to be changed.
This message is from the GOFriends moderated mailing list. A list of public
announcements and discussion of the Gene Ontology (GO) project.
Problems with the list? E-mail: owner-gofriends at geneontology.org
Subscribing send "subscribe" to gofriends-request at geneontology.org
Unsubscribing send "unsubscribe" to gofriends-request at geneontology.org
More information about the go-friends