Ok, thx
Do you think there is any more semantics in a functional property than just 
saying maxcard=1?
Or is this equivalent? 


 
 
 

   TNO.NL

 

Michel Böhms

Consultant Building Innovation
 

TNO Built Environment and Geosciences

Van Mourik Broekmanweg 6 | PO Box 49 

2600 AA | Delft | The Netherlands

 

 

Tel +31 15 2763107

E-mail  [email protected]

Web http://www.linkedin.com/in/michelbohms

Skype name michelbohms

 

 

Disclaimer 

 

 
 
 
 
 
 

-----Original Message-----
From: [email protected] 
[mailto:[email protected]] On Behalf Of Holger Knublauch
Sent: dinsdag 5 januari 2010 13:37
To: [email protected]
Subject: Re: [tbc-users] Max card of datatype props

Yes, any owl:Datatype property can have any number of values by default. You 
would need to declare it owl:FunctionalProperty or add an owl:maxCardinality 
restriction otherwise.

In my experience most datatype properties take at most one value, so that 
making them owl:FunctionalProperties is often a good choice.

Holger


On Jan 5, 2010, at 4:30 AM, Bohms, H.M. (Michel) wrote:


        A general question on datatype properties.
         
        Did I remember well that these can have in principle multiple values? 
(ie max card = +INF) ?
         
        so default 0..INF values?
         
        (ie need min and.or max card restrictions when otherwise)
         
        thx Michel
         
         
         
 

   TNO.NL

 

Michel Böhms

Consultant Building Innovation
 

TNO Built Environment and Geosciences

Van Mourik Broekmanweg 6 | PO Box 49 

2600 AA | Delft | The Netherlands

 

 

Tel +31 15 2763107

E-mail  [email protected] <mailto:[email protected]> 

Web http://www.linkedin.com/in/michelbohms 
<http://www.linkedin.com/in/michelbohms> 

Skype name michelbohms

 

 

Disclaimer 
<blocked::http://www.tno.nl/content.cfm?&context=overtno&content=overtnosub&laag1=282&item_id=72&Taal=2>
  

         

         
         
         
         
         
         
         
        This e-mail and its contents are subject to the DISCLAIMER at 
http://www.tno.nl/disclaimer/email.html


        --

        You received this message because you are subscribed to the Google 
Groups "TopBraid Composer Users" group.
        To post to this group, send email to 
[email protected].
        To unsubscribe from this group, send email to 
[email protected].
        For more options, visit this group at 
http://groups.google.com/group/topbraid-composer-users?hl=en.
        


--

You received this message because you are subscribed to the Google Groups 
"TopBraid Composer Users" group.
To post to this group, send email to [email protected].
To unsubscribe from this group, send email to 
[email protected].
For more options, visit this group at 
http://groups.google.com/group/topbraid-composer-users?hl=en.

This e-mail and its contents are subject to the DISCLAIMER at 
http://www.tno.nl/disclaimer/email.html

--

You received this message because you are subscribed to the Google Groups 
"TopBraid Composer Users" group.
To post to this group, send email to [email protected].
To unsubscribe from this group, send email to 
[email protected].
For more options, visit this group at 
http://groups.google.com/group/topbraid-composer-users?hl=en.


Reply via email to