Ever since Eran explained this at the IIW and XRI TC F2F sessions two weeks
ago, I've been wondering this same thing. Given that XRDS/XRD has probably
penetrated <1% of its eventual installed user base if successful, now's the
time to make this change if ever.
I find the direct mapping of semantics compelling, especially as XRD spreads
out to a much larger audience of developers.
Question: would <Type> become <Rel> under the parent XRD element as well, or
would that remain <Type>?
=Drummond
> -----Original Message-----
> From: Eran Hammer-Lahav [mailto:]
> Sent: Tuesday, November 25, 2008 12:00 PM
> To:
> Subject: [xri] Aligning XRD with Link (Header/Element)
>
> 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
