Submissions:TimeIndexedSituation
From Odp
(Imported from OWL file.) |
Current revision (14:03, 8 March 2010) (view source) m |
||
(4 intermediate revisions not shown.) | |||
Line 1: | Line 1: | ||
{{Content_OP_Proposal_toolbar}} | {{Content_OP_Proposal_toolbar}} | ||
- | {{ | + | {{Graphical representation header}} |
- | |ImageName= | + | {{Graphical representation |
+ | |ImageName=TimeIndexedSituation.png | ||
}} | }} | ||
{{Content OP Proposal Template | {{Content OP Proposal Template | ||
- | | | + | |SubmittedBy=AldoGangemi |
- | | | + | |Name=TimeIndexedSituation |
+ | |Intent=To represent time indexed situations. | ||
+ | |Domain=General, | ||
|CompetencyQuestion=At what time did a certain situation occur?,What situations occurred at a certain time? | |CompetencyQuestion=At what time did a certain situation occur?,What situations occurred at a certain time? | ||
- | | | + | |ContentODPDescription=This pattern adds a time specification (the [[Submissions:TimeInterval|Time interval]] pattern) to the [[Submissions:Situation|Situation]] pattern, in order to provide a handy solution to many cases. |
- | | | + | |ReusableOWLBuildingBlock=http://ontologydesignpatterns.org/cp/owl/timeindexedsituation.owl |
|Consequences=We can represent situations that have an explicit time parameter. | |Consequences=We can represent situations that have an explicit time parameter. | ||
In principle, this can be done already with the Situation pattern, but this provides a handy composition with the TimeInterval pattern. | In principle, this can be done already with the Situation pattern, but this provides a handy composition with the TimeInterval pattern. | ||
- | | | + | |Scenario=Mustafa's address in 2005 was in Brussels |
+ | |HasComponent=TimeInterval | ||
|SpecializationOf=Situation | |SpecializationOf=Situation | ||
- | | | + | |RelatedCP=Time indexed participation,TimeIndexedClassification |
- | + | ||
}} | }} | ||
{{Element list header}} | {{Element list header}} | ||
Line 32: | Line 35: | ||
|HasElement=TimeIndexedSituation | |HasElement=TimeIndexedSituation | ||
}} | }} | ||
- | + | {{Additional information header}} | |
+ | A generic pattern usable for all situations that require a temporal indexing. | ||
{{Scenarios about me}} | {{Scenarios about me}} | ||
{{Reviews about me}} | {{Reviews about me}} | ||
- | + | {{Modeling issues about me}} | |
+ | {{My references}} |
Current revision
If you are a member of quality committee please visit the
If you are author of this proposal or you want to contribute to this pattern's review, you can: specify if this revision takes in account any of the review(s) In general, it could be useful to visit the evaluation section to have information about the evaluation process of this proposal Current revision ID: 9135 |
Graphical representation
Diagram
General description
Name: | TimeIndexedSituation |
---|---|
Submitted by: | AldoGangemi |
Also Known As: | |
Intent: | To represent time indexed situations. |
Domains: | |
Competency Questions: |
|
Solution description: | This pattern adds a time specification (the Time interval pattern) to the Situation pattern, in order to provide a handy solution to many cases. |
Reusable OWL Building Block: | http://ontologydesignpatterns.org/cp/owl/timeindexedsituation.owl (1021) |
Consequences: | We can represent situations that have an explicit time parameter.
In principle, this can be done already with the Situation pattern, but this provides a handy composition with the TimeInterval pattern. |
Scenarios: | Mustafa's address in 2005 was in Brussels |
Known Uses: | |
Web References: | |
Other References: | |
Examples (OWL files): | |
Extracted From: | |
Reengineered From: | |
Has Components: | |
Specialization Of: | |
Related CPs: |
Elements
The TimeIndexedSituation Content OP locally defines the following ontology elements:
Additional information
A generic pattern usable for all situations that require a temporal indexing.
Scenarios
No scenario is added to this Content OP.
Reviews
There is no review about this proposal. This revision (revision ID 9135) takes in account the reviews: none
Other info at evaluation tab
Modeling issues
There is no Modeling issue related to this proposal.
References