Hello Allan,

sorry, I'm a late comer to the discussion, so there might be something I've/am 
missed/missing, but...

From your description I understand that "embassy=*", "consulate=*" and 
"liaison=*" will be new first level keys: wouldn't it be better to make them 
secondary level keys under the "diplomatic" /namespace/, exactly as you are 
proposing for "services" (/and maybe also add "services"" as a possible value 
for "diplomatic=*"/) ?

We should then have:

  * diplomatic:embassy 
<https://wiki.openstreetmap.org/w/index.php?title=Key:embassy&action=edit&redlink=1>=*
 with key values of [yes, high_commission, nunciature, interests_section, 
mission, delegation, branch_embassy, residence]
  * diplomatic:consulate 
<https://wiki.openstreetmap.org/w/index.php?title=Key:consulate&action=edit&redlink=1>=*
 with key values of {yes, consulate_general, consular_agency, consular_office, 
honorary_consul]
  * diplomatic:liaison 
<https://wiki.openstreetmap.org/w/index.php?title=Key:liaison&action=edit&redlink=1>=*
 with key values of [liaison_office, representative_office, subnational];

Cheers,

Sergio


On 2018-11-11 12:40, Allan Mustard wrote:
>
> Here, please take a look at the updated Tagging section of the proposal and 
> see if that solves the issue.  I include a link to the Wikipedia article on 
> ISO 3166-1 alpha-2 codes.
>
> https://wiki.openstreetmap.org/wiki/Proposed_features/office%3Ddiplomatic#Tagging
>
> *Current Proposal:*
>
>   * establish formally the office 
> <https://wiki.openstreetmap.org/wiki/Key:office>=diplomatic 
> <https://wiki.openstreetmap.org/w/index.php?title=Tag:office%3Ddiplomatic&action=edit&redlink=1>
>  primary tag/key value combination, with the following additional (secondary 
> and tertiary) tags:
>       o diplomatic <https://wiki.openstreetmap.org/wiki/Key:diplomatic>=* 
> with key values of [embassy, consulate, liaison]
>           + embassy 
> <https://wiki.openstreetmap.org/w/index.php?title=Key:embassy&action=edit&redlink=1>=*
>  with key values of [yes, high_commission, nunciature, interests_section, 
> mission, delegation, branch_embassy, residence]
>           + consulate 
> <https://wiki.openstreetmap.org/w/index.php?title=Key:consulate&action=edit&redlink=1>=*
>  with key values of {yes, consulate_general, consular_agency, 
> consular_office, honorary_consul]
>           + liaison 
> <https://wiki.openstreetmap.org/w/index.php?title=Key:liaison&action=edit&redlink=1>=*
>  with key values of [liaison_office, representative_office, subnational];
>
>   * establish formally diplomatic:services:*=[yes/no] additional (tertiary) 
> tag with the following options:
>      o
>           + diplomatic:services:non-immigrant_visas*=[yes/no]
>           + diplomatic:services:immigrant_visas=[yes/no]
>           + diplomatic:services:citizen_services=[yes/no]; and
>
>   * deprecate the amenity=embassy tag over a period of time.
>
> Additional tags routinely used would include:
>
>   * country <https://wiki.openstreetmap.org/wiki/Key:country>=* where * is 
> thetwo-character ISO 3166-1 alpha-2 code 
> <https://en.wikipedia.org/wiki/ISO_3166-1_alpha-2>for the sending country or 
> organization or the generally accepted English acronym for an international 
> organization (e.g., UN, OSCE);
>   * name <https://wiki.openstreetmap.org/wiki/Key:name>=* where * is the name 
> of the mission;
>   * target <https://wiki.openstreetmap.org/wiki/Key:target>=* where * is 
> thetwo-character ISO 3166-1 alpha-2 code 
> <https://en.wikipedia.org/wiki/ISO_3166-1_alpha-2>for the receiving 
> (accrediting) country or organization or the generally accepted English 
> acronym for an international organization (e.g., UN, OSCE, NATO, WTO). If a 
> mission is accredited to multiple countries or organizations, * will 
> constitute a semicolon-delimited list of tags, e.g., target 
> <https://wiki.openstreetmap.org/wiki/Key:target>=US;CA 
> <https://wiki.openstreetmap.org/w/index.php?title=Tag:target%3DUS;CA&action=edit&redlink=1>
>  for a mission accredited to both the United States and Canada.
>
> and of course the address and other contact information.
>
>
> On 11/11/2018 3:52 PM, Colin Smale wrote:
>>
>> On 2018-11-11 11:27, Warin wrote:
>>
>>> On 11/11/18 20:05, Colin Smale wrote:
>>>>
>>>> On 2018-11-11 07:49, Graeme Fitzpatrick wrote:
>>>>
>>>>      
>>>>     But wouldn't it be covered by the name eg "Australian Embassy to 
>>>> Russia"?
>>>>      
>>>>
>>>> We should not rely on free-text fields like "name" to convey information 
>>>> that belongs in a structured form...
>>>
>>> The text clearly identifies the object as;
>>> an Embassy
>>> The 'from' country as Australia
>>> the 'to' country ... as Russia ... though this may also include other 
>>> countries too ..and would be indicated by an enclosure by that county.
>>
>> You miss the point... The fact that the words "Australian Embassy" and/or 
>> "to Russia" occur in the "name" tag is not enough for an automated processor 
>> to unambiguously understand that the sending nation is the Commonwealth of 
>> Australia and the receiving nation is the Russian Federation. All these 
>> words can be written in any language of the world. Hence the need for the 
>> "from," "to" and "function" concepts to be modelled with a curated list of 
>> values - there are only so many countries and international organisations 
>> (in this sense) in the world, and those lists are pretty static.
>>
>> Enclosure won't work for missions to international organisations or the 
>> Vatican either. There are (IIRC) also arrangements between countries such 
>> that the embassy of A in country B also represents country C under certain 
>> circumstances. This also doesn't fit nicely with the "from"/"to" model. On 
>> wikipedia they are called "De facto embassies":
>>
>> https://en.wikipedia.org/wiki/De_facto_embassy
>>
>>
>> _______________________________________________
>> Tagging mailing list
>> [email protected]
>> https://lists.openstreetmap.org/listinfo/tagging
>
> _______________________________________________
> Tagging mailing list
> [email protected]
> https://lists.openstreetmap.org/listinfo/tagging

Attachment: smime.p7s
Description: S/MIME Cryptographic Signature

_______________________________________________
Tagging mailing list
[email protected]
https://lists.openstreetmap.org/listinfo/tagging

Reply via email to