[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: Re: [xri] <Type>
We seems to have enough consensus to make this change and produce another working draft.
I think showing other communities that we are in fact very receptive to suggestions would encourage more engagement and feedback on the CD. It will also allow us to open a new vote on CD2 as soon as the public review period ends.
EHL
> -----Original Message-----
> From: Nat Sakimura [mailto:n-sakimura@nri.co.jp]
> Sent: Monday, November 09, 2009 2:49 AM
> To: Eran Hammer-Lahav
> Agreed.
>
> So, in the xrd, it will appear like:
>
> <subject>https://xri.net/=nat</subject>
> <link rel="http://openid.net/rel/myop">
> <property
> key="http://openid.net/type/localid">https://example.net/nat_s</propert
> y>
> <url>https://delegatedop.example.net</url>
> </link>
>
> etc.
>
> =nat
>
> Eran Hammer-Lahav wrote:
> > This of course raises the question of supporting the <Property>
> element as a child of <Link>. Seems to make sense, especially
> considering the OpenID delegation use case (not sure it is still valid
> but a good example), where such an element will remove the need to
> define another XML namespace. It is also in line with the HTTP Link
> header which explicitly allows extensions in the form of key/value
> pairs.
> >
> > This model makes XRD truly extensible without the need to extend the
> schema in every use case I am aware of. And in term of spec change,
> once we define the element, it is just another line to add it under
> Link.
> >
> > Thoughts?
> >
> > EHL
> >
> >
> >> -----Original Message-----
> >> From: drummond.reed@gmail.com [mailto:drummond.reed@gmail.com] On
> >> Behalf Of Drummond Reed
> >> Sent: Friday, November 06, 2009 5:37 PM
> >> To: Eran Hammer-Lahav
> >> Cc: xri@lists.oasis-open.org
> >> Subject: Re: [xri] <Type>
> >>
> >> Yup, IMHO it makes sense to go from <Type> to <Property
> >> type="uri-goes-here">value-if-not-empty<Property>.
> >>
> >> =Drummond
> >>
> >> On Friday, November 6, 2009, Eran Hammer-Lahav <eran@hueniverse.com>
> >> wrote:
> >>
> >>> I have been thinking about James' feedback regarding the need for
> >>>
> >> key/value pairs to describe resources, and I have been convinced
> that
> >> it makes more sense than the current Boolean approach taken with
> >> <Type>.
> >>
> >>> Right now, we can describe a resource using only a list of "tags".
> >>>
> >> While protocols can customize these to include configuration:
> >>
> >>> <Type>http://example.com/version/1.1</Type>
> >>> <Type>http://example.com/version/2.0</Type>
> >>>
> >>> Or
> >>>
> >>> <Type>http://example.com/popup/size/300,400</Type>
> >>>
> >>> This approach has been rejected by most members a few months back
> as
> >>>
> >> a bad extensibility model.
> >>
> >>> To make XRD useful we should either drop <Type> and leave it up to
> >>>
> >> individual extensions to define a container that is useful for them
> to
> >> describe the resource, or replace <Type> with a key/value element
> such
> >> as:
> >>
> >>> <Property key="http://example.com/version">1.1</Property>
> >>>
> >>> Ignore the element syntax, use of value or attributes or child
> >>>
> >> elements. The key will be a URI (just like <Type>) and the value a
> >> string. A key without value is the same as a <Type> declaration.
> >>
> >>> Thoughts?
> >>>
> >>> EHL
> >>>
> >>>
> >>> -------------------------------------------------------------------
> --
> >>> 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
> >>
> >>>
> >
> > ---------------------------------------------------------------------
> > 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
> >
> >
---------------------------------------------------------------------
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
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]