[esip-semanticweb] [ESIP-AQ] help with marking up WMS/WCS Capability docs?

[John Graybeal]

Can you all describe what you mean by 'machine tags'?

John

On Jul 15, 2009, at 7:02 PM, Wilson, Brian D (335G) wrote:

> Chris et al,
>
> Machine tags are certainly the fastest way to start specifying
> a controlled set of facets and values.  They can serve as a way
> to populate instances into a fuller ontology to be supplied later.
>
> I don't think RDFa is suitable for insertion into XML files.
>
> -- Brian
>
>
>
> -----Original Message-----
> From: esip-aqcluster-bounces at rtpnet.org [mailto:esip-aqcluster-bounces at rtpnet.org 
> ] On Behalf Of Christopher Lynnes
> Sent: Wednesday, July 15, 2009 12:54 PM
> To: esip-semanticweb at rtpnet.org
> Cc: esip-aqcluster at rtpnet.org; Erin Robinson
> Subject: [ESIP-AQ] help with marking up WMS/WCS Capability docs?
>
> Greetings!
>
> Over in the Air Quality Cluster, we are 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'". Seehttp://wiki.esipfed.org/index.php/WMS_GetCapabilities#WMS_GetCapabilities_Layer_Description
>
> Thing is, we figure 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.  We
> have pondered a machine tags approach, e.g.,
> <Keyword>esip:dataset=OMI_AI_G</Keyword>.  (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)
> .
>
> Alternatively, we have heard RDFa mentioned for microformats, though
> mostly in the context of XHTML.  Can this be applied to OGC's XML and
> if so, how?
>
> Can the ESIP Semantic Web cluster provide a recommendation or
> suggestion in how to move forward that would be:
> (a) flexible and extensible,
> (b) compatible with the evolving ESIP datatype and services ontology  
> and
> (c) lightweight and easy to use?
> --
> Christopher Lynnes             NASA/GSFC, Code 610.2
> 301-614-5185
>
> _______________________________________________
> ESIP-AQcluster mailing list
> ESIP-AQcluster at rtpnet.org
> http://lists.deltaforce.net/mailman/listinfo/esip-aqcluster
> _______________________________________________
> esip-semanticweb mailing list
> esip-semanticweb at rtpnet.org
> http://lists.deltaforce.net/mailman/listinfo/esip-semanticweb


John

--------------
John Graybeal   <mailto:graybeal at mbari.org>  -- 831-775-1956
Monterey Bay Aquarium Research Institute
Marine Metadata Interoperability Project: http://marinemetadata.org