Proposal Re: usingTool - not a property of Assertor?

On Sat, 18 Jun 2005 16:25:37 +0200, Charles McCathieNevile  
<chaals@opera.com> wrote:

> It seems that we could do this in several ways - we could subclass  
> Assertor, and make User with Tool, then have porperties of user (domain  
> User with Tool, range foaf:Person) and tool (domain same, range  
> earl:ToolG). We could also do this without the subclass I guess.

I propose that we subclass Assertor, to have a "Guided tester", and have  
properties "user" and "usingTool" with Guided Tester as domain and  
foaf:Person / earl:ToolG as range. These properties should each have  
minCardinality 1 and no maxCardinality, IMHO, since the user may be  
working with several tools in conjunction. The idea is not to prohibit  
multiple users, although that is an edge case. If there are a group of  
people making a collective decision, they should be described in a Bag -  
again IMHO...

This would solve the modelling problem which is one of the two things that  
I see as showstopper bugs at our current status (other than finishing the  
review of the proposals - I have some comments there too, but they are  
mostly about loosening proposed requirements :-)

-- 
Charles McCathieNevile                              chaals@opera.com
          hablo español - je parle français - jeg lærer norsk
   Here's one we prepared earlier:   http://www.opera.com/download

Received on Tuesday, 21 June 2005 15:33:22 UTC