|
Last modified date is: 2010-03-08 |
Diagram
| Name: | collection entity |
|---|---|
| Submitted by: | ValentinaPresutti |
| Also Known As: | collections, membership |
| Intent: | To represent collections, and their entities, i.e. to represent membership. |
| Domains: | |
| Competency Questions: | |
| Solution description: | This pattern is a basic one: it catches the idea of a collection and its members. |
| Reusable OWL Building Block: | 1 (989) |
| Consequences: | It is possible to put sets in the domain of discourse through the class Collection, which reifies them.
For temporary membership, the TimeIndexedMembership should be used. |
| Scenarios: | The Louvre Aegyptian collection. |
| Known Uses: | |
| Web References: | |
| Other References: | |
| Examples (OWL files): | |
| Extracted From: | |
| Reengineered From: | |
| Has Components: | |
| Specialization Of: | |
| Related CPs: |
The CollectionEntity Content OP locally defines the following ontology elements:
Collection (owl:Class) Any container for entities that share one or more common properties. E.g. stone objects, the nurses, the Louvre Aegyptian collection. A collection is not a logical class: a collection is a first-order entity, while a class is a second-order one.
Collection page Entity (owl:Class) Anything: real, possible, or imaginary, which some modeller wants to talk about for some purpose.
Entity page
hasMember (owl:ObjectProperty) A relation between collections and entities, e.g. 'my collection of saxophones includes an old Adolphe Sax original alto' (i.e. my collection has member an Adolphe Sax alto). The object property isMemberOf is its inverse.
hasMember pageNo scenario is added to this Content OP.
This revision (revision ID 9075) takes in account the reviews: CollectionEntity (ValentinaPresutti about CollectionEntity)
Other info at evaluation tab
'Ontology Design Patterns'