That will make it easier to also re-align other discovery-based specs
such as Yadis/OpenID to use the same syntax (i.e., LINK). Coming
without loss in semantics or restriction in architecture,
standardizing the syntax is a win.
On Tue, Nov 25, 2008 at 11:59 AM, Eran Hammer-Lahav <> wrote:
> As currently proposed:
>
> <XRD>
> <Service>
> <Type>http://example.com/relationship</Type>
> <MediaType>application/xml</MediaType>
> <URI>http://example.org/document</URI>
> </Service>
> </XRD>
>
> Is semantically equivalent to:
>
> HTTP Header:
> Link: <http://example.org/document>; rel="http://example.com/relationship";
> type="application/xml";
>
> HTML Element:
> <Link rel="http://example.com/relationship"
> href="http://example.org/document" type="application/xml" />
>
> Given that Link(s) are becoming the prominent mechanism for metadata on the
> web, I think there is great value in lining up XRD with that trend. So...
>
> I would like us to seriously consider renaming:
>
> Service --> Link
> Type --> Rel
> MediaType --> (unchanged)
> URI --> (unchanged)
>
> 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
>
>
--
--Breno
+1 (650) 214-1007 desk
+1 (408) 212-0135 (Grand Central)
MTV-41-3 : 383-A
PST (GMT-8) / PDT(GMT-7)
