<Rel> & <ResourceType> (was Proposed XRD schema)

["Drummond Reed" <drummond.reed@cordance.net>]

+1 to Brian's point below. However his example raises one question that I
hadn't realized the importance of before. 

Eran, in the context of a <Link> element, can you concisely explain
difference between <Rel> and <ResourceType>?

I worry that future XRD consuming application developers are going to become
confused as to when they should be looking for a <Rel> and when they should
be looking for a <ResourceType> and when for both. 

I ask partly because the predecessor XRDS format only had a <Type> element,
and that seemed to do the job for everything, so I expect lots of questions
about why it was expanded into two elements. I'm cool with it if we have a
good, clean explanation which translates into clear best practices advice,
so that's why I'm asking.

=Drummond 

> -----Original Message-----
> From: Brian Eaton [mailto:beaton@google.com]
> Sent: Sunday, February 15, 2009 11:08 PM
> To: njones@ouno.com
> Cc: xri@lists.oasis-open.org
> Subject: Re: [xri] Proposed XRD schema
> 
> On Fri, Feb 13, 2009 at 7:28 PM,  <njones@ouno.com> wrote:
> > How would xsd:any work?
> 
> Libraries would wander through the XML looking for the appropriate
> Link element based on Rel and ResourceType.  Once they found it, they
> would return the entire Link element, and application code can then do
> further investigation.
> 
> The schemas for individual Link types would include whatever XML
> elements are necessary to supply interesting metadata.  For example:
> 
> <Link priority="10">
>        <Rel>
> http://some.URI.that.indicates.relationsip.is.self.or.sub.service.com
> </Rel>
>        <ResourceType> http://spec.openid.net/auth/2.0/ux/popup
> </ResourceType>
>        <height>500px</height>
>        <width>450px</width>
> </Link>
> 
> I'm completely appalled by the notion of encoding that kind of
> metadata as additional Rel or ResourceType or query string elements.
> We've got XML parsers.  We should use them.
> 
> Cheers,
> Brian
> 
> ---------------------------------------------------------------------
> 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