Doesn't this just mean we have to be a little more careful where we put the namespace? <owl:Class ID="ActionTime" xmlns:xs="http://www.w3.org/2001/XMLSchema" <owl:equivalentClass> <owl:Restriction> <owl:onProperty rdf:resource="#hasTime"/> <owl:someValuesFrom rdf:parseType="Literal"> <xs:simpleType xmlns:my="http://example.org/myDatatypes" > <--- the namespace is here now <xs:restriction base="my:precision3"> <xs:minInclusive value="305.200" /> <xs:maxInclusive value="310.199" /> </xs:restriction> </xs:simpleType> </owl:someValuesFrom> </owl:Restriction> </owl:equivalentClass> </owl:Class> BTW, Bijan, why would you create a different data type for each time interval you annotate, rather than defining a single "interval" datatype and then using a bunch of values from it? -Alan On Nov 19, 2007, at 4:44 PM, Jeremy Carroll wrote: > In today's telecon I took an action to explain some issues. > > I wrote a Wiki page > > > http://www.w3.org/2007/OWL/wiki/XSDinRDFXML > > which might do this. > > I try to iilustrate an OWL 1.0 restriction on a datarange defined > using an in-line unnamed XML Schema datatype. > > JeremyReceived on Tuesday, 20 November 2007 05:58:21 GMT
This archive was generated by hypermail 2.2.0+W3C-0.50 : Tuesday, 8 January 2008 14:13:27 GMT