- From: Polleres, Axel <axel.polleres@siemens.com>
- Date: Wed, 3 Oct 2012 09:19:45 +0200
- To: "public-owl-comments@w3.org" <public-owl-comments@w3.org>
- Message-ID: <9DA51FFE5E84464082D7A089342DEEE80149E35DFF89@ATVIES9917WMSX.ww300.siemens.net>
Hi, I have some question on the primer example on DataRanges, cf. http://www.w3.org/TR/2008/WD-owl2-primer-20080411/#Adatarange The prose text says "For example, we might have Teenager as those people whose age is an integer that is at least 13 but less than 20, Adult as those people whose age is at least 21, and Child as those people whose age is in the complement of adult ages." Class: Teenager EquivalentClass: Person and hasAge some integer[>= 13 , < 20] Class: Adult EquivalentClass: Person and hasAge some integer[>= 21] Class: Child EquivalentClass: Person and not ( hasAge some integer[>= 21] ) As it stands, this seems to allow several ages per person - one of which is in the defined range. IMO, it would be more intuitive to use for the first two lines "all" instead of "some" here plus stating that age is functional (each person has exactly one age, wouldn't it? Not a big deal nor meant as a formal comment, but just to note and ask for some opinion from the group or explanation why you got to formulate the example like that. With best regards, Axel Polleres Siemens Aktiengesellschaft Oesterreich CT RTC BAM CON-AT Siemensstrasse 90 1210 Vienna, Austria Tel.: +43 51707-36983 Mobile: +43 664 88550859 mailto:axel.polleres@siemens.com Company Name: Siemens Aktiengesellschaft Oesterreich; Legal Form: Stock Corporation; Company Seat: Vienna; Register Number: FN 60562 m; Registered at: Commercial Court Vienna; DVR-Number: 0001708
Received on Wednesday, 3 October 2012 07:20:09 UTC