Hello Tim,
The properties should be used to connect the mapped instances. However,
one of the following might have happened:
- Does the XML instance file validate against the XML schema file in a
validator tool like XMLSpy or Oxygen?
- In the Help pages, "Import XSD" page describes "Known Issues". Does
your XML schema file contain any items covered in Known Issues? If it
does, then the mapping might not have worked for those items.
Another way to try mapping the XML instance file is right-clicking on it
in Navigator, and then click on TopBraid (Semantic XML Documents). You
can then select the ontology that you imported from the XML Schema file
in the "Create .sxml file ....." dialog.
If you want, you can send the XML instance the XML schema files offline
to us, so we can check why there are missing mappings.
Gokhan
On 3/1/2012 10:38 AM, Tim Smith wrote:
Hi,
I'm attempting to import an XML instance and schema file into TBC.
I've imported the schema and generated a .ttl (OWL) model from the schema
I created another file and imported the .ttl ontology and an instance
file.
I'm expecting to see the xml instance data to be mapped into ontology.
For the most part this is true - the classes have instances. However,
even though the ontology seems to contain the properties necessary to
directly connect instances and the properties are attached to the
classes via restrictions, the instances are still connected using the
composite:child relationship instead of using the properties created
during the .xsd import.
Is this supposed to be the case? I was expecting the properties to be
used to connect instances.
If you've ever spent much time importing XML files, you understand how
onerous it is to query an XML file using the composite:child
relationships especially when your hierarchy is 6+ layers deep :)
Thanks,
Tim
--
You received this message because you are subscribed to the Google
Group "TopBraid Suite Users", the topics of which include Enterprise
Vocabulary Network (EVN), TopBraid Composer,
TopBraid Live, TopBraid Ensemble, SPARQLMotion and SPIN.
To post to this group, send email to
topbraid-users@googlegroups.com
To unsubscribe from this group, send email to
topbraid-users+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/topbraid-users?hl=en
--
You received this message because you are subscribed to the Google
Group "TopBraid Suite Users", the topics of which include Enterprise Vocabulary
Network (EVN), TopBraid Composer,
TopBraid Live, TopBraid Ensemble, SPARQLMotion and SPIN.
To post to this group, send email to
topbraid-users@googlegroups.com
To unsubscribe from this group, send email to
topbraid-users+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/topbraid-users?hl=en
