pimo:Collection
A collection of Things, independent of their class. The items in the collection share a common property. Which property may be modelled explicitly or mentioned in the description of the Collection. The requirement of explicit modelling the semantic meaning of the collection is not mandatory, as collections can be created ad-hoc. Implizit modelling can be applied by the system by learning the properties. For example, a Collection of "Coworkers" could be defined as that all elements must be of class "Person" and have an attribute "work for the same Organization as the user". Further standards can be used to model these attributes.
Blueprint information
- Status:
- Complete
- Approver:
- None
- Priority:
- Undefined
- Drafter:
- None
- Direction:
- Needs approval
- Assignee:
- None
- Definition:
- Approved
- Series goal:
- None
- Implementation:
-
Implemented
- Milestone target:
- None
- Started by
- Tomás Vírseda García
- Completed by
- Tomás Vírseda García
Related branches
Related bugs
Sprints
Whiteboard
I have taken this class from PIMO ontology to model collections in Vazaar.
Collections are resources. A collection could be linked to other collection. One collection has zero or more resources.
Common metadata properties:
- PIMO['hasLogica
Ex.:
<?xml version="1.0" encoding="utf-8"?>
<rdf:RDF
xmlns:pimo='http://
xmlns:rdf='http://
xmlns:nao='http://
xmlns:nie='http://
>
<pimo:Collection rdf:about=
<nao:
<nie:
<nie:
<nie:title>Foo Collection<
<nao:
</pimo:
</rdf:RDF>
Work Items
Dependency tree
* Blueprints in grey have been implemented.
