Mark, Sorry, it took us a while to get back on this question. Yes, you discovered the best solution to control how XML should be mapped to RDF - using an XSD to OWL import. After you import from XSD to OWL, then when opening an XML file using Semantic XML, you could use specify the ontology that was imported from XSD as the "schema" ontology to drive the mapping from XML to RDF.
You can also build your own "schema" ontologies by looking at example XSD to OWL imports, so you don't always need an XSD to drive the mapping. I think, you already discovered the related Help page at: TopBraid Composer > Importing Data Sources > Import external information > XSD to OWL Importer Gokhan On Wed, Jun 13, 2012 at 1:57 AM, Mark Colquhoun < [email protected]> wrote: > Hi, > > I haven't heard a reply on this topic so I thought I would post that I did > find a solution based on creating an XSD and importing that into TBC to > produce the XML/RDF mapping. This seems to have worked well for my > purposes. If you could let me know if that is the best solution to my > problem (as I have many similar imports I will need to perform) it would be > greatly appreciated. > > Regards, > Mark. > > > On Tuesday, 12 June 2012 14:58:47 UTC+10, Mark Colquhoun wrote: >> >> Hi, >> >> I am using the Semantic XML capabilities of TBC. I am just trying to >> confirm that one of the assumptions of Semantic XML is that Datatype >> Properties must be implemented as XML attributes? I have an XML file >> where all the data is represented as XML elements therefore my >> Datatype Properties are implemented as child elements. Is there a way >> to import an XML file so that I can build an Ontology that has >> DataType properties implemented as XML elements instead of attributes? >> >> <Field> >> <Uid>173</Uid> >> <Version>7</Version> >> <Name>GENERAL - AUSTRALIA</Name> >> <Description>General Australia wide</Description> >> <Area> >> <Uid>18</Uid> >> <Version>6</Version> >> <Name>NONE (AU)</Name> >> <Description /> >> <Basin> >> <Uid>13</Uid> >> <Version>11</Version> >> <Name>[AUST] GENERAL</Name> >> <Description>Across Australia either pertaining to a number of >> Basins or no Basin at all.</Description> >> <Location> >> <Uid>1</Uid> >> <Version>2</Version> >> <Name>Australia</Name> >> <Description>Prefix A</Description> >> <Prefix>A</Prefix> >> </Location> >> </Basin> >> </Area> >> <Site>1000</Site> >> <LocationSite>A-1000</**LocationSite> >> </Field> >> >> Regards, >> Mark. > > -- > 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 > [email protected] > To unsubscribe from this group, send email to > [email protected] > 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 [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/topbraid-users?hl=en
