[Tagging] Open of discussion on "operational_status" (part of life cycle with disused/abandoned/demolished)

[fly]

Am 29.06.2013 19:54, schrieb Bryce Nesbitt:
> On Sat, Jun 29, 2013 at 5:07 AM, fly <lowflight66 at googlemail.com
> <mailto:lowflight66 at googlemail.com>> wrote:
> 
>     Exactly, what you do describe won't work. Please use a prefix if
>     something is broken. Software which wants to display these kind of
>     broken objects can look for this prefix and all other simply ignore it.
> 
> 
> This tag is for the opposite use case.
> This tag is for objects which are intended to remain mapped.
> Examples:
> 
>   * Hospital, windows blown out due to hurricane, observed to be closed
>     1 day later.
>   * Drinking fountain, drain clogged with sand (needs repair, but still
>     works.)
>   * Gate, observed to be sticky (but you can walk around it 100 feet north).
> 
> A specific use case is in drinking fountains where certain rendering
> software processes additional tags to alert operating agencies about a
> problem, but all other rendering agents continue to function normally.
>  Most maps just show the drinking fountain.  The enhanced maps show the
> last reported status of the drinking fountain (working, needs repair and
> why, broken and why).

I understood your intension.
Sorry, but operational_status=closed is used in your example and this
does not fit at all.

It works as long as the primary function is available though somehow broken

> The disused: namespace prefix is fine for a different use case... if you
> want the object to be invisible to most processing agents.

Yes, like operational_status=closed for a toilet which is broken and
closed, but not like a burned down toilet where you can not tell if it
had been a toilet and also wether it will ever open again.