mw.data.representation Missing OWL DataRestrictions

[amedranogil]

There aren't specialised TypeRestrictions (maybe TypeMap too) for:

• owl:real (maybe Double restrictions apply)
• owl:rational (maybe Double restrictions apply)
• xsd:decimal
• xsd:nonNegativeInteger (maybe Integer restrictions apply)
• xsd:nonPositiveInteger(maybe Integer restrictions apply)
• xsd:positiveInteger (maybe Integer restrictions apply)
• xsd:negativeInteger (maybe Integer restrictions apply)
• xsd:short (maybe Integer restrictions apply)
• xsd:byte (maybe Integer restrictions apply)
• xsd:unsignedLong (maybe Long restrictions apply)
• xsd:unsignedInt (maybe Integer restrictions apply)
• xsd:unsignedShort (maybe Integer restrictions apply)
• xsd:unsignedByte (maybe Integer restrictions apply)
• xsd:normalizedString (maybe String restrictions apply)
• xsd:token (maybe String restrictions apply)
• xsd:language (or is it?)
• xsd:Name (maybe String restrictions apply)
• xsd:NCName (maybe String restrictions apply)
• xsd:NMTOKEN (maybe String restrictions apply)
• xsd:hexBinary (maybe Base64Binary restrictions apply)
• xsd:dateTime
• xsd:dateTimeStamp (maybe dateTime restrictions apply)

Missing Facets:

• Pattern (string/IRI)
• TotalDigits (Decimal) (my bad, this is defined in OWLAPI but not OWL2)
• FractionDigits (my bad, this is defined in OWLAPI but not OWL2)
• LangRange

[amedranogil]

check quick reference for Built-in Datatypes, and default facets of OWL2.

[cstockloew]

see TypeMapper:

xsd:nonNegativeInteger : class NonNegativeInteger
xsd:language : Java class Locale is used
xsd:dateTime : Java class XMLGregorianCalendar is used
xsd:decimal : Java class BigDecimal is used

[amedranogil]

xsd:nonNegativeInteger : class NonNegativeInteger

Will current integer restrictions work?

xsd:language : Java class Locale is used

so it is there! we also have a languaje ontology which might be redundant!

xsd:dateTime : Java class XMLGregorianCalendar is used

we still are missing the min/max inclusive/exclusive restrictions for this datatype.

xsd:decimal : Java class BigDecimal is used

will current Integer restrictions work? I guess we need to extend it to be able to use them there.

[cstockloew]

xsd:nonNegativeInteger : class NonNegativeInteger

Will current integer restrictions work?

Probably not, because Integer != NonNegativeInteger

xsd:decimal : Java class BigDecimal is used

will current Integer restrictions work? I guess we need to extend it to be able to use them there.

Probably not, because Integer != BigDecimal

xsd:dateTime : Java class XMLGregorianCalendar is used

we still are missing the min/max inclusive/exclusive restrictions for this datatype.

yes

xsd:language : Java class Locale is used

so it is there! we also have a languaje ontology which might be redundant!

And we also have the class org.universAAL.middleware.rdf.LangString ;-)

I don't think they are redundant (maybe parts of it), because they are used in different contexts. Consider the 2 examples

1. define that a person is speaking a language
   foo:Paul bar:speaks "english"

2. provide a Sting in different languages
   LightSource rdf:label "light source"@en, "Lichtquelle"@de;

The first one needs a definition of languages at ontological level (your language ont). The second one is part of RDF serialization (props set with LangString).

Maybe the use of Locale could be reviewed, especially since it only defines a very restricted set of languages..