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] URI templating proposal


Marty,

 

The template-uri ABNF is:

 

4.1  Template Variables
 
   Template variables are the parameterized components of a URI
   Template, their representation is described below.  A template
   variable MUST match the template-var production.
 
    template-char = unreserved
    template-name  = 1*template-char
    template-var  = "{" template-name "}"

 

By this ABNF, a template name cannot contain a template-var (because “{“ and “}” are not unreserved chars).

 

However fixing this would be easy.

 

    template-char = unreserved
    template-name  = 1*( 1*template-char / template-var )
    template-var  = "{" template-name "}"

 

=Drummond

 


From: Schleiff, Marty [mailto:marty.schleiff@boeing.com]
Sent: Saturday, October 07, 2006 10:46 PM
To: Drummond Reed; Gabe Wachob; xri@lists.oasis-open.org
Cc: xdi@lists.oasis-open.org
Subject: RE: [xri] URI templating proposal

 

Anyone know if the template variables can be nested?

 

Marty.Schleiff@boeing.com; CISSP
Associate Technical Fellow - Cyber Identity Specialist
Computing Security Infrastructure
(206) 679-5933

 

 


From: Drummond Reed [mailto:drummond.reed@cordance.net]
Sent: Saturday, October 07, 2006 12:17 PM
To: 'Gabe Wachob'; xri@lists.oasis-open.org
Cc: xdi@lists.oasis-open.org
Subject: RE: [xri] URI templating proposal

[Note: cross-posted to the XDI TC as well as the XRI TC.]

 

Gabe,

 

Thanks for putting this out. I discussed it with Marty on Thursday. To me it’s a sign of the growing interest in structured identifiers.

 

I think that URI templating could be highly useful with XRIs due to the ability to template the use of cross-references.

 

Ironically, XDI addressing (the use of XRIs to address across and within XDI documents) could be considered almost a pure “XRI templating” language. Recent work on the XDI schema has produced a version where XDI addresses can be algorithmically translated to XPath addresses to locate the precise node in the XML graph.

 

I personally believe we’re headed towards a tipping point in the usage of structured identifiers, be they structure URIs/IRIs or XRIs.

 

=Drummond

 


From: Gabe Wachob [mailto:gabe.wachob@amsoft.net]
Sent: Wednesday, October 04, 2006 8:55 PM
To: xri@lists.oasis-open.org
Subject: [xri] URI templating proposal

 

This is interesting, hopefully for obvious reasons:

 

http://www.mnot.net/blog/2006/10/04/uri_templating

 

**** NOTE: The introduction to the URI Templating spec is excerpted below for convenience. *******

 

1.  Introduction
 
   URI Templates are strings that contain embedded variables that are
   transformed into URIs after embedded variables are substituted.  This
   document defines the structure and syntax of URI Templates.
 
   URI Templates are useful when it's necessary to convey the structure
   of a URI in a well-defined way.  For example, documentation of an
   interface exposed by a Web site might use a template to show people
   how to find information about a user;
 
       http://www.example.com/users/{userid}
 
   URI Templates can also be thought of as the basis of a machine-
   readable forms language; by allowing clients to form their own
   identifiers based on templates given to them by the URI's authority,
   it's possible to construct dynamic systems that use more of the URI
   than traditional HTML forms are able to.  For example,
 
       http://www.example.org/products/{upc}/buyers?page={page_num}
 
   Finally, URI Templates can be used to compose URI-centric protocols
   without impinging on authorities' control of their URIs.  For
   example, there are many emerging conventions for passing around login
   information between sites using URIs.  Forcing people to use a well-
   known query parameter isn't good practice, but using a URI parameter
   allows different sites to specify local ways of conveying the same
   information;
 
       http://login.example.org/login?back={return-uri}
       http://auth.example.com/userauth;{return-uri}
 
   This specification defines the basic syntax and processing of URI
   Templates.  Each application of URI Templates will need to define its
   own profile of this specification that indicates what template
   variables are available, how to convey them to clients, and what
   their appropriate use is in that context.

 

 



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