3,543
edits
Alcohol/Beers/Best practices: Difference between revisions
Alcohol/Beers/Best practices (view source)
Revision as of 11:53, 5 September 2015
, 5 September 2015Suggestion for brewery address markup
(Added fl oz) |
(Suggestion for brewery address markup) |
||
| Line 79: | Line 79: | ||
== Manufacturing or processing places == | == Manufacturing or processing places == | ||
This would be the address of the brewery. | This would be the address of the brewery. There is some confusing how this should be entered. | ||
<br /> | |||
# Separate - as "Brewery", "Streetname + number", "Postal code", "City", "Region", "Country". This would allow to find all beers brewed in a country, or region, or city, or postal code, or street, or brewery. | |||
# Single - as "Brewery, Streetname + number, Postal code, City, Region, Country". Single query possible. Easy to reuse? | |||
# Tagged - as "Brewery=Breweryname", "addr:street=Streetname", "addr:housenumber=housenumber", "addr:street=postcode", "addr:city=city", "addr:province=Region", "addr:country=Country" following the Open Street Map mark up for [http://wiki.openstreetmap.org/wiki/Key:addr address]. Unfortunately this is not very readable for the end-user; | |||
As this is a keybased field, entering an address as separate items is preferred. One should always follow the same order for easy readability by the end-user. | |||
== EMB code == | == EMB code == | ||
Only enter the EMB-code, such as EMB 29293G for {{product| 3760010140017}}; | Only enter the EMB-code, such as EMB 29293G for {{product| 3760010140017}}; | ||