<div dir="ltr"><div>On Wed, Oct 24, 2018 at 5:27 PM Allan Mustard <<a href="mailto:allan@mustard.net">allan@mustard.net</a>> wrote:</div><div><br></div><div class="gmail_quote"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div text="#000000" bgcolor="#FFFFFF">
<font face="Helvetica, Arial, sans-serif">I have no idea why amenity=embassy first came into
existence.</font></div></blockquote><div><br></div><div>The usual reasons. Somebody needed to tag an embassy, couldn't find a documented way of</div><div>doing it so used the first tag that came to mind.</div><div><br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div text="#000000" bgcolor="#FFFFFF"><font face="Helvetica, Arial, sans-serif">There is another proposal to create amenity=diplomatic
and then use the diplomatic=* tag to define more precisely what
type of facility an object is. I have added it to the proposal
wiki, but assume you would not like it, either.<br></font></div></blockquote><div><br></div><div>Not under amenity, no. Maybe it works for other people, but my mental map of what constitutes</div><div>an amenity doesn't include embassies and consulates. Even though embassies and consulates</div><div>both sometimes hold parties.<br></div><div text="#000000" bgcolor="#FFFFFF"><font face="Helvetica, Arial, sans-serif"><br></font><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><font face="Helvetica, Arial, sans-serif">
Paul, are you proposing office=diplomatic and diplomatic=[embassy,
mission, nunciature, consulate, consulate_general, consular agency,
honorary_consul], or something else?</font></blockquote><div><br></div><div>Something along those lines. I'm not sure office is a good fit either. We have amenity=doctors</div><div>and office=doctor but there are attempts to move those under healthcare, which I think is a better</div><div>way of handling them. I definitely don't like amenity here and office is only slightly better. A better</div><div>fit would be diplomatic_mission=consulate|embassy|nunciate|whatever but underscores in keys</div><div>seem to be out of favour. Is there another encompassing term?<br></div><div> <font face="Helvetica, Arial, sans-serif"></font><br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><font face="Helvetica, Arial, sans-serif">
As for objection to the service=* tag, would a new consular:*=*
tag be a better solution? Just asking. I'm not well versed in
programing editors. It would be something like
consular:immigrant_visas=yes, consular:nonimmigrant_visas=yes,
consular:citizen_services=yes, etc.</font></blockquote><div><br></div><div>Only if there is no need for an equivalent embassy: tag. That is everything that need be dealt with</div><div>for an embassy is listing which consular functions it also performs (if any). This assumes an</div><div>underlying model where an embassy can (but may not) do anything a consulate can but all</div><div>embassies have the same non-consular functions. Otherwise, if we had an all-encompassing</div><div>term like diplomatic_mission=* we could then have diplomatic_mission:citizen_services=yes. Or</div><div>something like that. I'm making this up as I go along. :)<br></div><font face="Helvetica, Arial, sans-serif">
<br></font><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><font face="Helvetica, Arial, sans-serif">
As for whether embassies serve "any purpose other than housing
spies," as a diplomat now for over 30 years, I can assure you that
at least in the case of U.S. embassies, we diplomats do a lot more
than that.</font></blockquote><div><br></div><div>That's how it worked until recent times. Now diplomacy-by-tweet seems to be the norm in the US. :(</div><div><br></div><div>However, your experience does mean you have a good idea of what the tagging scheme needs to</div><div>cover so it can be made coherent and possibly anticipate future needs. It's always a pain to introduce</div><div>a new way of doing things and then find out a year down the line that it can't handle something.</div><div><br></div><div>-- <br></div><div>Paul</div><div><br></div></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
</blockquote></div></div>