Hi Dimitrios,
I can confirm the behavior, and did not come up with a "quick"
work-around. I have filed this as an enhancement request in our internal
bug tracker for the time being. We will let you know in case this is
fixed. Meanwhile I am afraid you'd need to post-process these files or
merge them into one namespace etc.
Thanks
Holger
On 2/05/2017 5:52, Dimitrios Tzannetos wrote:
Hi everyone.
I have been experimenting with Semantic XML in order to create RDF
instances that correspond to the contents of an XML file. I discovered
an issue when trying to generate a Schema Ontology file with matching
Semantic XML annotations using the appropriate XSD files. It seems
that for every class, all generated properties reside in the same
namespace. However, it might be the case that a tag in the XML file
can have nested 'child' Datatype elements that are defined in a
different namespace. Instead of attaching a Datatype property to the
parent class, the Import Tool creates an owl:ObjectProperty in the
namespace of the 'parent' that points to a Datatype Class in the
child's namespace. However, the latter class is not defined anywhere
and as a result the RDF instances are not populated correctly. I have
attached two XSD files and a minimal XML sample that generates this
issue.
In my example, for the sample XML
<?xml version="1.0" encoding="UTF-8"?>
<oadr:oadrDistributeEvent ei:schemaVersion="2.0b"
xsi:schemaLocation="http://openadr.org/oadr-2.0b/2012/07 oadr_20b.xsd"
xmlns:pyld="http://docs.oasis-open.org/ns/energyinterop/201110/payloads"
xmlns:oadr="http://openadr.org/oadr-2.0b/2012/07" >
<pyld:requestID>REQ_12345</pyld:requestID>
</oadr:oadrDistributeEvent>
the Import Tool generates the following definition for
oadr:oadrDistributeEvent :
<https://lh3.googleusercontent.com/-Hx4cA4WNe38/WQeO1n1x99I/AAAAAAAAADc/GEvNV0BNV2Irt9_ZVok0dkZhDmSirCnZACLcB/s1600/Topbraid_1.PNG>
The highlighted payload:RequestID is not defined
I was hoping that the Import Tool would define the Datatype property
in the child namespace, with the appropriate range, such as xsd:string
in my example and attach it to the parent Class (shown below).
<https://lh3.googleusercontent.com/-T7H09U2f7bU/WQePryEFl9I/AAAAAAAAADo/xSfoyshcRFgCVAqmZImTOqWUQr4Vs7s0gCLcB/s1600/Topbraid_2.PNG>
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 topbraid-users@googlegroups.com
---
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 topbraid-users+unsubscr...@googlegroups.com
<mailto:topbraid-users+unsubscr...@googlegroups.com>.
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 topbraid-users@googlegroups.com
---
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 topbraid-users+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.