(The Transport Pattern allows data modellers and ontology creators the ability to filter and categorise large geoscience data stores.) |
|||
| Line 33: | Line 33: | ||
{{Modeling issues about me}} | {{Modeling issues about me}} | ||
{{My references}} | {{My references}} | ||
| + | {{Submission to event | ||
| + | |Event=WOP:2013 | ||
| + | }} | ||
Diagram (this article has no graphical representation)
| Name: | transportPattern |
|---|---|
| Submitted by: | Brandonwhitehead |
| Also Known As: | |
| Intent: | To reduce dimensionality of large data collections. |
| Domains: | |
| Competency Questions: |
Where was a package shipped from and where was it shipped to? |
| Solution description: | The rive water was polluted from effluent near a large factory.
A package left Auckland, New Zealand, at 5:45am on 01/06/2012 and arrived in Los Angeles, USA, on 01/12/2012. |
| Reusable OWL Building Block: | 1 (0) |
| Consequences: | This CP allows data modellers and ontology creators the ability to filter and categorise large geoscience data stores. |
| Scenarios: | |
| Known Uses: | |
| Web References: | |
| Other References: | |
| Examples (OWL files): | |
| Extracted From: | |
| Reengineered From: | |
| Has Components: | |
| Specialization Of: | |
| Related CPs: |
The TransportPattern Content OP locally defines the following ontology elements:
No scenario is added to this Content OP.
This revision (revision ID 11628) takes in account the reviews: none
Other info at evaluation tab
| |
Submission to event |
|---|