RE: [xri-editors] Proposals for XRI Descriptor priority attribute

["Drummond Reed" <drummond.reed@cordance.net>]

I believe the modal use case is pretty simple and directly parallels that of
MX records in DNS, i.e., a client application receives back an XRID with
more than one [Authority/Service/Internal Synonym/External Synonym] element
and/or an Authority or Service element with more than one URI element. How
can the publishing Authority unambiguously indicate the priority in which
the client application should consume these elements?

While I agree with Peter's text below, my only question is whether XML
document order should be the default if the priority element is not present.
In other words, should it be:

    The order of processing of sibling nodes of an XRID is XML document
    order unless the priority attribute is present, in which case, resolvers
    SHOULD process the siblings with such attributes as an ordered set
    where lower integer values indicate high sorting weights.

But I don't feel strongly about this, i.e., it could just be unspecified in
the absence of the priority attribute if that's preferred.

=Drummond 

-----Original Message-----
From: Peter Davis [mailto:peter.davis@neustar.biz] 
Sent: Thursday, June 16, 2005 10:40 PM
To: Lindelsee, Mike; Wodjenski, Sharon; Wachob, Gabe; Drummond Reed;
xri-editors@lists.oasis-open.org
Cc: Chasen, Les; Zhang, Ning; Tran, Trung
Subject: Re: [xri-editors] Proposals for XRI Descriptor priority attribute

Sorry, coming late to the party.  I think Mike is spot on.  We definitely
need a set of motivating use cases for this (I know some of them, but
Sharon's got a better grasp than I now ;-)

I think Gabe's recommended semantics are right.  My cast:

    The order of processing of sibling nodes of an XRID is unspecified
    unless the priority attribute is present, in which case, revolvers
    SHOULD process the siblings with such attributes as an ordered set
    where lower integer values indicate high sorting weights.

--- peterd


On 6/14/05 4:09 PM, "Lindelsee, Mike" <mlindels@visa.com> wrote:

> Fair enough.  Even better than example XRIDs might be the use cases that
> those XRIDs are used in.  I think having proposed use cases might help
> us all come to agreement about how the priority attribute should be
> treated.  Does anyone on the list disagree that the resolution spec
> should have normative language regarding the semantics of how a client
> should treat priority attributes?  If not, are there any proposals for
> what those semantics should be?
> 
> Mike 
> 
>> -----Original Message-----
>> From: Wodjenski, Sharon [mailto:sharon.wodjenski@neustar.biz]
>> Sent: Tuesday, June 14, 2005 11:10 AM
>> To: Lindelsee, Mike ; Wachob, Gabe; Drummond Reed;
>> xri-editors@lists.oasis-open.org
>> Cc: Chasen, Les; Zhang, Ning; Tran, Trung; Davis, Peter
>> Subject: RE: [xri-editors] Proposals for XRI Descriptor
>> priority attribute
>> 
>> Mike,
>> 
>> I'm not sure any of the documents would be helpful.  They are
>> internal documents for the GRS design and don't cover anything
>> from a client perspective, or address the semantics of the
>> priority attribute.  About the best I could offer would be
>> some example XRIDs to use for discussion.
>> 
>> Sharon
>> 
>> -----Original Message-----
>> From: Lindelsee, Mike [mailto:mlindels@visa.com]
>> Sent: Monday, June 13, 2005 6:19 PM
>> To: Wodjenski, Sharon; Wachob, Gabe; Drummond Reed;
>> xri-editors@lists.oasis-open.org
>> Cc: Chasen, Les; Zhang, Ning; Tran, Trung; Davis, Peter
>> Subject: RE: [xri-editors] Proposals for XRI Descriptor priority
>> attribute
>> 
>> 
>> Would any of those documents serve as a starting point for this
>> discussion?  I tend to agree with Gabe that if we are going to
>> specify a
>> priority attribute, we should also specify the semantics of that
>> attribute.  At the very least, this seems needed for interoperability.
>> 
>> As a separate issue, if this topic is going to take some discussion to
>> work through, does the current schedule for publishing the specs and
>> voting still make sense?
>> 
>> Mike 
> 
> ---------------------------------------------------------------------
> To unsubscribe from this mail list, you must leave the OASIS TC that
> generates this mail.  You may a link to this group and all your TCs in
OASIS
> at:
> https://www.oasis-open.org/apps/org/workgroup/portal/my_workgroups.php
> 

Sent using the Microsoft Entourage 2004 for Mac Test Drive.


---------------------------------------------------------------------
To unsubscribe from this mail list, you must leave the OASIS TC that
generates this mail.  You may a link to this group and all your TCs in OASIS
at:
https://www.oasis-open.org/apps/org/workgroup/portal/my_workgroups.php