Thanks for the reply. I do not recall saying anything about
dtype:numericUnion in my mails and as far as I can see qudt:numericValue is
defined with an xsd:double range. That said, I can see that there are
instances of qudt:numericValue that follow the conventions you and I both
used, but
On 7/31/2015 2:23, Jack Hodges wrote:
Hello Holger,
Yes, mostly for the use of datatypes in properties. Well, last night
and this morning the problem is with an owl:DatatypeProperty in QUDT,
qudt:numericValue, whose rdfs:range is xsd:double. So it is a good
example of a custom property but
Hello Holger,
Yes, mostly for the use of datatypes in properties. Well, last night and
this morning the problem is with an owl:DatatypeProperty in QUDT,
qudt:numericValue, whose rdfs:range is xsd:double. So it is a good example
of a custom property but uses a standard datatype.
I created a
And for non-standard properties (such as those created by us), maybe an
option to provide such a legal default value definition for others.
On Wednesday, July 29, 2015 at 4:57:22 PM UTC-7, Jack Hodges wrote:
Often times I find myself in a situation where I am putting a value into a
form
Which datatypes do you have in mind? I assume xsd:string and any numeric
datatypes are not a problem. I can imagine that xsd:date and
xsd:dateTime are. What else?
Also, could you give me some example of user-defined datatypes that you
have created? With OWL 2 syntax?
(On the more general
