<html><head><meta http-equiv="Content-Type" content="text/html charset=windows-1252"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;"><div>Hi Stephen and Richard,</div><div><br></div>Thanks for the feedback. I agree that name recognition is a good thing. However, I feel that choosing for a domain/name that is not related to proprietary nor to open source software is a good thing. <div><br></div><div>Within GeoNetwork opensource we've been developing metadata profile support in the form of plugins for several year now. Because these profiles are hosted on our GeoNetwork github, outsiders using other software for metadata management are less likely to use and contribute to those profile plugins. This is a pity, because only a small part of the plugin is GeoNetwork specific while most is generic and often developed by a community of practice (e.g. a country or region, a community of marine or soil experts). Hence we want to move the profiles outside of the GeoNetwork opensource projects so we attract a larger expert community.</div><div><br></div><div>The idea is that under <a href="http://metadata101.org">metadata101.org</a> these profiles are developed and maintained by the profile custodians. Doing so has many benefits:</div><div>- Custodians manage versions better than software developers from a specific software.</div><div>- Interaction between metadata experts dealing with profiles can lead to more interoperable profiles.</div><div>- Transformations between profiles can be developed in a consistent manner between expert groups.</div><div><div>- Software developers of different applications that depend on supporting metadata profiles in their software need not to care about the specifics of a profile that much. They have a single point of reference for the schemas and the schematron rules that come with such profile. </div><div>- Software developers can ensure end users have the option to select the metadata profile of interest to them instead of hardcoding profiles into the software.</div><div>- End users and developers have an easier task in finding relevant & existing profiles. Now these are spread all over the place. And hardly anytime they can be found in a collaborative environment like github. So contributing or discussing them is difficult right now.</div><div>- It becomes easy for new communities to add their own metadata profile that can then automatically become available in their software of choice.</div><div><br></div><div>There are for sure more reasons why it is useful to maintain metadata profiles in an independent location.</div><div><br></div><div>Since vocabularies are so closely related to the metadata profiles that often use them, it seems a fairly logical thing to me to maintain those in the same location. And as I said, not relating it to a specific software project or to an open source (or proprietary) foundation makes it easier for both worlds to participate in the development, maintenance and use of these vocabularies.</div><div><br></div><div>I hope this makes sense to you. Cheers,</div><div>Jeroen</div><div><div><div apple-content-edited="true">
<span style="color: rgb(0, 0, 0); font-family: Helvetica; font-size: medium; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; orphans: 2; text-align: -webkit-auto; text-indent: 0px; text-transform: none; white-space: normal; widows: 2; word-spacing: 0px; -webkit-text-size-adjust: auto; -webkit-text-stroke-width: 0px; display: inline !important; float: none; ">_____________________________________________</span><span style="color: rgb(0, 0, 0); font-family: Helvetica; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; orphans: 2; text-align: -webkit-auto; text-indent: 0px; text-transform: none; white-space: normal; widows: 2; word-spacing: 0px; -webkit-text-size-adjust: auto; -webkit-text-stroke-width: 0px; display: inline !important; float: none; ">_______</span><br style="color: rgb(0, 0, 0); font-family: Helvetica; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; orphans: 2; text-align: -webkit-auto; text-indent: 0px; text-transform: none; white-space: normal; widows: 2; word-spacing: 0px; -webkit-text-size-adjust: auto; -webkit-text-stroke-width: 0px; "><b style="font-style: normal; font-variant: normal; letter-spacing: normal; line-height: normal; orphans: 2; text-align: -webkit-auto; text-indent: 0px; text-transform: none; white-space: normal; widows: 2; word-spacing: 0px; -webkit-text-size-adjust: auto; -webkit-text-stroke-width: 0px; color: rgb(19, 11, 81); font-family: Verdana, sans-serif; font-size: 11px; "></b><div style="color: rgb(0, 0, 0); font-family: Helvetica; font-size: 12px; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; orphans: 2; text-align: -webkit-auto; text-indent: 0px; text-transform: none; white-space: normal; widows: 2; word-spacing: 0px; -webkit-text-size-adjust: auto; -webkit-text-stroke-width: 0px; "><b style="color: rgb(19, 11, 81); font-family: Verdana, sans-serif; font-size: 11px; "><font class="Apple-style-span" color="#130B51" face="Verdana, sans-serif" size="3"><span class="Apple-style-span" style="font-size: 11px; "></span></font></b><font class="Apple-style-span" color="#130B51" face="Verdana, sans-serif" size="3"><div style="font-size: 12px; color: rgb(0, 0, 0); font-family: Helvetica; font-weight: normal; "><b style="color: rgb(19, 11, 81); font-family: Verdana, sans-serif; font-size: 11px; "><b style="color: rgb(19, 11, 81); font-family: Verdana, sans-serif; font-size: 11px; "><b><div style="font-family: Helvetica; font-size: medium; display: inline !important; "><font class="Apple-style-span" color="#FE2617"><span class="Apple-style-span" style="color: rgb(0, 0, 0); font-weight: normal; font-family: Verdana, sans-serif; font-size: 11px; "><b><div style="font-family: Helvetica; font-weight: normal; display: inline !important; "><span class="Apple-style-span" style="font-family: Verdana, sans-serif; font-size: 11px; "><b><div style="font-family: Helvetica; font-weight: normal; display: inline !important; "><span class="Apple-style-span" style="font-family: Verdana, sans-serif; font-size: 11px; "><b><font class="Apple-style-span" color="#130B51">Geo</font><font class="Apple-style-span" color="#00A7E3">Cat</font></b></span></div></b></span></div></b></span> </font><font class="Apple-style-span" color="#130B51">introduces</font><font class="Apple-style-span" color="#FE2617"> </font><font class="Apple-style-span" color="#00A7E3">Bridge<font class="Apple-style-span" size="1"><span class="Apple-style-span" style="font-size: 9px; ">© </span></font></font></div></b></b></b></div><div style="font-size: 12px; color: rgb(0, 0, 0); font-family: Helvetica; font-weight: normal; "><span class="Apple-style-span" style="font-size: 11px; font-family: Verdana, sans-serif; "><b><div style="font-family: Helvetica; display: inline !important; "><font class="Apple-style-span" color="#00A7E3"></font><font class="Apple-style-span" color="#130B51">An extension to ArcGIS<font class="Apple-style-span" size="1"><span class="Apple-style-span" style="font-size: 9px; ">©</span></font> to instantly publish data and metadata on GeoServer and GeoNetwork.</font></div></b></span></div><span class="Apple-style-span" style="color: rgb(0, 0, 0); font-family: Helvetica; font-weight: normal; "><span class="Apple-style-span" style="font-size: 12px; "><span class="Apple-style-span" style="border-collapse: separate; border-spacing: 0px; "><span class="Apple-style-span" style="border-collapse: separate; border-spacing: 0px; font-size: medium; "><span class="Apple-style-span" style="font-size: 12px; "><span class="Apple-style-span" style="border-collapse: separate; border-spacing: 0px; "><span class="Apple-style-span" style="font-size: 12px; "><span class="Apple-style-span" style="border-collapse: separate; border-spacing: 0px; "><span class="Apple-style-span" style="border-collapse: separate; border-spacing: 0px; "><span class="Apple-style-span" style="font-family: Arial; font-size: 10px; "><font class="Apple-style-span" color="#2AA7DF"><div style="color: rgb(0, 0, 0); font-family: Helvetica; "><span class="Apple-style-span" style="font-family: Verdana, sans-serif; font-size: 11px; "><b><div style="font-family: Helvetica; font-weight: normal; ">See <a href="http://geocat.net/">http://geocat.net</a> for more details. </div></b></span></div></font></span></span></span></span></span></span></span></span></span></span></font><div><br></div><div><span style=" ">Jeroen Ticheler</span></div></div><span style="color: rgb(0, 0, 0); font-family: Helvetica; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; orphans: 2; text-align: -webkit-auto; text-indent: 0px; text-transform: none; white-space: normal; widows: 2; word-spacing: 0px; -webkit-text-size-adjust: auto; -webkit-text-stroke-width: 0px; display: inline !important; float: none; ">GeoCat bv</span><br style="color: rgb(0, 0, 0); font-family: Helvetica; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; orphans: 2; text-align: -webkit-auto; text-indent: 0px; text-transform: none; white-space: normal; widows: 2; word-spacing: 0px; -webkit-text-size-adjust: auto; -webkit-text-stroke-width: 0px; "><span style="color: rgb(0, 0, 0); font-family: Helvetica; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; orphans: 2; text-align: -webkit-auto; text-indent: 0px; text-transform: none; white-space: normal; widows: 2; word-spacing: 0px; -webkit-text-size-adjust: auto; -webkit-text-stroke-width: 0px; display: inline !important; float: none; ">Veenderweg 13</span><br style="color: rgb(0, 0, 0); font-family: Helvetica; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; orphans: 2; text-align: -webkit-auto; text-indent: 0px; text-transform: none; white-space: normal; widows: 2; word-spacing: 0px; -webkit-text-size-adjust: auto; -webkit-text-stroke-width: 0px; "><span style="color: rgb(0, 0, 0); font-family: Helvetica; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; orphans: 2; text-align: -webkit-auto; text-indent: 0px; text-transform: none; white-space: normal; widows: 2; word-spacing: 0px; -webkit-text-size-adjust: auto; -webkit-text-stroke-width: 0px; display: inline !important; float: none; ">6721 WD Bennekom</span><br style="color: rgb(0, 0, 0); font-family: Helvetica; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; orphans: 2; text-align: -webkit-auto; text-indent: 0px; text-transform: none; white-space: normal; widows: 2; word-spacing: 0px; -webkit-text-size-adjust: auto; -webkit-text-stroke-width: 0px; "><span style="color: rgb(0, 0, 0); font-family: Helvetica; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; orphans: 2; text-align: -webkit-auto; text-indent: 0px; text-transform: none; white-space: normal; widows: 2; word-spacing: 0px; -webkit-text-size-adjust: auto; -webkit-text-stroke-width: 0px; display: inline !important; float: none; ">The Netherlands</span><br style="color: rgb(0, 0, 0); font-family: Helvetica; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; orphans: 2; text-align: -webkit-auto; text-indent: 0px; text-transform: none; white-space: normal; widows: 2; word-spacing: 0px; -webkit-text-size-adjust: auto; -webkit-text-stroke-width: 0px; "><span style="color: rgb(0, 0, 0); font-family: Helvetica; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; orphans: 2; text-align: -webkit-auto; text-indent: 0px; text-transform: none; white-space: normal; widows: 2; word-spacing: 0px; -webkit-text-size-adjust: auto; -webkit-text-stroke-width: 0px; display: inline !important; float: none; ">Tel: +31 (0)6 81286572</span><br style="color: rgb(0, 0, 0); font-family: Helvetica; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; orphans: 2; text-align: -webkit-auto; text-indent: 0px; text-transform: none; white-space: normal; widows: 2; word-spacing: 0px; -webkit-text-size-adjust: auto; -webkit-text-stroke-width: 0px; "><span style="color: rgb(0, 0, 0); font-family: Helvetica; font-size: medium; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; orphans: 2; text-align: -webkit-auto; text-indent: 0px; text-transform: none; white-space: normal; widows: 2; word-spacing: 0px; -webkit-text-size-adjust: auto; -webkit-text-stroke-width: 0px; display: inline !important; float: none; "><a href="http://geocat.net">http://geocat.net</a></span><br style="color: rgb(0, 0, 0); font-family: Helvetica; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; orphans: 2; text-align: -webkit-auto; text-indent: 0px; text-transform: none; white-space: normal; widows: 2; word-spacing: 0px; -webkit-text-size-adjust: auto; -webkit-text-stroke-width: 0px; "><span style="color: rgb(0, 0, 0); font-family: Helvetica; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; orphans: 2; text-align: -webkit-auto; text-indent: 0px; text-transform: none; white-space: normal; widows: 2; word-spacing: 0px; -webkit-text-size-adjust: auto; -webkit-text-stroke-width: 0px; "></span><br style="color: rgb(0, 0, 0); font-family: Helvetica; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; orphans: 2; text-align: -webkit-auto; text-indent: 0px; text-transform: none; white-space: normal; widows: 2; word-spacing: 0px; -webkit-text-size-adjust: auto; -webkit-text-stroke-width: 0px; "><span style="color: rgb(0, 0, 0); font-family: Helvetica; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; orphans: 2; text-align: -webkit-auto; text-indent: 0px; text-transform: none; white-space: normal; widows: 2; word-spacing: 0px; -webkit-text-size-adjust: auto; -webkit-text-stroke-width: 0px; "></span><span style="color: rgb(0, 0, 0); font-family: Helvetica; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; orphans: 2; text-align: -webkit-auto; text-indent: 0px; text-transform: none; white-space: normal; widows: 2; word-spacing: 0px; -webkit-text-size-adjust: auto; -webkit-text-stroke-width: 0px; "></span><span style="color: rgb(0, 0, 0); font-family: Helvetica; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; orphans: 2; text-align: -webkit-auto; text-indent: 0px; text-transform: none; white-space: normal; widows: 2; word-spacing: 0px; -webkit-text-size-adjust: auto; -webkit-text-stroke-width: 0px; "></span><span style="color: rgb(0, 0, 0); font-family: Helvetica; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; orphans: 2; text-align: -webkit-auto; text-indent: 0px; text-transform: none; white-space: normal; widows: 2; word-spacing: 0px; -webkit-text-size-adjust: auto; -webkit-text-stroke-width: 0px; "><span><span><span><span><span><span><span><img height="20" width="95" apple-inline="yes" id="910FBDF7-37EE-4A04-95F0-539D3A0F6DD4" apple-width="yes" apple-height="yes" src="cid:B0949C11-3920-4536-B5D5-DD637E5C6532"></span><span style="font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; orphans: 2; text-align: -webkit-auto; text-indent: 0px; text-transform: none; white-space: normal; widows: 2; word-spacing: 0px; -webkit-text-size-adjust: auto; -webkit-text-stroke-width: 0px; color: rgb(42, 167, 223); font-family: Arial; font-size: 10px; ">Please consider the environment before printing this email.</span>
</span></span></span></span></span></span></span></div>
<br><div><div>On 5 mrt. 2014, at 18:14, Steve Richard <<a href="mailto:steve.richard@azgs.az.gov">steve.richard@azgs.az.gov</a>> wrote:</div><br class="Apple-interchange-newline"><blockquote type="cite"><div lang="EN-US" link="blue" vlink="purple" style="font-family: Helvetica; font-size: 12px; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; orphans: auto; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; widows: auto; word-spacing: 0px; -webkit-text-stroke-width: 0px;"><div class="WordSection1" style="page: WordSection1;"><div style="margin: 0in 0in 0.0001pt; font-size: 12pt; font-family: 'Times New Roman', serif;"><span style="font-size: 11pt; font-family: Calibri, sans-serif; color: rgb(31, 73, 125);">Good point. The name recognition is important. Jeroen, what can you tell us about metadata101—it looks pretty new.<o:p></o:p></span></div><div style="margin: 0in 0in 0.0001pt; font-size: 12pt; font-family: 'Times New Roman', serif;"><span style="font-size: 11pt; font-family: Calibri, sans-serif; color: rgb(31, 73, 125);"> </span></div><div style="margin: 0in 0in 0.0001pt; font-size: 12pt; font-family: 'Times New Roman', serif;"><span style="font-size: 11pt; font-family: Calibri, sans-serif; color: rgb(31, 73, 125);">Stephen M Richard<o:p></o:p></span></div><div style="margin: 0in 0in 0.0001pt; font-size: 12pt; font-family: 'Times New Roman', serif;"><span style="font-size: 11pt; font-family: Calibri, sans-serif; color: rgb(31, 73, 125);">Arizona Geological Survey<o:p></o:p></span></div><div style="margin: 0in 0in 0.0001pt; font-size: 12pt; font-family: 'Times New Roman', serif;"><span style="font-size: 11pt; font-family: Calibri, sans-serif; color: rgb(31, 73, 125);">416 W. Congress #100<o:p></o:p></span></div><div style="margin: 0in 0in 0.0001pt; font-size: 12pt; font-family: 'Times New Roman', serif;"><span style="font-size: 11pt; font-family: Calibri, sans-serif; color: rgb(31, 73, 125);">Tucson, AZ<o:p></o:p></span></div><div style="margin: 0in 0in 0.0001pt; font-size: 12pt; font-family: 'Times New Roman', serif;"><span style="font-size: 11pt; font-family: Calibri, sans-serif; color: rgb(31, 73, 125);">AZGS: 520-770-3500<o:p></o:p></span></div><div style="margin: 0in 0in 0.0001pt; font-size: 12pt; font-family: 'Times New Roman', serif;"><span style="font-size: 11pt; font-family: Calibri, sans-serif; color: rgb(31, 73, 125);">Office: 520-209-4127<o:p></o:p></span></div><div style="margin: 0in 0in 0.0001pt; font-size: 12pt; font-family: 'Times New Roman', serif;"><span style="font-size: 11pt; font-family: Calibri, sans-serif; color: rgb(31, 73, 125);">FAX: 520-770-3505<o:p></o:p></span></div><div style="margin: 0in 0in 0.0001pt; font-size: 12pt; font-family: 'Times New Roman', serif;"><span style="font-size: 11pt; font-family: Calibri, sans-serif; color: rgb(31, 73, 125);"> </span></div><div style="border-style: none none none solid; border-left-color: blue; border-left-width: 1.5pt; padding: 0in 0in 0in 4pt;"><div><div style="border-style: solid none none; border-top-color: rgb(181, 196, 223); border-top-width: 1pt; padding: 3pt 0in 0in;"><div style="margin: 0in 0in 0.0001pt; font-size: 12pt; font-family: 'Times New Roman', serif;"><b><span style="font-size: 10pt; font-family: Tahoma, sans-serif;">From:</span></b><span style="font-size: 10pt; font-family: Tahoma, sans-serif;"><span class="Apple-converted-space"> </span>Rich Signell [via<span class="Apple-converted-space"> </span><a href="http://osgeo.org/" style="color: purple; text-decoration: underline;">OSGeo.org</a>] [<a href="mailto:ml-node+s1560n5107725h56@n6.nabble.com" style="color: purple; text-decoration: underline;">mailto:ml-node+s1560n5107725h56@n6.nabble.com</a>]<span class="Apple-converted-space"> </span><br><b>Sent:</b><span class="Apple-converted-space"> </span>Wednesday, March 05, 2014 10:13 AM<br><b>To:</b><span class="Apple-converted-space"> </span>Steve Richard<br><b>Subject:</b><span class="Apple-converted-space"> </span>Re: [cat-interop] Metadata link types vocabulary proposal<o:p></o:p></span></div></div></div><div style="margin: 0in 0in 0.0001pt; font-size: 12pt; font-family: 'Times New Roman', serif;"><o:p> </o:p></div><div style="margin: 0in 0in 0.0001pt; font-size: 12pt; font-family: 'Times New Roman', serif;">I like the git idea, but would vote for osgeo github as a location, if<span class="Apple-converted-space"> </span><br>only because it has more name recognition at this point.<span class="Apple-converted-space"> </span><br><br>On Wed, Mar 5, 2014 at 8:54 AM, Jeroen Ticheler<span class="Apple-converted-space"> </span><br><<a href="x-msg://24/user/SendEmail.jtp?type=node&node=5107725&i=0" target="_top" style="color: purple; text-decoration: underline;">[hidden email]</a>> wrote:<o:p></o:p></div><div><div style="margin: 0in 0in 0.0001pt; font-size: 12pt; font-family: 'Times New Roman', serif;"><br>> Hi Tom and others,<span class="Apple-converted-space"> </span><br>><span class="Apple-converted-space"> </span><br>> We are working on getting metadata profiles developed in a separate git repository<span class="Apple-converted-space"> </span><a href="https://github.com/metadata101" target="_top" style="color: purple; text-decoration: underline;">https://github.com/metadata101</a> and published under<a href="http://metadata101.org/" target="_top" style="color: purple; text-decoration: underline;">http://metadata101.org</a> . This allows people to work on a range of metadata profiles while maintaining a common basis, so that applications can use these profiles from a single source.<span class="Apple-converted-space"> </span><br>><span class="Apple-converted-space"> </span><br>> Would you be open to the idea to also host the vocabularies under that same umbrella? It would not be related to a specific project or foundation, which could help to get wide acceptance across open source and proprietary applications. This would be a great benefit for interoperability in my opinion.<span class="Apple-converted-space"> </span><br>><span class="Apple-converted-space"> </span><br>> A build process could ensure the vocabularies are kept up to date under<span class="Apple-converted-space"> </span><a href="http://metadata101.org/" target="_top" style="color: purple; text-decoration: underline;">http://metadata101.org</a> while they are developed and versioned on Github.<span class="Apple-converted-space"> </span><br>><span class="Apple-converted-space"> </span><br>> My 2 cents,<span class="Apple-converted-space"> </span><br>> Jeroen<span class="Apple-converted-space"> </span><br>><span class="Apple-converted-space"> </span><br>><span class="Apple-converted-space"> </span><br>> On 5 mrt. 2014, at 14:12, Tom Kralidis <<a href="x-msg://24/user/SendEmail.jtp?type=node&node=5107725&i=1" target="_top" style="color: purple; text-decoration: underline;">[hidden email]</a>> wrote:<span class="Apple-converted-space"> </span><br>><span class="Apple-converted-space"> </span><br>>><span class="Apple-converted-space"> </span><br>>> Thinking this though more, I think the way forward here is for this<span class="Apple-converted-space"> </span><br>>> to be an OSGeo vocabulary, which we can build and manage under<span class="Apple-converted-space"> </span><br>>><span class="Apple-converted-space"> </span><a href="http://osgeo.org/vocab" target="_top" style="color: purple; text-decoration: underline;">http://osgeo.org/vocab</a> like:<span class="Apple-converted-space"> </span><br>>><span class="Apple-converted-space"> </span><br>>><span class="Apple-converted-space"> </span><a href="http://osgeo.org/vocab/data/" target="_top" style="color: purple; text-decoration: underline;">http://osgeo.org/vocab/data/</a>{provider}/{type}[/version]<span class="Apple-converted-space"> </span><br>>><span class="Apple-converted-space"> </span><a href="http://osgeo.org/vocab/service/" target="_top" style="color: purple; text-decoration: underline;">http://osgeo.org/vocab/service/</a>{provider}/{type}[/version]<span class="Apple-converted-space"> </span><br>>><span class="Apple-converted-space"> </span><br>>> Then providing a thin resolution layer, members of this vocabulary, when<span class="Apple-converted-space"> </span><br>>> invoked via HTTP, would then dereference/resolve accordingly. Like:<span class="Apple-converted-space"> </span><br>>><span class="Apple-converted-space"> </span><br>>><span class="Apple-converted-space"> </span><a href="http://osgeo.org/vocab/service/ogc/sos/1.0" target="_top" style="color: purple; text-decoration: underline;">http://osgeo.org/vocab/service/ogc/sos/1.0</a><br>>><span class="Apple-converted-space"> </span><br>>> would resolve to:<span class="Apple-converted-space"> </span><br>>><span class="Apple-converted-space"> </span><br>>><span class="Apple-converted-space"> </span><a href="http://www.opengis.net/sos/1.0" target="_top" style="color: purple; text-decoration: underline;">http://www.opengis.net/sos/1.0</a> (which then resolves as per the<span class="Apple-converted-space"> </span><br>>> authoritative provider's wishes).<span class="Apple-converted-space"> </span><br>>><span class="Apple-converted-space"> </span><br>>> This provides the following benefits:<span class="Apple-converted-space"> </span><br>>><span class="Apple-converted-space"> </span><br>>> 1./ metadata clients/servers can bind to the OSGeo vocabulary, thus<span class="Apple-converted-space"> </span><br>>> realizing the core goal of a harmonized link type list<span class="Apple-converted-space"> </span><br>>> 2./ anyone who really wants to invoke / resolve these can do so<span class="Apple-converted-space"> </span><br>>> 3./ This keeps OSGeo as a just a gatekeeper / custodian of the list with<span class="Apple-converted-space"> </span><br>>> redirects as appropriate, which gets us out of the complexity of<span class="Apple-converted-space"> </span><br>>> managing these across standards orgs/etc.<span class="Apple-converted-space"> </span><br>>><span class="Apple-converted-space"> </span><br>>> Comments? I've written a small Flask app to act as a high level<span class="Apple-converted-space"> </span><br>>> resolver, based on our link types list and will resolve / redirect<span class="Apple-converted-space"> </span><br>>> accordingly, which we can push forward for hosting, etc.<span class="Apple-converted-space"> </span><br>>><span class="Apple-converted-space"> </span><br>>><span class="Apple-converted-space"> </span><br>>><span class="Apple-converted-space"> </span><br>>> On Mon, 3 Mar 2014, Tom Kralidis wrote:<span class="Apple-converted-space"> </span><br>>><span class="Apple-converted-space"> </span><br>>>> Date: Mon, 3 Mar 2014 21:53:51 -0500<span class="Apple-converted-space"> </span><br>>>> From: Tom Kralidis <<a href="x-msg://24/user/SendEmail.jtp?type=node&node=5107725&i=2" target="_top" style="color: purple; text-decoration: underline;">[hidden email]</a>><span class="Apple-converted-space"> </span><br>>>> To: Paul van Genuchten <<a href="x-msg://24/user/SendEmail.jtp?type=node&node=5107725&i=3" target="_top" style="color: purple; text-decoration: underline;">[hidden email]</a>><span class="Apple-converted-space"> </span><br>>>> Cc: "<<a href="x-msg://24/user/SendEmail.jtp?type=node&node=5107725&i=4" target="_top" style="color: purple; text-decoration: underline;">[hidden email]</a>>" <<a href="x-msg://24/user/SendEmail.jtp?type=node&node=5107725&i=5" target="_top" style="color: purple; text-decoration: underline;">[hidden email]</a>><span class="Apple-converted-space"> </span><br>>>> Subject: Re: [cat-interop] Metadata link types vocabulary proposal<span class="Apple-converted-space"> </span><br>>>> On Mon, Mar 3, 2014 at 4:07 PM, Paul van Genuchten<span class="Apple-converted-space"> </span><br>>>> <<a href="x-msg://24/user/SendEmail.jtp?type=node&node=5107725&i=6" target="_top" style="color: purple; text-decoration: underline;">[hidden email]</a>> wrote:<span class="Apple-converted-space"> </span><br>>>>> I support Stephan at this point. The semantic web can be a big consumer<span class="Apple-converted-space"> </span><br>>>>> of spatial data services, if we're able to optimally embed our data in<span class="Apple-converted-space"> </span><br>>>>> it. Linking to controlled vocabularies by url is a big facilitator.<span class="Apple-converted-space"> </span><br>>>>><span class="Apple-converted-space"> </span><br>>>><span class="Apple-converted-space"> </span><br>>>> Good points.<span class="Apple-converted-space"> </span><br>>>><span class="Apple-converted-space"> </span><br>>>>> Sure i see the point of having a urn structure as<span class="Apple-converted-space"> </span><br>>>>> {provider}:{type}:{identifier}:{version}. But this can also be managed<span class="Apple-converted-space"> </span><br>>>>> in a (skos) vocabulary-identifier-as-url by using identifiers like:<span class="Apple-converted-space"> </span><br>>>>><span class="Apple-converted-space"> </span><br>>>>> for example:<span class="Apple-converted-space"> </span><br>>>>><span class="Apple-converted-space"> </span><a href="http://osgeo.org/vocab/service/ogc/wms/1.1" target="_top" style="color: purple; text-decoration: underline;">http://osgeo.org/vocab/service/ogc/wms/1.1</a><br>>>>><span class="Apple-converted-space"> </span><a href="http://osgeo.org/vocab/service/opensearch/opensearch/2.0" target="_top" style="color: purple; text-decoration: underline;">http://osgeo.org/vocab/service/opensearch/opensearch/2.0</a><br>>>>><span class="Apple-converted-space"> </span><br>>>>> and<span class="Apple-converted-space"> </span><br>>>>><span class="Apple-converted-space"> </span><br>>>>><span class="Apple-converted-space"> </span><a href="http://osgeo.org/vocab/mediatype/esri/shapefile/1.0" target="_top" style="color: purple; text-decoration: underline;">http://osgeo.org/vocab/mediatype/esri/shapefile/1.0</a><br>>>>><span class="Apple-converted-space"> </span><a href="http://osgeo.org/vocab/mediatype/ogc/gml/2.0" target="_top" style="color: purple; text-decoration: underline;">http://osgeo.org/vocab/mediatype/ogc/gml/2.0</a><br>>>>><span class="Apple-converted-space"> </span><a href="http://osgeo.org/vocab/mediatype/w3c/json-ld/1.0" target="_top" style="color: purple; text-decoration: underline;">http://osgeo.org/vocab/mediatype/w3c/json-ld/1.0</a><br>>>>><span class="Apple-converted-space"> </span><br>>>>> or<span class="Apple-converted-space"> </span><br>>>>><span class="Apple-converted-space"> </span><br>>>>><span class="Apple-converted-space"> </span><a href="http://osgeo.org/vocab/service#ogc_wms_1_1" target="_top" style="color: purple; text-decoration: underline;">http://osgeo.org/vocab/service#ogc_wms_1_1</a><br>>>>><span class="Apple-converted-space"> </span><a href="http://osgeo.org/vocab/mediatype#ogc_gml_2_0" target="_top" style="color: purple; text-decoration: underline;">http://osgeo.org/vocab/mediatype#ogc_gml_2_0</a><br>>>>><span class="Apple-converted-space"> </span><br>>>>> At this point we should consider if<span class="Apple-converted-space"> </span><a href="http://osgeo.org/" style="color: purple; text-decoration: underline;">osgeo.org</a><span class="Apple-converted-space"> </span>is the best place to set<span class="Apple-converted-space"> </span><br>>>>> up such a service/vocab, as this is more a data-matter then a software<span class="Apple-converted-space"> </span><br>>>>> matter. Should we connect with geovocab, w3c/ogc, dbpedia to have this<span class="Apple-converted-space"> </span><br>>>>> set up?<span class="Apple-converted-space"> </span><br>>>>><span class="Apple-converted-space"> </span><br>>>><span class="Apple-converted-space"> </span><br>>>> Based on the comments on HTTP URIs at<span class="Apple-converted-space"> </span><br>>>><span class="Apple-converted-space"> </span><a href="https://github.com/OSGeo/Cat-Interop/issues/3" target="_top" style="color: purple; text-decoration: underline;">https://github.com/OSGeo/Cat-Interop/issues/3</a>, the OGC has this at<span class="Apple-converted-space"> </span><br>>>><span class="Apple-converted-space"> </span><a href="http://www.opengis.net/" style="color: purple; text-decoration: underline;">www.opengis.net</a>. However the structure is not SKOS-like. I guess one<span class="Apple-converted-space"> </span><br>>>> factor is how deep version negotiation would go.<span class="Apple-converted-space"> </span><br>>>><span class="Apple-converted-space"> </span><br>>>> Then again, we could implement this in OSGeo and have resolver back to<span class="Apple-converted-space"> </span><br>>>> their authoritative resources (i.e.<span class="Apple-converted-space"> </span><br>>>><span class="Apple-converted-space"> </span><a href="http://osgeo.org/vocab/service/csw/2.0.2" target="_top" style="color: purple; text-decoration: underline;">http://osgeo.org/vocab/service/csw/2.0.2</a> could resolve to<span class="Apple-converted-space"> </span><br>>>><span class="Apple-converted-space"> </span><a href="http://www.opengis.net/cat/csw/2.0.2" target="_top" style="color: purple; text-decoration: underline;">http://www.opengis.net/cat/csw/2.0.2</a>. Does this sound useful/make<span class="Apple-converted-space"> </span><br>>>> sense?<span class="Apple-converted-space"> </span><br>>>><span class="Apple-converted-space"> </span><br>>>>> If we feel<span class="Apple-converted-space"> </span><a href="http://osgeo.org/" style="color: purple; text-decoration: underline;">osgeo.org</a><span class="Apple-converted-space"> </span>is a good place, let's post about it in the<span class="Apple-converted-space"> </span><br>>>>> request-list...<span class="Apple-converted-space"> </span><br>>>>><span class="Apple-converted-space"> </span><br>>>>> _______________________________________________<span class="Apple-converted-space"> </span><br>>>>> cat-interop mailing list<span class="Apple-converted-space"> </span><br>>>>><span class="Apple-converted-space"> </span><a href="x-msg://24/user/SendEmail.jtp?type=node&node=5107725&i=7" target="_top" style="color: purple; text-decoration: underline;">[hidden email]</a><span class="Apple-converted-space"> </span><br>>>>><span class="Apple-converted-space"> </span><a href="http://lists.osgeo.org/cgi-bin/mailman/listinfo/cat-interop" target="_top" style="color: purple; text-decoration: underline;">http://lists.osgeo.org/cgi-bin/mailman/listinfo/cat-interop</a><br>>>><span class="Apple-converted-space"> </span><br>><span class="Apple-converted-space"> </span><br>><span class="Apple-converted-space"> </span><br>> _______________________________________________<span class="Apple-converted-space"> </span><br>> cat-interop mailing list<span class="Apple-converted-space"> </span><br>><span class="Apple-converted-space"> </span><a href="x-msg://24/user/SendEmail.jtp?type=node&node=5107725&i=8" target="_top" style="color: purple; text-decoration: underline;">[hidden email]</a><span class="Apple-converted-space"> </span><br>><span class="Apple-converted-space"> </span><a href="http://lists.osgeo.org/cgi-bin/mailman/listinfo/cat-interop" target="_top" style="color: purple; text-decoration: underline;">http://lists.osgeo.org/cgi-bin/mailman/listinfo/cat-interop</a><br>><o:p></o:p></div></div><p class="MsoNormal" style="margin: 0in 0in 12pt; font-size: 12pt; font-family: 'Times New Roman', serif;"><br><br><br>--<span class="Apple-converted-space"> </span><br>Dr. Richard P. Signell (508) 457-2229<span class="Apple-converted-space"> </span><br>USGS, 384 Woods Hole Rd.<span class="Apple-converted-space"> </span><br>Woods Hole, MA 02543-1598<span class="Apple-converted-space"> </span><br>_______________________________________________<span class="Apple-converted-space"> </span><br>cat-interop mailing list<span class="Apple-converted-space"> </span><br><a href="x-msg://24/user/SendEmail.jtp?type=node&node=5107725&i=9" target="_top" style="color: purple; text-decoration: underline;">[hidden email]</a><span class="Apple-converted-space"> </span><br><a href="http://lists.osgeo.org/cgi-bin/mailman/listinfo/cat-interop" target="_top" style="color: purple; text-decoration: underline;">http://lists.osgeo.org/cgi-bin/mailman/listinfo/cat-interop</a><br><br><o:p></o:p></p><div class="MsoNormal" align="center" style="margin: 0in 0in 0.0001pt; font-size: 12pt; font-family: 'Times New Roman', serif; text-align: center;"><hr size="1" width="100%" noshade="" align="center" style="color: rgb(204, 204, 204);"></div><div><div><div style="margin: 0in 0in 0.0001pt; font-size: 12pt; font-family: 'Times New Roman', serif;"><b><span style="font-size: 9pt; font-family: Tahoma, sans-serif; color: rgb(68, 68, 68);">If you reply to this email, your message will be added to the discussion below:<o:p></o:p></span></b></div></div><div style="margin: 0in 0in 0.0001pt; font-size: 12pt; font-family: 'Times New Roman', serif;"><span style="font-size: 9pt; font-family: Tahoma, sans-serif; color: rgb(68, 68, 68);"><a href="http://osgeo-org.1560.x6.nabble.com/cat-interop-Metadata-link-types-vocabulary-proposal-tp5106675p5107725.html" style="color: purple; text-decoration: underline;">http://osgeo-org.1560.x6.nabble.com/cat-interop-Metadata-link-types-vocabulary-proposal-tp5106675p5107725.html</a><o:p></o:p></span></div></div><div style="margin-top: 4.8pt;"><div style="margin: 0in 0in 0.0001pt; font-size: 12pt; font-family: 'Times New Roman', serif; line-height: 18pt;"><span style="font-size: 8.5pt; font-family: Tahoma, sans-serif; color: rgb(102, 102, 102);">To unsubscribe from Cat-Interop,<span class="Apple-converted-space"> </span><a href="http://osgeo-org.1560.x6.nabble.com/template/NamlServlet.jtp?macro=unsubscribe_by_code&node=5079187&code=c3RldmUucmljaGFyZEBhemdzLmF6Lmdvdnw1MDc5MTg3fC0xMDkwNzA1OTU0" style="color: purple; text-decoration: underline;">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" style="color: purple; text-decoration: underline;"><span style="font-size: 7pt; font-family: 'Times New Roman', serif;">NAML</span></a></span></div></div></div></div></div></blockquote></div><br></div></div></div></body></html>