Submissions:Collection

From Odp

(Difference between revisions)
Jump to: navigation, search
Line 6: Line 6:
|ContentODPAlsoKnownAs=membership, collection entity
|ContentODPAlsoKnownAs=membership, collection entity
|Intent=To represent domain (not set theory) membership.
|Intent=To represent domain (not set theory) membership.
 +
|Domain=General
|CompetencyQuestion=What things are contained in this collection (community, collective)? What collections this thing is member of?
|CompetencyQuestion=What things are contained in this collection (community, collective)? What collections this thing is member of?
|ContentODPDescription=A class collection represents the concept of a set of entities (things). Things are members of the collection.
|ContentODPDescription=A class collection represents the concept of a set of entities (things). Things are members of the collection.

Revision as of 15:52, 15 February 2010


This pattern has been certified.

Related submission, with evaluation history, can be found here

If you are a member of quality committee please visit the

evaluation section

If you are author of this proposal or you want to contribute to this pattern's review, you can:

In general, it could be useful to visit the evaluation section to have information about the evaluation process of this proposal

Current revision ID: 6768


General description

Name: Collection
Submitted by: AldoGangemi
Also Known As: membership, collection entity
Intent: To represent domain (not set theory) membership.
Domains:

General

Competency Questions:
  • What things are contained in this collection (community
  • collective)? What collections this thing is member of?
Solution description: A class collection represents the concept of a set of entities (things). Things are members of the collection.
Reusable OWL Building Block: http://www.ontologydesignpatterns.org/cp/owl/collectionentity.owl (1042)
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:


Elements

The Collection Content OP locally defines the following ontology elements:

ObjectProperty 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).
hasMember page
ObjectProperty isMemberOf (owl:ObjectProperty)
isMemberOf page
Class 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

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

Scenarios

Scenarios about Collection

No scenario is added to this Content OP.

Reviews

Reviews about Collection

There is no review about this proposal. This revision (revision ID 6768) takes in account the reviews: none

Other info at evaluation tab

Personal tools
Quality Committee
Content OP publishers