BeerXML 3.0

[Oud Schoten]

http://www.spaarnebier.com/downloads/BeerXML3_preview.zip

Is there a word document from the 2.07 specification i can edit to make some changes to that document?

i made this come true

I'd like to suggest making the BeerXML <styles> tags a bit more like the BJCP for easier cross referencing.  I'd propose changing the BeerXML, since the BJCP format and breakdown of style info is so pervasive and often cited and used.   

Here's a comparison of the BJCP Styles and BeerXML breakdown of listing a style:

BJCP Styles	BeerXML Styles
category ----------- subcategory ----------- style name ----------- aroma appearance* flavor* mouthfeel* overall impression* comments ingredients - stats - og fg bitterness color abv ----------- examples	category category number* stylenumber styleguide* style name type* profile* ----------- ----------- ----------- ----------- notes ingredients - stats - og fg bitterness color abv carbonation* examples

* differences

Noted Differences:
The big difference is in how the BJCP styles breakdown what BeerXML calls "profile".

The category and subcategory info is dealt with slightly different, but this shouldn't be a big deal.

BeerXML's <styleguide> maps to the root of the BJCP XML document:  <bjcp_styleguide>

BeerXML's <type> is somewhat implemented in BJCP_XML, but at a higher level.  However, I'll be suggesting that it is used more explicitly in the BJCP XML.  Currently, it is used one up from the root of the document, eg.  <class type="beer">   ....I'm not sure that's the best usage, and curently, everything in the BJCP document is in class=beer, which is not even logically correct.

Carbonation is missing from the BJCP Styles XML, but unfortunately it is not part of the BJCP guidelines, so, that'll just have to be left as-is.


Proposed Change Summary
I propose that BeerXML map "profile" into the following elements so that it aligns better with the BJCP and is better suited for more extensive and organized profile descriptions. 
Break down BeerXML's <profile> into  ====>  <aroma>, <appearance>, <flavor>, <mouthfeel>, <overall_impression>

[jlochner]

I know the guys are busy working on other things so I am going to chime in here.

Regarding the BJCP style guidelines, although there is merit to bringing BeerXML in line with their schema, it may be a wild goose chase.  As the community at large we do not have much sway as how they present the schema.  They could change encodings, namespaces and the schema as a whole at will.

That being said, I do prefer the way they the BJCP guidelines are laid out.

I think it would benefit all to move this project to a more open forum to allow more direct contributors to the project, at this point it seems pretty dead here. To that end I have created a new repository on GitHub for tracking changes and allowing everyone to contribute to the project: https://github.com/brewpoo/BeerXML-Standard

I have not yet pushed the repo yet but will do so by the end of the weekend.

Thanks,
Jon (brewpoo)