<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
</head>
<body text="#000000" bgcolor="#FFFFFF">
<div class="moz-cite-prefix">On 08/03/19 00:07, seirra blake wrote:<br>
</div>
<blockquote type="cite"
cite="mid:c99b5685-4fe8-b383-5b27-a7e773336329@yandex.com">
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
<p>while I can't see a problem with a tag for each pet, it may
still make more sense to have a pets tag and just namespace
species/related things under it similar to the access tag. use
cases I can think of:</p>
<ul>
<li>pets=no | no matter what, no pets</li>
<li>pets=yes | open to all or at least most pets other than
specified examples such as...</li>
<li>pets:dogs=no | dogs that are pets are not allowed, a guide
dog does not necessarily count as a pet or at least, I don't
think of one as being a pet.</li>
<li>pets:cats=1 | only one cat allowed</li>
</ul>
</blockquote>
<br>
Presently they are tagged as per access tagging.<br>
motor_vehicle=yes/no<br>
horse=yes/no<br>
dog=yes/no<br>
ferret=yes/no <br>
parrot=yes/no<br>
etc<br>
<br>
<blockquote type="cite"
cite="mid:c99b5685-4fe8-b383-5b27-a7e773336329@yandex.com">
<ul>
</ul>
<p>this does still make it vague in the sense that if only one cat
is allowed, is it per party or per person, but this probably
could be made more specific with another tag namespaced under
pets (my mind is blank, I haven't eaten yet. however this feels
like the best approach to cover most situations). this may also
be useful for things like water-bowls/treats for pets as
mentioned elsewhere here; for example: my bank offers dog
biscuits for dogs, the train station used to offer a water-bowl
as well, but I haven't put much thought into seeing if it's
there after the take over by LNER.<br>
</p>
</blockquote>
<br>
Where a quantity limit applies ? dog:1= yes @ per party ??? <br>
<br>
</body>
</html>