<html xmlns:v="urn:schemas-microsoft-com:vml" xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns="http://www.w3.org/TR/REC-html40">
<head>
<meta http-equiv="Content-Type" content="text/html; charset=us-ascii">
<meta name="Generator" content="Microsoft Word 14 (filtered medium)">
<!--[if !mso]><style>v\:* {behavior:url(#default#VML);}
o\:* {behavior:url(#default#VML);}
w\:* {behavior:url(#default#VML);}
.shape {behavior:url(#default#VML);}
</style><![endif]--><style><!--
/* Font Definitions */
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
{font-family:Tahoma;
panose-1:2 11 6 4 3 5 4 4 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
margin-bottom:.0001pt;
font-size:12.0pt;
font-family:"Times New Roman","serif";}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:blue;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:purple;
text-decoration:underline;}
span.EmailStyle17
{mso-style-type:personal-reply;
font-family:"Calibri","sans-serif";
color:#1F497D;}
.MsoChpDefault
{mso-style-type:export-only;
font-family:"Calibri","sans-serif";}
@page WordSection1
{size:8.5in 11.0in;
margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]-->
</head>
<body lang="EN-US" link="blue" vlink="purple">
<div class="WordSection1">
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">I like the idea of having the registry on GitHub, using a neutral domain for the host name in the HTTP URIs, with a redirector to point those URIs at authoritative
resources when dereferenced. These resources must be under some stable stewardship, ideally not linked with any commercial interest, and with a supporting community. Should the host be metadata101 or OSGeo—which is more stable and better supported.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">Stephen M Richard<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">Arizona Geological Survey<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">416 W. Congress #100<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">Tucson, AZ<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">AZGS: 520-770-3500<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">Office: 520-209-4127<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">FAX: 520-770-3505<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D"><o:p> </o:p></span></p>
<div style="border:none;border-left:solid blue 1.5pt;padding:0in 0in 0in 4.0pt">
<div>
<div style="border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0in 0in 0in">
<p class="MsoNormal"><b><span style="font-size:10.0pt;font-family:"Tahoma","sans-serif"">From:</span></b><span style="font-size:10.0pt;font-family:"Tahoma","sans-serif""> Tom Kralidis [via OSGeo.org] [mailto:ml-node+s1560n5107713h84@n6.nabble.com]
<br>
<b>Sent:</b> Wednesday, March 05, 2014 9:31 AM<br>
<b>To:</b> Steve Richard<br>
<b>Subject:</b> Re: [cat-interop] Metadata link types vocabulary proposal<o:p></o:p></span></p>
</div>
</div>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal"><br>
Thinking this though more, I think the way forward here is for this <br>
to be an OSGeo vocabulary, which we can build and manage under <br>
<a href="http://osgeo.org/vocab" target="_top">http://osgeo.org/vocab</a> like: <br>
<br>
<a href="http://osgeo.org/vocab/data/" target="_top">http://osgeo.org/vocab/data/</a>{provider}/{type}[/version]
<br>
<a href="http://osgeo.org/vocab/service/" target="_top">http://osgeo.org/vocab/service/</a>{provider}/{type}[/version]
<br>
<br>
Then providing a thin resolution layer, members of this vocabulary, when <br>
invoked via HTTP, would then dereference/resolve accordingly. Like: <br>
<br>
<a href="http://osgeo.org/vocab/service/ogc/sos/1.0" target="_top">http://osgeo.org/vocab/service/ogc/sos/1.0</a><br>
<br>
would resolve to: <br>
<br>
<a href="http://www.opengis.net/sos/1.0" target="_top">http://www.opengis.net/sos/1.0</a> (which then resolves as per the
<br>
authoritative provider's wishes). <br>
<br>
This provides the following benefits: <br>
<br>
1./ metadata clients/servers can bind to the OSGeo vocabulary, thus <br>
realizing the core goal of a harmonized link type list <br>
2./ anyone who really wants to invoke / resolve these can do so <br>
3./ This keeps OSGeo as a just a gatekeeper / custodian of the list with <br>
redirects as appropriate, which gets us out of the complexity of <br>
managing these across standards orgs/etc. <br>
<br>
Comments? I've written a small Flask app to act as a high level <br>
resolver, based on our link types list and will resolve / redirect <br>
accordingly, which we can push forward for hosting, etc. <br>
<br>
<br>
<br>
On Mon, 3 Mar 2014, Tom Kralidis wrote: <o:p></o:p></p>
<div>
<p class="MsoNormal"><br>
> Date: Mon, 3 Mar 2014 21:53:51 -0500 <br>
> From: Tom Kralidis <<a href="/user/SendEmail.jtp?type=node&node=5107713&i=0" target="_top">[hidden email]</a>>
<br>
> To: Paul van Genuchten <<a href="/user/SendEmail.jtp?type=node&node=5107713&i=1" target="_top">[hidden email]</a>>
<br>
> Cc: "<<a href="/user/SendEmail.jtp?type=node&node=5107713&i=2" target="_top">[hidden email]</a>>" <<a href="/user/SendEmail.jtp?type=node&node=5107713&i=3" target="_top">[hidden email]</a>>
<br>
> Subject: Re: [cat-interop] Metadata link types vocabulary proposal <br>
> <br>
> On Mon, Mar 3, 2014 at 4:07 PM, Paul van Genuchten <br>
> <<a href="/user/SendEmail.jtp?type=node&node=5107713&i=4" target="_top">[hidden email]</a>> wrote:
<br>
>> I support Stephan at this point. The semantic web can be a big consumer <br>
>> of spatial data services, if we're able to optimally embed our data in <br>
>> it. Linking to controlled vocabularies by url is a big facilitator. <br>
>> <br>
> <br>
> Good points. <br>
> <br>
>> Sure i see the point of having a urn structure as <br>
>> {provider}:{type}:{identifier}:{version}. But this can also be managed <br>
>> in a (skos) vocabulary-identifier-as-url by using identifiers like: <br>
>> <br>
>> for example: <br>
>> <a href="http://osgeo.org/vocab/service/ogc/wms/1.1" target="_top">http://osgeo.org/vocab/service/ogc/wms/1.1</a><br>
>> <a href="http://osgeo.org/vocab/service/opensearch/opensearch/2.0" target="_top">
http://osgeo.org/vocab/service/opensearch/opensearch/2.0</a><br>
>> <br>
>> and <br>
>> <br>
>> <a href="http://osgeo.org/vocab/mediatype/esri/shapefile/1.0" target="_top">http://osgeo.org/vocab/mediatype/esri/shapefile/1.0</a><br>
>> <a href="http://osgeo.org/vocab/mediatype/ogc/gml/2.0" target="_top">http://osgeo.org/vocab/mediatype/ogc/gml/2.0</a><br>
>> <a href="http://osgeo.org/vocab/mediatype/w3c/json-ld/1.0" target="_top">http://osgeo.org/vocab/mediatype/w3c/json-ld/1.0</a><br>
>> <br>
>> or <br>
>> <br>
>> <a href="http://osgeo.org/vocab/service#ogc_wms_1_1" target="_top">http://osgeo.org/vocab/service#ogc_wms_1_1</a><br>
>> <a href="http://osgeo.org/vocab/mediatype#ogc_gml_2_0" target="_top">http://osgeo.org/vocab/mediatype#ogc_gml_2_0</a><br>
>> <br>
>> At this point we should consider if osgeo.org is the best place to set <br>
>> up such a service/vocab, as this is more a data-matter then a software <br>
>> matter. Should we connect with geovocab, w3c/ogc, dbpedia to have this <br>
>> set up? <br>
>> <br>
> <br>
> Based on the comments on HTTP URIs at <br>
> <a href="https://github.com/OSGeo/Cat-Interop/issues/3" target="_top">https://github.com/OSGeo/Cat-Interop/issues/3</a>, the OGC has this at
<br>
> <a href="http://www.opengis.net">www.opengis.net</a>. However the structure is not SKOS-like. I guess one
<br>
> factor is how deep version negotiation would go. <br>
> <br>
> Then again, we could implement this in OSGeo and have resolver back to <br>
> their authoritative resources (i.e. <br>
> <a href="http://osgeo.org/vocab/service/csw/2.0.2" target="_top">http://osgeo.org/vocab/service/csw/2.0.2</a> could resolve to
<br>
> <a href="http://www.opengis.net/cat/csw/2.0.2" target="_top">http://www.opengis.net/cat/csw/2.0.2</a>. Does this sound useful/make
<br>
> sense? <br>
> <br>
>> If we feel osgeo.org is a good place, let's post about it in the <br>
>> request-list... <br>
>> <br>
>> _______________________________________________ <br>
>> cat-interop mailing list <br>
>> <a href="/user/SendEmail.jtp?type=node&node=5107713&i=5" target="_top">[hidden email]</a>
<br>
>> <a href="http://lists.osgeo.org/cgi-bin/mailman/listinfo/cat-interop" target="_top">
http://lists.osgeo.org/cgi-bin/mailman/listinfo/cat-interop</a><br>
> <o:p></o:p></p>
</div>
<p class="MsoNormal" style="margin-bottom:12.0pt">_______________________________________________
<br>
cat-interop mailing list <br>
<a href="/user/SendEmail.jtp?type=node&node=5107713&i=6" target="_top">[hidden email]</a>
<br>
<a href="http://lists.osgeo.org/cgi-bin/mailman/listinfo/cat-interop" target="_top">http://lists.osgeo.org/cgi-bin/mailman/listinfo/cat-interop</a><br>
<br>
<o:p></o:p></p>
<div class="MsoNormal" align="center" style="text-align:center">
<hr size="1" width="100%" noshade="" style="color:#CCCCCC" align="center">
</div>
<div>
<div>
<p class="MsoNormal"><b><span style="font-size:9.0pt;font-family:"Tahoma","sans-serif";color:#444444">If you reply to this email, your message will be added to the discussion below:<o:p></o:p></span></b></p>
</div>
<p class="MsoNormal"><span style="font-size:9.0pt;font-family:"Tahoma","sans-serif";color:#444444"><a href="http://osgeo-org.1560.x6.nabble.com/cat-interop-Metadata-link-types-vocabulary-proposal-tp5106675p5107713.html">http://osgeo-org.1560.x6.nabble.com/cat-interop-Metadata-link-types-vocabulary-proposal-tp5106675p5107713.html</a>
<o:p></o:p></span></p>
</div>
<div style="margin-top:4.8pt">
<p class="MsoNormal" style="line-height:18.0pt"><span style="font-size:8.5pt;font-family:"Tahoma","sans-serif";color:#666666">To unsubscribe from Cat-Interop,
<a href="http://osgeo-org.1560.x6.nabble.com/template/NamlServlet.jtp?macro=unsubscribe_by_code&node=5079187&code=c3RldmUucmljaGFyZEBhemdzLmF6Lmdvdnw1MDc5MTg3fC0xMDkwNzA1OTU0">
click here</a>.<br>
<a href="http://osgeo-org.1560.x6.nabble.com/template/NamlServlet.jtp?macro=macro_viewer&id=instant_html%21nabble%3Aemail.naml&base=nabble.naml.namespaces.BasicNamespace-nabble.view.web.template.NabbleNamespace-nabble.view.web.template.NodeNamespace&breadcrumbs=notify_subscribers%21nabble%3Aemail.naml-instant_emails%21nabble%3Aemail.naml-send_instant_email%21nabble%3Aemail.naml"><span style="font-size:7.0pt;font-family:"Times New Roman","serif"">NAML</span></a>
<o:p></o:p></span></p>
</div>
</div>
</div>
</body>
</html>