To help me better understand your set up (without seeing the actual
script this is a bit tricky):
If you have a SPINMap that operates on the output of the SXML loader, I
assume you have an Ontology that defines classes and properties together
with sxml: annotations that link them to the corresponding XML elements?
Then, I assume these classes are visible in the input graph to the
sml:ConvertXMLToRDF module, so that the script is instantiating the same
classes and properties, with their stable URIs?
Maybe you can share at least a screenshot of the flow in your script?
Thanks,
Holger
On 29/03/2017 12:58, Dimitrios Tzannetos wrote:
Holger,
Thank you for the prompt reply.
The second approach (different namespace) by itself does not cause any
problems. However, later in the SPARQLMotion script I created, these
generated instances are mapped to another ontology using SPINMap. The
mapping - assuming a unique localname - makes use of the "change
namespace" functionality in order to create the URI for the instance
of the "destination" class. Therefore, the uniqueness provided by
using different namespaces for the instances of the "source" class
would be lost. I guess I have to manipulate the namespace in a
different way than just using "change namespace" to ensure that the
mapped instances also have unique URIs. Any suggestions would be
greatly appreciated.
Best Regards,
Dimitrios
On Tuesday, March 28, 2017 at 5:28:09 PM UTC-7, Holger Knublauch wrote:
Hi Dimitrios ,
the second approach (use different namespace) sounds easy and
makes most sense to me. Where does it cause problems?
Holger
On 29/03/2017 9:01, [email protected] <javascript:> wrote:
Hi Everyone!
I am a CMU graduate student in the research group of Dr. Steven
Ray. I am working on a SPARQLMotion script that takes in an XML
as a string, converts it to instances of classes in an ontology
using ConvertXMLtoRDF module and then stores it to a file. The
aforementioned ontology has been automatically imported from XSD
schemata and is annotated with the appropriate sxml elements as
described in Help > TopBraid Composer > Import and
Export,Creating, Importing, Querying, Saving XML documents with
Semantic XML.
When invoking the web-service call for the first time, everything
works fine - instances are created having URIs such as r, r-2-0,
r-2-0-0,etc. However,
when running the script again with an XML input string
representing different instances, the same URIs (r, r-2-0,...)
are built and as a result the previous instances are overwritten.
I have experimented with to two partial solutions to the problem :
1. use an ApplyConstruct module after the ConvertXMLtoRDF
output to manually create "unique" URIs
2. each time use a different namespace in the ConvertXMLtoRDF
module to end up with distinct qnames
Is there another and easier way to create instances with unique
URIs using Semantic XML?
Best Regards,
Dimitrios Tzannetos
--
You received this message because you are subscribed to the
Google Group "TopBraid Suite Users", the topics of which include
the TopBraid Suite family of products and its base technologies
such as SPARQLMotion, SPARQL Web Pages and SPIN.
To post to this group, send email to [email protected]
<javascript:>
---
You received this message because you are subscribed to the
Google Groups "TopBraid Suite Users" group.
To unsubscribe from this group and stop receiving emails from it,
send an email to [email protected] <javascript:>.
For more options, visit https://groups.google.com/d/optout
<https://groups.google.com/d/optout>.
On Tuesday, March 28, 2017 at 5:28:09 PM UTC-7, Holger Knublauch wrote:
Hi Dimitrios ,
the second approach (use different namespace) sounds easy and
makes most sense to me. Where does it cause problems?
Holger
On 29/03/2017 9:01, [email protected] <javascript:> wrote:
Hi Everyone!
I am a CMU graduate student in the research group of Dr. Steven
Ray. I am working on a SPARQLMotion script that takes in an XML
as a string, converts it to instances of classes in an ontology
using ConvertXMLtoRDF module and then stores it to a file. The
aforementioned ontology has been automatically imported from XSD
schemata and is annotated with the appropriate sxml elements as
described in Help > TopBraid Composer > Import and
Export,Creating, Importing, Querying, Saving XML documents with
Semantic XML.
When invoking the web-service call for the first time, everything
works fine - instances are created having URIs such as r, r-2-0,
r-2-0-0,etc. However,
when running the script again with an XML input string
representing different instances, the same URIs (r, r-2-0,...)
are built and as a result the previous instances are overwritten.
I have experimented with to two partial solutions to the problem :
1. use an ApplyConstruct module after the ConvertXMLtoRDF
output to manually create "unique" URIs
2. each time use a different namespace in the ConvertXMLtoRDF
module to end up with distinct qnames
Is there another and easier way to create instances with unique
URIs using Semantic XML?
Best Regards,
Dimitrios Tzannetos
--
You received this message because you are subscribed to the
Google Group "TopBraid Suite Users", the topics of which include
the TopBraid Suite family of products and its base technologies
such as SPARQLMotion, SPARQL Web Pages and SPIN.
To post to this group, send email to [email protected]
<javascript:>
---
You received this message because you are subscribed to the
Google Groups "TopBraid Suite Users" group.
To unsubscribe from this group and stop receiving emails from it,
send an email to [email protected] <javascript:>.
For more options, visit https://groups.google.com/d/optout
<https://groups.google.com/d/optout>.
--
You received this message because you are subscribed to the Google
Group "TopBraid Suite Users", the topics of which include the TopBraid
Suite family of products and its base technologies such as
SPARQLMotion, SPARQL Web Pages and SPIN.
To post to this group, send email to [email protected]
---
You received this message because you are subscribed to the Google
Groups "TopBraid Suite Users" group.
To unsubscribe from this group and stop receiving emails from it, send
an email to [email protected]
<mailto:[email protected]>.
For more options, visit https://groups.google.com/d/optout.
--
You received this message because you are subscribed to the Google Group "TopBraid
Suite Users", the topics of which include the TopBraid Suite family of products and
its base technologies such as SPARQLMotion, SPARQL Web Pages and SPIN.
To post to this group, send email to [email protected]
---
You received this message because you are subscribed to the Google Groups "TopBraid Suite Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
For more options, visit https://groups.google.com/d/optout.
