(Imported from OWL file.) |
|||
| Line 1: | Line 1: | ||
{{Content_OP_Proposal_toolbar}} | {{Content_OP_Proposal_toolbar}} | ||
{{Graphical representation header}} | {{Graphical representation header}} | ||
| − | {{Graphical representation | + | {{Graphical representation}} |
| − | + | ||
| − | }} | + | |
{{Content OP Proposal Template | {{Content OP Proposal Template | ||
| + | |SubmittedBy=MarjanAlirezaie | ||
| + | |Name=time | ||
| + | |Intent=This pattern allows us to represent a temporal distance between two timestamps within an observation process in a SmartHome. There are other situations where we need to measure the interval (temporal distance) in the form of time steps regardless of the exact dates indicating the boundaries of the interval. The latter case is used when we want to define a complex event based on the temporal distance with its preconditions. | ||
|CompetencyQuestion=What is the time interval between two specific timestamps in the form of dates?, What is the temporal distance between two specific time steps?, What is the starting/ending timestamp? | |CompetencyQuestion=What is the time interval between two specific timestamps in the form of dates?, What is the temporal distance between two specific time steps?, What is the starting/ending timestamp? | ||
| − | | | + | |ContentODPDescription=Specializing the OWL-Time ontology |
| + | |ReusableOWLBuildingBlock=http://ecareathome-ontology.mpi.aass.oru.se/patterns/time.owl | ||
|Consequences=We can quantitavely represent temporal distances through an observation process for different purposes . These purposes include | |Consequences=We can quantitavely represent temporal distances through an observation process for different purposes . These purposes include | ||
definition of an event in terms of its preconditions whose occurance timestamp is within a specific temporal distance with that of the event. | definition of an event in terms of its preconditions whose occurance timestamp is within a specific temporal distance with that of the event. | ||
| − | | | + | |ExtractedFrom=https://www.w3.org/TR/owl-time/ |
| − | | | + | |ReengineeredFrom=https://www.w3.org/TR/owl-time/ |
| − | + | |SpecializationOf=https://www.w3.org/TR/owl-time/ | |
| − | | | + | |
}} | }} | ||
{{Element list header}} | {{Element list header}} | ||
| Line 27: | Line 28: | ||
|HasElement=SmartHomeTimeInterval | |HasElement=SmartHomeTimeInterval | ||
}} | }} | ||
| − | |||
{{Additional information header}} | {{Additional information header}} | ||
{{Scenarios about me}} | {{Scenarios about me}} | ||
| − | {{Reviews about me}}{{Modeling issues about me}}{{My references}} | + | {{Reviews about me}} |
| + | {{Modeling issues about me}} | ||
| + | {{My references}} | ||
|
Last modified date is: 2017-11-25 |
Diagram (this article has no graphical representation)
| Name: | time |
|---|---|
| Submitted by: | MarjanAlirezaie |
| Also Known As: | |
| Intent: | This pattern allows us to represent a temporal distance between two timestamps within an observation process in a SmartHome. There are other situations where we need to measure the interval (temporal distance) in the form of time steps regardless of the exact dates indicating the boundaries of the interval. The latter case is used when we want to define a complex event based on the temporal distance with its preconditions. |
| Domains: | |
| Competency Questions: | |
| Solution description: | Specializing the OWL-Time ontology |
| Reusable OWL Building Block: | 1 (256) |
| Consequences: | We can quantitavely represent temporal distances through an observation process for different purposes . These purposes include
definition of an event in terms of its preconditions whose occurance timestamp is within a specific temporal distance with that of the event. |
| Scenarios: | |
| Known Uses: | |
| Web References: | |
| Other References: | |
| Examples (OWL files): | |
| Extracted From: | |
| Reengineered From: | |
| Has Components: | |
| Specialization Of: | |
| Related CPs: |
The SmartHome TimeInterval Content OP locally defines the following ontology elements:
No scenario is added to this Content OP.
This revision (revision ID 13366) takes in account the reviews: none
Other info at evaluation tab
'Ontology Design Patterns'
