RE: [xri] SEP type registries and XRD self-descriptions

["Mary McRae" <mary.mcrae@oasis-open.org>]

Nope.

> -----Original Message-----
> From: Peter Davis [mailto:peter.davis@neustar.biz]
> Sent: Friday, November 21, 2008 8:27 AM
> To: Gabe Wachob
> Cc: Drummond Reed; Barnhill, William [USA]; Nick Nicholas; OASIS XRI TC
> Subject: Re: [xri] SEP type registries and XRD self-descriptions
> 
> OASIS must have a registry for such things.. after all, they must
> track schema namespaces already, and the SSTC has a large collection
> of URIs used to define profiles and authN contexts (among other things)
> 
> =peterd
> 
> On Nov 21, 2008, at 2:08 AM, Gabe Wachob wrote:
> 
> > I registered xrdstype.net - but there was never a lot of interest.
> >
> > If you want to take it over, I think that could be arranged. Its
> > just really a namespace...
> >
> > On Thu, Nov 20, 2008 at 10:49 PM, Drummond Reed
> <drummond.reed@cordance.net
> > > wrote:
> > > -----Original Message-----
> > > From: Barnhill, William [USA] [mailto:barnhill_william@bah.com]
> > >
> > > <snip>
> > >
> > > By the way, was a mechanism ever settled on how to register new
> > service
> > > endpoint types, or if such a registration process will exist?  To
> my
> > > knowledge the only registry is the wiki one at http://
> > xrdstype.net/. Is
> > > that the standard one at present?
> >
> >
> > Bill, there's never been a formal mechanism for registering service
> > endpoint
> > types -- since they are URIs, it's inherently decentralized.
> > http://xrdstype.net/ and the Wikipedia page for XRDS
> > (http://en.wikipedia.org/wiki/XRDS) are the two "directories" I know
> > of.
> >
> >
> > > I ask as I'd like to register two service types: one for
> > > resource-description, i.e. an endpoint that provides additional
> > metadata
> > > on the resource described by XRD, and one for self-description,
> > i.e. an
> > > endpoint that provides metadata on the enveloping XRD itself.
> >
> > What types of additional resource description do you have in mind?
> > Are you
> > thinking other formats (e.g., RDF, POWDER, XDI)? If so, I think that
> > in the
> > new XRD design those would just service endpoints with a MediaType
> > (and no
> > Type) element plus the URI at which that mediatype was available.
> > Example:
> >
> > <XRD>
> >        <Service>
> >                <MediaType>application/rdf+xml</MediaType>
> >                <URI>http://example.com/some/rdf.xml</URI>
> >        </Service>
> > </XRD>
> >
> > As for self-description, we talked about that at the F2F, and no
> > service
> > type should be needed for that because XRD discovery is recursive,
> > i.e.,
> > since the XRD is itself a resource with a URI, you can do XRD
> > discovery on
> > that URI.
> >
> > For example, if the original URI on which are doing XRD discovery on
> > is
> > http://yahoo.com, and you discovery the URI of its XRD is
> > http://yahoo.com/xrd, then to get XRD metadata on the XRD itself,
> > you'd do
> > XRD discovery on http://yahoo.com/xrd (which might lead you to a URI
> > like
> > http://yahoo.com/xrd/xrd - whatever template Yahoo uses).
> >
> > Hope this helps,
> >
> > =Drummond
> >
> >
> > ---------------------------------------------------------------------
> > To unsubscribe from this mail list, you must leave the OASIS TC that
> > generates this mail.  Follow this link to all your TCs in OASIS at:
> > https://www.oasis-
> open.org/apps/org/workgroup/portal/my_workgroups.php
> >
> >
> >
> >
> > --
> > Gabe Wachob / gwachob@wachob.com \ http://blog.wachob.com
> >
> 
> Peter Davis: NeuStar, Inc.
> Director & Distinguished Member of the Technical Staff
> 45980 Center Oak Plaza Sterling, VA 20166
> [T] +1 571 434 5516 [E] peter.davis@neustar.biz [W]
> http://www.neustar.biz/
>   [X] xri://@neustar*pdavis [X] xri://=peterd
> The information contained in this e-mail message is intended only for
> the use of the recipient(s) named above and may contain confidential
> and/or privileged information. If you are not the intended recipient
> you have received this e-mail message in error and any review,
> dissemination, distribution, or copying of this message is strictly
> prohibited. If you have received this communication in error, please
> notify us immediately and delete the original message.
> 
> 
> 
> ---------------------------------------------------------------------
> To unsubscribe from this mail list, you must leave the OASIS TC that
> generates this mail.  Follow this link to all your TCs in OASIS at:
> https://www.oasis-open.org/apps/org/workgroup/portal/my_workgroups.php