Submissions:Map Legend Ontology

From Odp

(Difference between revisions)
Jump to: navigation, search
(Imported from OWL file.)
Line 2: Line 2:
{{Graphical representation header}}
{{Graphical representation header}}
{{Graphical representation
{{Graphical representation
-
|ImageName=
+
|ImageName=http://ontologydesignpatterns.org/wiki/Image:MapLegendSketch.png
}}
}}
{{Content OP Proposal Template
{{Content OP Proposal Template
|SubmittedBy=SongGao
|SubmittedBy=SongGao
 +
|Name=Map Legend Ontology
 +
|Intent=Map legends are keys to the understanding of symbols used on maps. Without such legends and the knowledge to interpret them, maps are reduced to mere pictures.From an information retrieval perspective, facts such as that a certain map contains transportation features organized in a hierarchy of highways, streets, trails, and so forth, remain hidden and therefore can neither be used by machines nor humans to enable a richer search for map contents.
 +
|Domain=Geography, GIScience
 +
|CompetencyQuestion=What are the common symbol resources to represent highway transportation
 +
systems?
 +
|ContentODPDescription=In this work, we formalize a map legend ontology (MLO) that can be used for semantically annotate and query map contents via their legend in a machine-readable manner using Semantic Web and Linked Data technologies.
|ReusableOWLBuildingBlock=http://stko-exp.geog.ucsb.edu/mlo/map_legend_ontology.owl
|ReusableOWLBuildingBlock=http://stko-exp.geog.ucsb.edu/mlo/map_legend_ontology.owl
-
|Name=Map Legend Ontology
 
}}
}}
{{Element list header}}
{{Element list header}}
-
 
{{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}}

Revision as of 08:23, 20 August 2016


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: 12818

Graphical representation

Diagram (this article has no graphical representation)

General description

Name: Map Legend Ontology
Submitted by: SongGao
Also Known As:
Intent: Map legends are keys to the understanding of symbols used on maps. Without such legends and the knowledge to interpret them, maps are reduced to mere pictures.From an information retrieval perspective, facts such as that a certain map contains transportation features organized in a hierarchy of highways, streets, trails, and so forth, remain hidden and therefore can neither be used by machines nor humans to enable a richer search for map contents.
Domains:

Geography, GIScience

Competency Questions:
  • What are the common symbol resources to represent highway transportation

systems?

Solution description: In this work, we formalize a map legend ontology (MLO) that can be used for semantically annotate and query map contents via their legend in a machine-readable manner using Semantic Web and Linked Data technologies.
Reusable OWL Building Block: http://stko-exp.geog.ucsb.edu/mlo/map_legend_ontology.owl (720)
Consequences:
Scenarios:
Known Uses:
Web References:
Other References:
Examples (OWL files):
Extracted From:
Reengineered From:
Has Components:
Specialization Of:
Related CPs:


Elements

The Map Legend Ontology Content OP locally defines the following ontology elements:

Additional information

Scenarios

Scenarios about Map Legend Ontology

No scenario is added to this Content OP.

Reviews

Reviews about Map Legend Ontology

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

Other info at evaluation tab


Modeling issues

Modeling issues about Map Legend Ontology

There is no Modeling issue related to this proposal.


References

Add a reference


Personal tools
Quality Committee
Content OP publishers