i can deal with it - (have done) but was just a shame not to be able to
access the internal components that seem to do this job anyway.
On Friday, 16 August 2019 09:08:59 UTC+10, Holger Knublauch wrote:
>
> In addition to what Irene said, if the pre-built tooling doesn't fit your
> needs, ther
In addition to what Irene said, if the pre-built tooling doesn't fit
your needs, there is always the option of going through 3rd party
technologies such as XSL transformations (there is a SM module to
execute those if you have a script to produce RDF/XML).
Holger
On 15/08/2019 22:38, Irene P
unfortunately in a programmatic context "first import XSD" is not really
specific enough to interpret - it could mean
1) use LoadFromXML and ConvertXMLtoRDF sequence to get into current query
graph
2) do it as a manual step in advance (not relevant in this context)
3) inject is as an owl:import
Rob,
As I understand it, Holger’s recommendation is to first import XSD. This will
create annotated ontology.
If you do not have XSD, then Import XML file and delete all instances from the
resulting RDF, leaving only classes and properties.
This will automatically create the annotated ontology
I have tried reading this a few times and am still a little lost...
1) I dont see how the context "If a process ontology is used to control
the Semantic XML mapping" relates the to arguments for
sml:ConvertXMLToRDF (sm:Module)
Converts an arbitrary XML input document into an RDF graph usin
Hi Rob,
if you have already existing classes and properties with sxml:
annotations then the algorithm should reuse those instead of creating
new classes. See comment at sml:ConvertXMLToRDF:
Converts an arbitrary XML input document into an RDF graph using the
Semantic XML mapping approach. Th
