Home. 
.

transparent

transparent

transparent

Altova Mailing List Archives


Re: design pattern for nested xml?

From: Andy Dingley <dingbat@----------.--->
To: NULL
Date: 8/4/2009 3:14:00 AM
On 3 Aug, 20:23, lawpoop <lawp...@gmail.com> wrote:
> I have two questions about the 'best' way to design an xml document.

For your example, I wouldn't use XML, I'd go straight to RDF, RDF
Schema and maybe even OWL.

Your offices aren't a "tree", they're a graph (mulltiple roots, not a
simple branching tree). XML is poor at these.

Your identifier structure is crucial to success here. Use URIs.

Typing (as practised by RDFS) would be extremely useful to you.

The downside of using RDF is that is does rather restrict the
implementation language to Java (or Scala, if you're fashionable!) as
that's where the good RDF toolsets are  (start by looking at Jena).


transparent
Print
Mail
Like It
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.

.
.

transparent

transparent