Hello all,
I have the following mapping command:
map:rel_GatewayNodes_DeploymentSiteId__ref a d2rq:PropertyBridge;
d2rq:belongsToClassMap map:dbo_GatewayNodes; d2rq:property
inws:hasMeasurementSite; d2rq:refersToClassMap map:dbo_DeploymentSites;
d2rq:join "dbo.GatewayNodes.DeploymentSiteId => dbo.DeploymentSites.Id";
.
which produces the following RDF code:
<rdf:Description rdf:about="http://www.co-ode.org/ontologies/ont.owl#g7";>
<inws:hasMeasurementSite
rdf:resource="http://www.co-ode.org/ontologies/ont.owl#d7"/>
<rdf:type
rdf:resource="http://www.co-ode.org/ontologies/ont.owl#GatewayNode"/></rdf:Description>
The generated ontology appears correct in Altova SemanticWorks environment. But
when I open the generated ontology in Protege v3.5 beta the upper mentioned
relationships are disappearing. Maybe this is because that d2rq translates
tables to rdf:class instead of owl:class or maybe its something else that you
may help me. I have simulated the expected result in Protege v3.5 which in RDF
code has the following representation:
<inws:GatewayNode rdf:ID="g7"> <inws:hasCentralMonitoringNode
rdf:resource="#c3"/></inws:GatewayNode>
Is there any possibility to make the mapping in such a way which will return me
a supported code for running in Protege 3.x envirnment?
Thank you in advance.
-Edmond ------------------------------------------------------------------------------
The Go Parallel Website, sponsored by Intel - in partnership with Geeknet,
is your hub for all things parallel software development, from weekly thought
leadership blogs to news, videos, case studies, tutorials, tech docs,
whitepapers, evaluation guides, and opinion stories. Check out the most
recent posts - join the conversation now. http://goparallel.sourceforge.net/
_______________________________________________
d2rq-map-devel mailing list
d2rq-map-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/d2rq-map-devel
