Diagram
| Name: | Collection |
|---|---|
| Submitted by: | AldoGangemi |
| Also Known As: | membership, collection entity |
| Intent: | To represent domain (not set theory) membership. |
| Domains: | |
| Competency Questions: | |
| Solution description: | A class collection represents the concept of a set of entities (things). Things are members of the collection. |
| Reusable OWL Building Block: | 1 (989) |
| Consequences: | Collections and their members can be associated. Time-indexed membership cannot be represented though (you need a situation-based pattern). |
| Scenarios: | My saxophone collection includes a Mark VI tenor, a Balanced Action alto, and a Conn Transitional bari. |
| Known Uses: | |
| Web References: | |
| Other References: | |
| Examples (OWL files): | |
| Extracted From: | |
| Reengineered From: | |
| Has Components: | |
| Specialization Of: | |
| Related CPs: |
The Collection Content OP locally defines the following ontology elements:
The collection entity pattern. It is extracted from DOLCE-UltraLite by partial clone of elements.
(type): http://www.w3.org/2002/07/owl#Ontology
(versionInfo): Created by Aldo Gangemi and Valentina Presutti
(comment): The collection entity pattern. It is extracted from DOLCE-UltraLite by partial clone of elements.
(imports): http://www.ontologydesignpatterns.org/schemas/cpannotationschema.owl
No scenario is added to this Content OP.
This revision (revision ID 9074) takes in account the reviews: none
Other info at evaluation tab