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] updated proposed XRI 1.1 ABNF


Bryan,

Good question. XRI 1.1, like most any 1.1 specification, did arise through
feedback from multiple implementations of the 1.0 spec. Implementations I
know of include Epok (www.epok.net), Identity Commons (www.idcommons.net),
and various open source implementations that are part of the XRI Support
project at Sourceforge (http://sourceforge.net/projects/xri/). 

Links to much of the activity going on around XRI and XDI (XRI Data
Interchange - see http://www.oasis-open.org/committees/xdi) are also
available at the XRIXDI Wiki operated by Identity Commons
(http://xrixdi.idcommons.net). 

=Drummond 

-----Original Message-----
From: Bryan Rasmussen [mailto:brs@itst.dk] 
Sent: Thursday, September 23, 2004 1:50 AM
To: xri@lists.oasis-open.org
Subject: SV: [xri] updated proposed XRI 1.1 ABNF


Well I've just joined this group as an observer, although I have read
sporadically on the technology for a while, my reason for joining is I think
it might help me with a bunch of things I need to do, and because I am also
interested in making an implementation (probably wouldn't start for at least
a month from now, I'm hoping this list together with evening reading of
specs will help sketch out my path). That said I'm not sure I understand why
XRI is at 1.1, when I hear 1.1 after something I automatically think there
must have been a 1.0 with implementations, and that those implementations
were fairly wide spread and canonical, have there been? 

>1.  Concern about allowing the "//" at the beginning of an XRI to be
optional.  Resolution: "//" is never optional.  
>Absolute XRIs begin with "xri://" or with either an xref or gcs character.
Anyway, since the implementation I was thinking of would be for IE if xri:
without // is encountered an error must be returned, are there any
requirements on errors that would answer this, a malformed xri? 






To unsubscribe from this mailing list (and be removed from the roster of the
OASIS TC), go to
http://www.oasis-open.org/apps/org/workgroup/xri/members/leave_workgroup.php
.





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