ddooley
commented
2 years ago A few brief comments, and promise to look more at this later in week. Basically there are a variety of modelling approaches one can take with classes and instances, object and data properties. I'm trying to massage the kind of RDF graph design notes you have above into an OBO Foundry design perspective below. I don't mean to convey OBO Foundry or the highway; just that FoodOn tries to take on the foundry principles to encourage data harmonization within that paradigm. The upcoming Wine ontology workshop may reveal other desired features that sit outside OBO design principles.
In FoodOn an instant of a beverage like wine is an actual sample of it that can be tested. A class of a beverage is a category - with various criteria for recognizing whether an instance belongs to it.
I think "grape wine" class members have each undergone a fermentation process, yielding alcohol (ethanol) content. We can also have a "de-alcoholized grape wine" class that is the output of a de-alcoholization process applied to "grape wine". This illustrates the use of process ontology terms to tie concepts together.
About: "Instances are each commercially offered named wine designated by year." - we'd say a "commercially offered named wine" is a class. It may be that [named wine] x year is also a subclass - the idea being that a glass from that year should taste like any other from same year. But if push comes to shove, and this isn't true, then we might just choose to have instances of a named wine described by year, batch, etc.
About wine regions: It looks like Wikidata is starting to build a list of them: https://www.wikidata.org/wiki/Q2140699 . OBO Foundry proponents are starting to turn to Wikidata for geography references. (Geonames is also popular but I don't think they'd cover this kind of thing). It looks like this resource would need to be expanded incrementally, as needed, and seeded with some popular french/italian etc regions? What would be desirable certainly is to use Wikidata for country and city references.
About data properties: Every data property is essentially semantically opaque, so OBO Foundry generally shies away from them. If I said "x123 'спирт по объему' 14%" a computer would have no idea of what I was talking about. Its ok as a shorthand as long as there is a long-hand more detailed version to convert to that starts to provide meaning. In this case we're talking about volumes of a substance within another substance. PATO offers an informatic approach with its "concentration of" quality, which can be seen at work in CDNO where we could add a concentration of alcohol in a substance as a quality class: https://www.ebi.ac.uk/ols/ontologies/cdno/terms?iri=http%3A%2F%2Fpurl.obolibrary.org%2Fobo%2FPATO_0000033&viewMode=All&siblings=false (click on + sign by "concentration of"). We create an instance representing concentration of alcohol in the wine, and then say that instance "is about" some wine beverage instance " Or this happens at the class level if some producer is promising some % for its product line.
FoodOn would just say an entity (instance or class) has a label (rdfs:label) annotation , rather than introducing a "grape wine name". This avoids data property explosion for each kind of thing name out there.
FoodOn has product labelling entities (http://purl.obolibrary.org/obo/FOODON_03510023) which sulfite content could fit into. You raise a good point that a bit more of a model is necessary for capturing legislative requirements around that though!
About object properties, we generally try to reuse RO obo relation ontology relations. However, RO doesn't have much in the way of "country of origin", "originates from" etc. so we probably need to add one or two there. It has "located in" which might do.
DianeKEPR
Proposed definition: Grape wine is a beverage made from fermented grapes that typically contains alcohol.
Reference https://en.wikipedia.org/wiki/Wine in wikipedia for Wine states: Wine is an alcoholic drink typically made from fermented grapes. This wiki reference also has content on wines made with other sources (rice, honey, etc). Propose leaving room in the definition to include the small presence of instances of grape wine that are considered de-alcoholized (legally non-alcoholic), but are made from fermented grapes with the alcohol removed from a secondary process, and has most of the characteristics of wine that retains the alcohol.
Propose an assumption that grape wine is the bottom level subclass, and this is where instances of grape wine would exist, if sample instances are added to the ontology. Sample instances can be used to test this assumption, even if the instance data not loaded to the ontology. Instances are each commercially offered named wine designated by year.
Proposed below are some object properties and data properties of grape wine from a quick brainstorm, not in syntax, references other not yet modeled classes, and are not in proper syntax. Provided for discussion and further refinement.
Object properties: must have one or more Wine Style Geography (not aware of an external source for geography that includes Wine Region) -- must have Country -- may have sub-country -- may have City -- may have Wine Region may have one or more Wine Variety (technically cultivar) -- this information not always disclosed -------a varietal wine has a single wine variety and can be classified by the name of the variety -- need to determine how to model the varietal wine name ----------- a classified variety name like Pinot Noir, Cabernet Sauvignon might assume the Red wine style (Pinot Noir is Red, Rose or White wine) ----------- a Chardonnay is a white wine has Packaging Type (bottle, box, can) may have Appellation(and similar) given by a recognized Organization that controls these designations roles by Company -- Bottler -- Producer -- Importer -- Vineyard
Data properties: grape wine name (could have multiple parts to the name) year produced (does scope need to designate which are vintage years?) alcohol by volume net volume may have sulfite warning (yes/no) (over a specified percent of SO2 and whether required to disclose varies by country) web site address