Altova Mailing List Archives
>xml-dev Archive Home
>Recent entries
>Thread Prev - RE: [xml-dev] xml:href, xml:rel and xml:type
>Thread Next - RE: [xml-dev] xml:href, xml:rel and xml:type
Re: [xml-dev] xml:href, xml:rel and xml:type
To: xml-dev@-----.---.---
Date: 4/16/2012 3:52:00 PM
> I'm not suggesting that. I'm suggesting @xml:rel as a way of capturing > the name of the relationships: > > <factory xml:href="http://example.com/willy-wonkas-chocolate-factory/location" xml:rel="location" xml:type="application/xml"> > <name>Willy Wonka's Chocolate Factory</name> > <products> > <product xml:href=""http://example.com/willy-wonkas-products/wonka-bar" xml:rel="describedby" xml:type="application/xml"><name>Wonka Bar</name> > </products> > </factory > Are these href values URIs or URLs? I get the impression, because you're talking about REST, that they can be dereferenced. If that's the case, then I'm sceptical about whether this information belongs in the XML. The identity of a product is not the same as the address of a web service that can provide information about the product. There's too much muddling of layers going on here. The application should get information about products by combining two pieces of information: knowledge of the product's identifier, and knowledge of a service that provides trustworthy information about products. I don't think it's right to bundle those two things inseparably together. Michael Kay Saxonica _______________________________________________________________________ XML-DEV is a publicly archived, unmoderated list hosted by OASIS to support XML implementation and development. To minimize spam in the archives, you must subscribe before posting. [Un]Subscribe/change address: http://www.oasis-open.org/mlmanage/ Or unsubscribe: xml-dev-unsubscribe@l... subscribe: xml-dev-subscribe@l... List archive: http://lists.xml.org/archives/xml-dev/ List Guidelines: http://www.oasis-open.org/maillists/guidelines.php
Disclaimer
These Archives are provided for informational purposes only and have been generated directly from the Altova mailing list archive system and are comprised of the lists set forth on www.altova.com/list/index.html. Therefore, Altova does not warrant or guarantee the accuracy, reliability, completeness, usefulness, non-infringement of intellectual property rights, or quality of any content on the Altova Mailing List Archive(s), regardless of who originates that content. You expressly understand and agree that you bear all risks associated with using or relying on that content. Altova will not be liable or responsible in any way for any content posted including, but not limited to, any errors or omissions in content, or for any losses or damage of any kind incurred as a result of the use of or reliance on any content. This disclaimer and limitation on liability is in addition to the disclaimers and limitations contained in the Website Terms of Use and elsewhere on the site.

