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

 


Help: OASIS Mailing Lists Help | MarkMail Help

xri-editors message

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


Subject: RE: [xri-editors] Section for XRI authority cref resolution


Gabe (and all editors): please do send any and all feedback on 09k (and
all TO DOs if possible) by COB today. I need to post 09l by tonight as I
have an all-day meeting tomorrow. One more draft will be posted before
our call on Thursday afternoon, so if you miss the 09l deadline tonight,
you'll have to wait for Thursday.

Below is revised text for the XRI authority cross-reference section:

Resolving Cross-References in XRI Authorities
A sub-segment within an XRI authority segment may be a cross-reference
(see sections 2.1.1.4 and 2.1.2). Resolving a cross-reference is
identical to resolving any other sub-segment because the cross-reference
is considered opaque. In other words, the value of the cross-reference
(including the parentheses) is considered the literal value of the
sub-segment for the purpose of constructing the Next Resolution URI as
described in section 3.2.4.
Table 4 provides several examples. In each of these examples,
sub-segment "b" resolves to a Next Authority URI of
"http://example.com/xri-authority/";.

Cross-reference type	Example XRI	Next Resoluton URI after
resolving "xri:@:a:b"
Absolute XRI	xri:@:a:b:(@:1:2:3).e/f
http://example.com/xri-authority/:(@:1:2:3)
Absolute URI	xri:@:a:b.(mailto:jd@example.com).e/f
http://example.com/xri-authority/.(mailto:jd@example.com)
Relative XRI	xri:@:a:b:(.c.d).e/f
http://example.com/xri-authority/:(.c.d)
Table 4: Examples of the Next Authority URIs constructed using different
types of cross-references.

=Drummond 

-----Original Message-----
From: Wachob, Gabe [mailto:gwachob@visa.com]
Sent: Tuesday, November 04, 2003 9:47 AM
To: Drummond Reed; Dave McAlpin; XRI Editors (E-mail)
Subject: RE: [xri-editors] Section for XRI authority cref resolution

The text is fine and all 3 examples are fine - this is in resolution, so
its not terribly important to describe the function of the xref.

I have some feedback on the k version but I won't be able to get to it
until at least cob today (meetings all day today).

        -Gabe

> -----Original Message-----
> From: Drummond Reed [mailto:drummond.reed@onename.com]
> Sent: Tuesday, November 04, 2003 9:01 AM
> To: Dave McAlpin; XRI Editors (E-mail)
> Subject: RE: [xri-editors] Section for XRI authority cref resolution
>
>
> Good point. Since a relative xref is actually pretty simple, how about
> we compromise and show three examples: a) an absolute XRI
> xref, b) a URI
> xref, and c) the current example, which is a relative XRI xref.
>
> I think all three are very illustrative in the context of the
> main spec.
> You are right that we'll go into this in greater detail in the primer.
>
> I'll rewrite this with all 3 examples and send back to the list.
>
> =Drummond
>
> -----Original Message-----
> From: Dave McAlpin [mailto:dave.mcalpin@epokinc.com]
> Sent: Tuesday, November 04, 2003 7:29 AM
> To: Drummond Reed; XRI Editors (E-mail)
> Subject: RE: [xri-editors] Section for XRI authority cref resolution
>
> Since relative cross-references caused so much internal
> discussion when
> we
> talked about them on the list earlier this week, I'd vote
> that we ues an
> absolute cross-reference in the example below. It might be less
> confusing to
> save relative cross-references for the primer where we can
> explain their
> intended use.
>
> Dave
>
> > -----Original Message-----
> > From: Drummond Reed [mailto:drummond.reed@onename.com]
> > Sent: Monday, November 03, 2003 10:56 PM
> > To: XRI Editors (E-mail)
> > Subject: [xri-editors] Section for XRI authority cref resolution
> >
> >
> > Following is my proposed text for the brief discussion of resolving
> > cross-references in XRI authorities. (As proof of why we need to add
> > this, I was surprised how long it took me to think it through. It's
> > really quite trivial, but the novelty of cross-references as an
> > identifier construct is what could trip up implementers
> without simple
> > guidance like this.)
> >
> > This would go in as section 3.2.6 right after the Examples section
> (sort
> > of like a footnote to the Examples) and right before the
> User Relative
> > XRIs section.
> >
> > Resolving Cross-References in XRI Authorities
> > A sub-segment within an XRI authority segment may be a
> cross-reference
> > (see sections 2.1.1.4 and 2.1.2). Resolving a cross-reference is
> > identical to resolving any other sub-segment because the
> cross-reference
> > is considered opaque. In other words, the value of the
> cross-reference
> > (including the parentheses) is considered the literal value of the
> > sub-segment for the purpose of constructing the Next
> Resolution URI as
> > described in section 3.2.4.
> > For example, when resolving "xri:@:a:b:(.c.d)/f", if the "b"
> sub-segment
> > resolves to a Next Authority URI of
> "http://example.com/xri-authority/";,
> > then the Next Resolution URI would be
> > "http://example.com/xri-authority/:(.c.d)", because "(.c.d)" is the
> > literal value of the entire cross-reference.
> >
> > Comments?
> >
> > =Drummond
> >
> >
> >
> >
> >
> > 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-editors/members/l
> eave_workgroup.php.
>
>
>
>
> 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-editors/membe
rs/leave_w
orkgroup.php.

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-editors/members/leave_w
orkgroup.php.


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