W3C home > Mailing lists > Public > public-webont-comments@w3.org > November 2003

Re: implicit ways to define mandatory properties in OWL?

From: Jim Hendler <hendler@cs.umd.edu>
Date: Tue, 18 Nov 2003 13:00:16 -0500
Message-Id: <p05200f0ebbe00e218185@[10.0.1.5]>
To: Benjamin Nowack <office@e-senses.de>, public-webont-comments@w3.org

At 6:48 PM +0100 11/18/03, Benjamin Nowack wrote:
>Hi,
>
>as far as I understand, the usual way to specify
>a _required_ property is by using OWL's cardinality
>constraints (owl:cardinality, owl:minCardinality,
>owl:maxCardinality) on local classes/restrictions.
>
>I wonder if there are any other ways to flag a
>property (locally or globally) as mandatory?
>
>thanx for your time and help,
>benjamin
>
>[background: I'm working on a tool which creates html
>forms based on an OWL ontology that can only be
>submitted if at least the mandatory fields are
>filled in. Now I'm trying to find out, if I missed
>something in the OWL docs..]
>
>___________________________
>benjamin nowack
>
>kruppstrasse 82-100
>45145 essen, germany

The other way is with owl:someValuesFrom -- this means there must be 
at least one value of the property that has that class or datatype, 
so it makes it mandatory.  (note that paradoxically allValuesFrom 
doesn't mandate that there must be one, just that if there is one it 
must be of that class)
-- 
Professor James Hendler			  http://www.cs.umd.edu/users/hendler
Director, Semantic Web and Agent Technologies	  301-405-2696
Maryland Information and Network Dynamics Lab.	  301-405-6707 (Fax)
Univ of Maryland, College Park, MD 20742	  240-277-3388 (Cell)
Received on Tuesday, 18 November 2003 13:02:12 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Monday, 7 December 2009 10:43:29 GMT