foodon
foodon copied to clipboard
FoodOntology
Wine Appellation
Definition: A set of rules from a governmental agency or wine trade association to designate a defined and commercially protected geographic area and any applicable rules such as allowed varieties of grapes, maximum grape yields, alcohol level, presence of bubbles, vintage rules, etc., that are required to be compliant with the appellation and use the appellation name on a wine bottle label or published information.
Data/Object properties (to be refined and defined): Appellation name Governing Organization Appellation Code (AOC, AVA, DOC, etc) , Appellation Code Name (Appellation of Controlled Origin, American Viticultural Area, Denominazione di Origine Controllata, etc...) Geographic Area -- Village, City, Sub-Country (state/province), River, Valley, Country Facility -- Facility owned by Company, Facility at Geographic Area, Facility subclasses (Chateau, Estate, Vineyard, Winery, Cellar, etc.) Allowed varieties of grapes minimum level of alcohol maximum level of yields vineyard planting density minimum percent of grapes from the specified geographic area age of vines vintage rules bubble size wine style vinification techniques harvest techniques harvest fruit maturity wine classified status (Grand Cru, Premier Cru, Village, Petit, etc)
Really interesting challenge - I'm going to try an initial diagram now which can then be redone up to and into the wine hackathon (https://biohackathon-europe.org/projects.html) based on the above dimensions. You have exposed regulatory proscriptive components, phenotypes, contextual information ... each thing needs a model in its own right, as well as with respect to what we call "wine"!
So, just a first pass, with a number of ICE information content entities left undefined:
Starting to have a structure for the Wine Hackathon to really dig into and have fun! Breaking the paradigm of Wine -> Red Wine -> Pinot Noir Wine taxonomy. Too many white and rose Pinot Noir wines, and the existence of Blanc de Noirs Champagne - a white, sparkling wine made with Pinot Noir and Pinot Meunier, or all Pinot Noir.
So the wine hackathon starts tomorrow - sadly in CET timezone for north americans. I will report out on who is there in terms of focus - whether the hackathon focuses on characterizing organoleptic qualities of wine; or whether we also do more in oenology / vinification and into the upstream agricultural variables that drive organoleptic variety.
Very interested in learning what the “hackers” come up with!
Hope it is a good experience for all.
Diane
On Nov 7, 2021, at 5:45 PM, Damion Dooley @.***> wrote:
So the wine hackathon starts tomorrow - sadly in CET timezone for north americans. I will report out on who is there in terms of focus - whether the hackathon focuses on characterizing organoleptic qualities of wine; or whether we also end up developing the upstream agricultural and vinification variables that drive organoleptic variety.
— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub, or unsubscribe. Triage notifications on the go with GitHub Mobile for iOS or Android.
...and how's the hacking going?
On Mon, Nov 8, 2021 at 5:56 AM Diane Alexander @.***> wrote:
Very interested in learning what the “hackers” come up with!
Hope it is a good experience for all.
Diane
On Nov 7, 2021, at 5:45 PM, Damion Dooley @.***> wrote:
So the wine hackathon starts tomorrow - sadly in CET timezone for north americans. I will report out on who is there in terms of focus - whether the hackathon focuses on characterizing organoleptic qualities of wine; or whether we also end up developing the upstream agricultural and vinification variables that drive organoleptic variety.
— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub, or unsubscribe. Triage notifications on the go with GitHub Mobile for iOS or Android.
— You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub https://github.com/FoodOntology/foodon/issues/162#issuecomment-963173137, or unsubscribe https://github.com/notifications/unsubscribe-auth/AAMZGI4W6TF3GEXTRZP746TUK7JKJANCNFSM5GHHFHXQ .
Hey, its fun and a bit arduous at the same time since we don't have an integrated editor for ontologies that covers things like robot files and ontofox import files. So a bit of shuffling around. Main diagram work is happening at: https://drive.google.com/file/d/1-jHjnJ5njPggPh0MlhnrF51RZ9OFpYK2/view I'm translating everything that has new ID's into FoodOn by way of robot process table, or by Wine ontology table. The fermentation, and appellation section and "wine characteristics" phenotype sections (tabs in draw.io diagram above) are coming last because frankly they are the most complex, so slow pickings for progress, and require the most consultation which will have to extend well past end of this Hackathon tomorrow morning. I'm thinking that FoodOn will have to take on all the wine composition tasting phenotypes rather than PATO but I will check in with them about that. As well the main question is how far down into descriptive vocabulary words or phrases should we carry that section? Here are a number of diagrams, all open for criticism!!!!!
Basic wine product information:
🤓 😍 👏 🙌
On Thu, Nov 11, 2021 at 5:02 PM Damion Dooley @.***> wrote:
And FoodOn has been updated with many new wine-related terms!
— You are receiving this because you commented. Reply to this email directly, view it on GitHub https://github.com/FoodOntology/foodon/issues/162#issuecomment-966735036, or unsubscribe https://github.com/notifications/unsubscribe-auth/AAMZGI5WBOKY7OPNQY6TVVDULRRTPANCNFSM5GHHFHXQ .
New thoughts on the picture in [ddooley] commented [on Oct 18, 2021]:
Reverse the direction of the arrow from Wine Style to Wine Appellation Wine Style(s) is optionally prescribed by Wine Appellation
Objects related to Wine Appellation that are changed to optional Data Properties of Wine Appellation --- minimum percent alcohol --- minimum age of vines --- maximum level of grape berry yield --- bubble size (pertains to sparklers only) --?-investigate if a range for two data properties, minimum only? --- maximum vineyard planting density --- minimum percent of grapes from the specified geographic region --- maximum percent of wine that can come from a year that is not the listed vintage year
Object properties to Wine Appellation -- harvest technique -- harvest fruit maturity -- vinification technique
A few notes:
-
I didn't include cardinality in any of the relations but that is always an option. One can say for any diagrammed ----> relation that it is 0 or more, with the default semantic being 1 or more. One can even say 3 or more, or max 3, etc. but reasoners often can't handle testing truth with those attributes.
-
About "Wine Style to Wine Appellation" I think I see your point - that for a wine style there isn't always an appellation, but for an appellation there is always a wine style? In which case the relation should be reversed.
-
A core tenet of OBO Foundry ontology design is to minimize and generalize object relations - basically to the Relations Ontology set + additions as needed. And the second thrust is to have almost no data properties at all except for generic ones like "has quantity" and "has unit". James Overton is currently working on a finalized OBI/COB/OBO sanctioned treatment of data which is almost ready for testing. But basically instead of a particular data property relation we take the predicate and turn it into a type of datum, so "minimum age of vine at harvest" is a datum, a subclass of age datum, which is about some wine vintage. As a pattern this enables process modelling in a way that data properties do not. But I understand out in the RDF graph world people find it convenient to simply use equivalent data properties. So I would steer FoodOn to stick with the minimal object properties and almost no data properties approach, but I see it is important for us to show the equivalency, i.e. to show a mapping to the kinds of properties you mention for those who want the simplification. I can diagram a few examples if people want?
I see that the grey bubbles are for Information, that might be the equivalent to Data Properties, I think.
An Appellation does not always specify a particular Wine Style, but can have one or more Wine Style required in the Appellation Rule