RE: [xml-dev] 'is-a' Relationships in XML?

["stephengreenubl@gmail.com" <stephengreenubl@gmail.com>]

Like you say though, we need to cater for fine grained contexts.
Maybe CAM is useful in this case.
Also Schematron. They allow, I think, contexts beyond even parent
/ child. The context could be any 
Xpath.
A table with one column as an
XPath and another as an RDFXML fragment which refers, say to a
RDF or OWL ontology might do it.
Just inserting RDF into XSD might
only suffice for when the context is simple.

Context association files?

Stephen D Green


-----Original Message-----
From: stephengreenubl@gmail.com; stephengreenubl@gmail.com
Sent:  08/05/2010 9:02:51 pm
To: G. Ken Holman; xml-dev
Subject:  RE: [xml-dev] 'is-a' Relationships in XML?

Thanks Ken,

As I think about it, maybe the 
two way relationship is not essential. The schema could contain 
references to an RDF or OWL model or contain copies of extracts from 
the model. GRDDL gives a precedent by inserting RDFXML inside XSD 
schema annotations. If RDFXML fragments were placed in schema 
annotations it might provide enough mapping information. 
The other direction, ontology to schema, has merit but maybe is not 
essential. It would be one to many anyway. 
I agree a table might not be suitable for complex hierachies
though. 
What seems to me to be a key measure of success use case is that a query or other expression put i terms of the 'model' or 'ontology' classes and properties can return
results when run against the XML.
Maybe for this there has to be a way to start with the model so
the above might not be appropriate.
Unless, that is, you take the expression in SPARQL and a schema 
URL and get the result by finding the appropriate RDF expressions
 embedded in the schema and using the information of where they occur
in the schema to find the nodes in the XML needed to resolve the expression.
Anyway, RDFXML extracts in a schema together with an ontology
might let us associate 'iSa' and 
'hasA' relationships with elements and types in a schema. 
Then queries and constraints and assertions can be made and executed in terms of model semantics as distinct from  
structure alone.

Stephen D Green

-----Original Message-----
From: G. Ken Holman
Sent:  08/05/2010 1:45:40 pm
Subject:  RE: [xml-dev] 'is-a' Relationships in XML?

My gut feel is "no", because genericode is suitable for expressing a 
fully- or sparsely-populated keyed table.  Given that both ontologies 
and schemas are hierarchical, and the table and its key are flat, it 
may take too much shoehorning to suitably express context when 
ontology and schema members have the same names in different contexts.

For schemas expressed using naming and design rules such as UBL's 
NDRs, it starts to make more sense to use genericode because the 
uniqueness for the key is found in the parent/child relationship of 
elements.  Context is uniquely found in parents in UBL.  I can 
imagine two columns: parent and child, and the genericode key being 
the combination of the two, and then supplemental information about 
that unique context in the columns.

Of course in UBL there already exists a single key value for 
parent/child relationships, that being the dictionary entry name, but 
that may not be true for other schemas that have uniqueness in the 
parent/child combination.

For the next issue to go two ways as you ask, it would then be 
necessary in genericode to express every member of the ontology 
uniquely.  So it would depend on properties of the ontology to know 
if such a key-able value exists.

I hope this helps.

. . . . . . . . . . . Ken

At 2010-05-08 10:42 +0000, stephengreenubl@gmail.com wrote:
>Maybe OASIS open's genericode could be used for mapping two ways 
>between ontology and schema for the markup.
>
>Stephen D Green
>
>
>-----Original Message-----
>From: Stephen Green
>Sent:  06/05/2010 4:52:07 pm
>Subject:  Re: [xml-dev] 'is-a' Relationships in XML?
>
>Maybe, as with character sets, what we need are three kinds of artefacts
>to more completely define the markup
>
>1. schema (to define the structure and structural constraints)
>2. ontology (to define the semantics - the real world things and
>concepts to which the markup relates)
>3. mapping table (to map between 1. and 2.)
>
>Again, as with my analogy to character sets and their mapping tables,
>we'd ideally need to use the table when 'understanding' the underlying
>markup (as a table is used to 'understand' ASCII in its binary/hex form).
>
>In some cases it might be possible to combine 2. and 3. (or even 1. and 3.).
>E.g. maybe RDF's 'about' can be used somehow with a combination of URL
>(or the like) and XPath (or the like) - or just XQuery??? - to denote
>the mappings.
>Or maybe the RDF would want it the other way round to map XML to the
>meaning (mapping XPaths/XQueries to RDF classes and properties via 'about'?)
>But the lookups need, I think, to be able to work both ways, which might be
>more than can be done with RDF alone.
>
>Best regards
>
>Steve
>---
>Stephen D Green


--
Principles of XSLT for XQuery Writers: San Francisco,CA 2010-05-03
XSLT/XQuery/UBL/Code List training: Trondheim,Norway 2010-06-02/11
Vote for your XML training:   http://www.CraneSoftwrights.com/x/i/
Crane Softwrights Ltd.          http://www.CraneSoftwrights.com/x/
G. Ken Holman                 mailto:gkholman@CraneSoftwrights.com
Male Cancer Awareness Nov'07  http://www.CraneSoftwrights.com/x/bc
Legal business disclaimers:  http://www.CraneSoftwrights.com/legal


_______________________________________________________________________

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@lists.xml.org
subscribe: xml-dev-subscribe@lists.xml.org
List archive: http://lists.xml.org/archives/xml-dev/
List Guidelines: http://www.oasis-open.org/maillists/guidelines.php