<p>"<a href="https://tools.ietf.org/html/rfc2169" rel="nofollow">URN resolver</a>" is an old technical name that can be reused here with some adaptations... The main goal is to avoid confusion with "free text searches". URNs are controlled names, like the <a href="https://en.wikipedia.org/wiki/ISO_3166-2" rel="nofollow">ISO 3166-2</a> codes for country names (AR=Argentina, BR=Brazil, FR=France, etc.) and its subdivisions (e.g. BR-AM, BR-SP, BR-PA are subdivisions defined by <a href="https://en.wikipedia.org/wiki/ISO_3166-2:BR" rel="nofollow">ISO 3166-2:BR</a>).</p>
<p>There are many ways to define a syntax for namespaces or controlled names, suppose the <code>urn:lex</code> schema for jurisdiction names... Examples:</p>
<ul>
<li>
<p><a href="https://www.openstreetmap.org/relation/7408" rel="nofollow"><code>osm.org/urn:lex:FR</code></a> would be a short and reliable link to the <strong>France</strong> map.</p>
</li>
<li>
<p><a href="https://www.openstreetmap.org/relation/7408" rel="nofollow"><code>osm.org/urn:lex:FR-37</code></a>, as defined by <a href="https://en.wikipedia.org/wiki/ISO_3166-2:FR" rel="nofollow">ISO 3166-2:FR</a>, would be a short and reliable link to the <strong>France/Indre-et-Loire</strong> map.</p>
</li>
<li>
<p><a href="https://www.openstreetmap.org/relation/298285" rel="nofollow"><code>osm.org/urn:lex:BR-SP-SaoPaulo</code></a>, to the <strong>Brasil/São Paulo/São Paulo</strong> map.</p>
</li>
<li>
<p><a href="https://www.openstreetmap.org/relation/185554" rel="nofollow"><code>osm.org/urn:lex:BR-PA-Altamira</code></a>, to the <strong>Brasil/Pará/Altamira</strong> map.</p>
</li>
<li>
<p><a href="https://www.openstreetmap.org/relation/185579" rel="nofollow"><code>osm.org/urn:lex:BR-PA</code></a>, to the <strong>Brasil/Pará</strong> map.</p>
</li>
<li>
<p>... each link, with its judistiction code, would be a short and reliable link to each full name.</p>
</li>
</ul>
<p><strong>Short, reliable and persistent</strong> way to link OSM administrative boundaris.</p>
<hr>
<p>With this <strong>same infrastructure</strong> of redirecting controled names, we can add location identifiers, as the OLC code discussed at <a class="issue-link js-issue-link" data-error-text="Failed to load issue title" data-id="310542210" data-permission-text="Issue title is private" data-url="https://github.com/openstreetmap/openstreetmap-website/issues/1807" data-hovercard-type="issue" data-hovercard-url="/openstreetmap/openstreetmap-website/issues/1807/hovercard" href="https://github.com/openstreetmap/openstreetmap-website/issues/1807">#1807</a> or another relevant one, like Geohash. Examples:</p>
<ul>
<li>
<p><code>http://osm.org/geo:{geoUriValue}</code> a resolver for the <a href="https://tools.ietf.org/html/rfc5870" rel="nofollow">RFC 5870's</a> strings, the <code>geo</code> URI protocol.</p>
</li>
<li>
<p><code>http://osm.org/olc/{olcCode}</code> for original OpenLocationCode 8+N digits geocodes, without context.</p>
</li>
<li>
<p><code>http://osm.org/ghs/{geohashCode}</code> for original <a href="https://en.wikipedia.org/wiki/Geohash" rel="nofollow">Geohash</a>, without context. PostGIS, at OSM server, offers <a href="https://postgis.net/docs/ST_PointFromGeoHash.html" rel="nofollow">ST_PointFromGeoHash()</a>.</p>
</li>
<li>
<p>...</p>
</li>
<li>
<p><code>http://osm.org/pluscode/{context}/{olcShortCode}</code> for PlusCode-like short-OpenLocationCode, with 6+N digits geocodes. The <strong>context</strong> can be resolved by the URN schema described above (e.g. context "FR-37" for France/Indre-et-Loire, context "BR-PA-Altamira" for Brasil/Pará/Altamira).</p>
</li>
</ul>
<p style="font-size:small;-webkit-text-size-adjust:none;color:#666;">—<br />You are receiving this because you are subscribed to this thread.<br />Reply to this email directly, <a href="https://github.com/openstreetmap/openstreetmap-website/issues/2099">view it on GitHub</a>, or <a href="https://github.com/notifications/unsubscribe-auth/ABWnLfCw-SMpiZR33JpPUhxDYJSNLVXQks5vACiMgaJpZM4ZvHgA">mute the thread</a>.<img src="https://github.com/notifications/beacon/ABWnLYl784CGXlDGszZslmjz5-vU6XjSks5vACiMgaJpZM4ZvHgA.gif" height="1" width="1" alt="" /></p>
<script type="application/json" data-scope="inboxmarkup">{"api_version":"1.0","publisher":{"api_key":"05dde50f1d1a384dd78767c55493e4bb","name":"GitHub"},"entity":{"external_key":"github/openstreetmap/openstreetmap-website","title":"openstreetmap/openstreetmap-website","subtitle":"GitHub repository","main_image_url":"https://github.githubassets.com/images/email/message_cards/header.png","avatar_image_url":"https://github.githubassets.com/images/email/message_cards/avatar.png","action":{"name":"Open in GitHub","url":"https://github.com/openstreetmap/openstreetmap-website"}},"updates":{"snippets":[{"icon":"DESCRIPTION","message":"Short links to controlled names at OSM website (#2099)"}],"action":{"name":"View Issue","url":"https://github.com/openstreetmap/openstreetmap-website/issues/2099"}}}</script>
<script type="application/ld+json">[
{
"@context": "http://schema.org",
"@type": "EmailMessage",
"potentialAction": {
"@type": "ViewAction",
"target": "https://github.com/openstreetmap/openstreetmap-website/issues/2099",
"url": "https://github.com/openstreetmap/openstreetmap-website/issues/2099",
"name": "View Issue"
},
"description": "View this Issue on GitHub",
"publisher": {
"@type": "Organization",
"name": "GitHub",
"url": "https://github.com"
}
}
]</script>