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 t
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
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
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
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 InverseFunc
