Mark, Probably, some artefact had been hanging around as you said. When you specify to use XSD datatypes rather than user-defined datatypes, the generated restrictions in the schema ontology uses XSD datatypes as ranges rather than the user-defined datatypes. Semantic XML uses these restrictions to assign datatypes to literals. However, the restriction still keeps an annotation to the user-defined datatype for reference in this case, which doesn't have any effect in Semantic XML mapping.
Gokhan On Thu, Jun 14, 2012 at 1:39 PM, Mark Colquhoun < [email protected]> wrote: > Update... > > This works now, it must have been some artefact hanging around. > > Regards, > Mark. > > > On Thursday, June 14, 2012 7:42:26 PM UTC+10, Mark Colquhoun wrote: >> >> Hi Gokhan, >> >> I tried using that option and the XSD to OWL mapping showed the >> properties as string types however when I import the XML, it still creates >> the values as the XML data types rather than the XSD datatypes specified in >> the mapping. I am wondering if there is some artefact hanging around >> causing this or if it is still possible for the import to generate the RDF >> as a different datatype compared to the mapping? >> >> Regards, >> Mark. >> >> On Thursday, June 14, 2012 6:12:08 PM UTC+10, Gokhan Soydan wrote: >>> >>> Mark, >>> >>> You could generate another ontology using XSD to OWL importer which >>> purely assigns XSD datatypes for literals. The XSD to OWL importer has an >>> option called "Use only XSD datatypes for datatype properties and >>> literals". After generating a "schema" ontology using that option, you >>> could use it in Semantic XML mapping. >>> >>> If the above solution doesn't work for you, then for sameness, you would >>> need to use a SPARQL query with spif:cast function, which casts a given >>> datatype to a literal. The following example generates a ?y literal with >>> value of ?x with xsd:string datatype: >>> >>> BIND( spif:cast( ?x, xsd:string ) AS ?y) ) >>> >>> Gokhan >>> >>> >>> On Thu, Jun 14, 2012 at 10:39 AM, Mark Colquhoun < >>> [email protected].**au <[email protected]>>wrote: >>> >>>> Hi, >>>> >>>> I am trying to infer sameness across two different sources of data by >>>> using an InverseFunctionalProperty. One of the sources of data is being >>>> imported as XML using a XML/RDF mapping imported using a XSD document. For >>>> this datasource, the property that I would like to use as >>>> the InverseFunctionalProperty is of a data type generated from the xsd >>>> import. That is, to compare a value from the XML datasource, I need to use >>>> something like "4120"^^<http://www.mydomain.** >>>> com.au/ontology/mapping/etdcs#**SiteDatatype<http://www.mydomain.com.au/ontology/mapping/etdcs#SiteDatatype>>. >>>> I think becuase of this, I am having trouble produce sameAs relationships >>>> through my InverseFunctionProperty as the other property I am comparing is >>>> a string (i.e. "4120"). I did note that the SiteDataType is a subClassOf >>>> xsd:string however I'm not sure what I have to run to have the SiteDatatype >>>> to be inferred as xsd:string? >>>> >>>> I'm not sure if I have explained this very well above but does anyone >>>> have any suggestions on how to modify my two properties so that they can be >>>> compared to each other to determine equivalence? >>>> >>>> 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 >>>> topbraid-users@googlegroups.**com <[email protected]> >>>> To unsubscribe from this group, send email to >>>> topbraid-users+unsubscribe@**googlegroups.com<topbraid-users%[email protected]> >>>> For more options, visit this group at >>>> http://groups.google.com/**group/topbraid-users?hl=en<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 > -- 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
