OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.


Help: OASIS Mailing Lists Help | MarkMail Help

xri message

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]

Subject: Re: [xri] Minutes: XRI TC Telecon 2-3PM PT Thursday 2009-07-16

On Jul 21, 2009, at 11:13 AM, Eran Hammer-Lahav wrote:

> We can also turn this into an attribute of <Subject>, something like
> 'set="prefix"' which will allow other rules in the future (such as
> 'set="regex"').

One problem with using a "set" attribute on <Subject> is that you are  
still limited to a type of xs:anyURI.  This would prevent you from  
having any kind of meaningful regex value down the road.  Granted,  
this isn't a problem for our current use-case, where set="beginswith"  
works just fine, but how much flexibility do we want to leave here?  A  
<SubjectSet> element with a type of xs:string provides a lot of  
flexibility with the value.  Breaking things back out into separate  
XML elements as Scott just asked about also provides flexibility, but  
in a different way.

One specific use case does come to mind with this discussion, also --  
webfinger.  From the last webfinger discussions I remember, the plan  
was still to use a non-URL identifier.  So either they would need a  
non-URL subject element to use for matching, or perhaps would need to  
define some other rules for matching the identifier with the <Subject>  
URL value?  This may not be anything we need to worry about for XRD,  
but I at least wanted to mention it.


[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]