[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [Elist Home]
Subject: RE: [chairs] Oasis document identifiers - conclusion?
Carlisle's
point is an excellent illustration of the rule that every naming convention is
really a database indexing decision. We've seen
both cases now – that indexing by the Status is most important and indexing by
the TC identifier is most important. Neither is
"right", just more convenient depending on your POV and needs at a
particular point in time. The
"right" answer would to be able to index the documents both ways. Gabe
Wachob and I, co-chairs of the XRI TC which starts this week, appreciate how
much this discussion reflects the requirements of our TC's work. Each OASIS document
is a resource which needs to be identified. Each resource has multiple
attributes and different identifiers could be used to reflect different attributes
depending on the needs of the end user trying to locate or reference the
resource. The ideal
solution would be an identifier syntax and resolution capability that supports
any combination of the attributes that results in resolution to a unique
instance. That's one of the key goals of our TC. [Sorry,
but it won't be available until at least we reach CS status.] =Drummond -----Original
Message----- Hi all, At Eve's request, I'm forwarding this to
the chair's list (I hadn't done this initially because I don't feel too
strongly about this, but thought it was worth registering a vote with Eve...). Carlisle. -----Original Message----- Makes sense to me! (Now I don't know
which side of the fence I'm on.
Eve Carlisle Adams wrote: -- |
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [Elist Home]
Powered by eList eXpress LLC