Difference between revisions of "Recommendations for Semantic Web Markup of Existing XML"
(New page: ==Use Case: Semantic Markup of WMS Capabilities Documents== The Air Quality Cluster is experimenting with using some kind of structured markup / tagging of OGC WMS and WCS capabilities ...) |
|||
| Line 7: | Line 7: | ||
way that it is compatible with or even leverages the semantic web. A machine tags approach has been considered, e.g. | way that it is compatible with or even leverages the semantic web. A machine tags approach has been considered, e.g. | ||
<nowiki><Keyword>esip:dataset=OMI_AI_G</Keyword></nowiki> | <nowiki><Keyword>esip:dataset=OMI_AI_G</Keyword></nowiki> | ||
| + | |||
A link to an initial attempt of a WMS that includes the current keyword encoding: | A link to an initial attempt of a WMS that includes the current keyword encoding: | ||
[http://webapps.datafed.net/AIRNOW.ogc?service=wms&request=getCapabilities&version=1.1.1]. In the actual use case, this is used in a faceted search engine. Clearly, if this started out as a form of RDF, it would already be amenable to faceted search | [http://webapps.datafed.net/AIRNOW.ogc?service=wms&request=getCapabilities&version=1.1.1]. In the actual use case, this is used in a faceted search engine. Clearly, if this started out as a form of RDF, it would already be amenable to faceted search | ||
| Line 12: | Line 13: | ||
An alternative using XLink has been proposed as well. | An alternative using XLink has been proposed as well. | ||
| − | EXAMPLE? | + | '''EXAMPLE''''? |
Alternatively, RDFa was considered, but it is mostly defined in the context of XHTML. | Alternatively, RDFa was considered, but it is mostly defined in the context of XHTML. | ||
Revision as of 15:50, July 16, 2009
Use Case: Semantic Markup of WMS Capabilities Documents
The Air Quality Cluster is experimenting with using some kind of structured markup / tagging of OGC WMS and WCS capabilities documents (inside <Keyword> elements) to allow us to do structured searches on the documents. An example might be, "give me the layers where Dataset = 'OMI_AI_G'". See WMS_GetCapabilities#WMS_GetCapabilities_Layer_Description
However, if we are going to try to implement this kind of markup with a quasi-controlled vocabulary, we should do it in such a way that it is compatible with or even leverages the semantic web. A machine tags approach has been considered, e.g. <Keyword>esip:dataset=OMI_AI_G</Keyword>
A link to an initial attempt of a WMS that includes the current keyword encoding: [1]. In the actual use case, this is used in a faceted search engine. Clearly, if this started out as a form of RDF, it would already be amenable to faceted search
An alternative using XLink has been proposed as well.
EXAMPLE'?
Alternatively, RDFa was considered, but it is mostly defined in the context of XHTML.
Can the ESIP Semantic Web cluster provide a recommendation or suggestion in how to move forward that would be:
- flexible and extensible,
- compatible with the evolving ESIP datatype and services ontology and
- lightweight and easy to use
For any proposed solution, it would be extremely helpful to provide:
- an example of implementation, based on the current case at [2]
- an assessment of the scheme's usability by semantic web newbies
- pointers to existing tools that can work with the proposed solution, if they exist
- for bonus points, can the scheme be chained? That is, if I have <Keyword>Platform:Satellite</Keyword>, can I also have something like <Keyword>Satellite:Aura</Keyword>?
