I have to clarify that "meet up" is an
"event" not an organization ! It is an
ongoing event ( cyclic) and has a psuedo or informal
organization or represent some sort of organization..
So to simply, one has to model the psuedo
organization as " meetup group " or
something.. and normalize it.. or call
"meet up" an event!
--- On Wed, 10/28/09, Matthew West <dr.matthew.west@xxxxxxxxx>
wrote:
From: Matthew West <dr.matthew.west@xxxxxxxxx>
Subject: Re: [ontolog-forum] Ontology modules and namespaces
To: "'[ontolog-forum] '" <ontolog-forum@xxxxxxxxxxxxxxxx>
Date: Wednesday, October 28, 2009, 9:14 AM
I think that was a very interesting discussion! We
do have some examples from traditional modeling
world. ( class room kind of examples..)
For example, A Supervisor is an employee
himself, and he has staff ( group of employees ) working for
him! Which creates a one to many relationship !
MW: I’m afraid that really is only a class-room
example. In the real l world, the employees and supervisors come and go, so
it is really a many-to-many relationship, and arguably more complex even
than that.
A meetup of Meetups has similar modeling notations..
About your previous slides.. and the exmaples of Table.
At a conceptual level ( Ontology) I would just have a
superclass, a class of "Furniture"
with subclass as Tables, Chairs, upholstry and the
rest in the list.. and relationships..
MW: Upholstery is not a class of furniture. It is only a
part of a piece of furniture.
As one can see, Class "Furniture" can be generic and
standardazised with a set of generic subclasses and generic
relationhips.. if one does not include the
exceptions, at this level, I would find that acceptable. it can
be done at a detail level.. as long as superclass covers
all.. However, if one finds the exceptions or the
special types ear;y, then can include as notes with explanation, it would
help at a detail level.
MW: If there are exceptions, then you have just done
something wrong.
At a detail design level - which is logical and physical,
I would include further details and exceptional or special types
etc.. But at a detail level of design, if this step is
overlooked, it causes either design flaws or difficult coding to
cover it up. ( its just bad design..)
MW: I’m sorry, I don’t follow this. Specific product models
may be subtypes of generic product types.
|
Regards
Matthew
West
Information
Junction
Tel:
+44 560 302 3685
Mobile:
+44 750 3385279
matthew.west@xxxxxxxxxxxxxxxxxxxxxxxxx
http://www.informationjunction.co.uk/
http://www.matthew-west.org.uk/
This
email originates from Information Junction Ltd. Registered in England and
Wales No. 6632177.
Registered
office: 2 Brookside, Meadow Way, Letchworth Garden City, Hertfordshire, SG6
3JE.
Note: I am sending this a comments only.
--- On Wed, 10/28/09, Matthew West <dr.matthew.west@xxxxxxxxx>
wrote:
From: Matthew West <dr.matthew.west@xxxxxxxxx>
Subject: Re: [ontolog-forum] Ontology modules and namespaces
To: "'[ontolog-forum] '" <ontolog-forum@xxxxxxxxxxxxxxxx>
Date: Wednesday, October 28, 2009, 4:27 AM
-----Inline Attachment Follows-----
|
|