Altova Mailing List Archives


Re: Standard way to express object, not resource, rels in XML?

From: Stefan Haustein <haustein@---.--.------------.-->
To: Mike Brown <mbrown@----.----.--->
Date: 8/21/2000 5:29:00 AM
Mike Brown wrote:
> 
> (...) However, I am not interested in saying "doc1.xml is related
> to doc2.xml". Rather, I want to say "object foo1 (the thing doc1.xml's data
> describes) is related to object foo2 (the thing doc2.xml's data describes)".
> I do not want to refer to doc1.xml or doc2.xml at all when expressing this
> relationship; I want to refer to only the foo1 and foo2 identifiers.
> 
> RDF seems to be concerned with metadata like this, but a cursory inspection
> of what RDF covers made it look like it, too, was more concerned with
> "resources" like documents. 

Did you already take a look at the SOAP serialization 
format (SOAP spec, chapter five, http://www.w3.org/TR/SOAP/)?

If your data is object oriented, this may be an
approach more suitable than RDF. Since RDF is more 
property centric than object oriented,
mapping object definitions to an RDF schema
is a bit difficult. 

Best,

Stefan

-- 
Stefan Haustein             
Univ. Dortmund, FB 4, LS 8   tel: +49 231 755 2499
Baroper Str. 301             fax: +49 231 755 5105
D-44221 Dortmund (Germany)   www-ai.cs.uni-dortmund.de

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.