Home. 
.

transparent

transparent

transparent

Altova Mailing List Archives


Schema design and attribute for ontology identification

From: "Alexander Johannesen" <alexander.johannesen@-----.--->
To: "XML Developers List" <xml-dev@-----.---.--->
Date: 11/9/2007 4:50:00 AM
Hi all,

I'm creating a very simple pipeline schema as a basis for various
SOA/ROA development projects, and I've been pondering a number of
things in this process, especially what the best way is to identify
that a certain sub-tree of an XML belongs to a certain ontology (an
ontology here is loosely defined as a vocabulary, and not as a schema
per se). Now before we head down namespaces let's make it clear that
this is not about mixed content model but about identification. I've
pondered different ways to do it (In all these examples I've use URI's
as the identifier, but they might be uid's of any kind, of course) ;

 <container xmlns="http://some.ontology"> ... </container>

Namespaces here feels wrong to me as the content of the <container>
may not even have a schema (yet). It's up to applications to deal with
content they know about, and I'm not sure I want to a) imply namespace
handling in all our tools pr. default, and b) most of our tools will
use simple but application specific XML and I don't see the benefits
to forcing everyone to also do schema work for mostly non-validating
reasons.

 <container id="http://some.ontology"> ... </container>
 <container oid="http://some.ontology"> ... </container>

The plain @id clashes with xml:id for me, and a great number of tools
will assume that's what they are. And that's not necessarily wrong.
The @oid seems quite non-descript yet workable. Perhaps call the
attribute @ontology or something similar?

Further to this is the notion that a container of XML contains data of
some kind, ala ;

 <container type="http://some.ontology"> ... </container>

Or one can pull an RDF (introducing namespaces where we might not want them) ;

 <container rdf:about="http://some.ontology"> ... </container>

Or Topic Maps (again, introducing namespaces where we might not want them) ;

 <container xtm:psi="http://some.ontology"> ... </container>

Thoughts? What do you people do these days to identify that a sub-tree
belongs to some notion that isn't necessarily another schema?


Alex
-- 
---------------------------------------------------------------------------
 Project Wrangler, SOA, Information Alchemist, UX, RESTafarian, Topic Maps
------------------------------------------ http://shelter.nu/blog/ --------


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