emmo-repo / domain-photovoltaics Goto Github PK

Please modify this issues for questions:

• What is the difference between photovoltaics.ttl and domain-photovoltaics.ttl? Response: domain-photovoltaics is a wrapper that includes all of the imported supporting domains. domain-photovoltaics should not contain any definitions itself it just collects definitions that are made in photovoltaics, etc.
• What is with boolean quantities? E.g. object is flexible, true/false. Where to put them? Response: If you want to describe an object that is boolean, there is the Boolean class. Just use the search bar in the top right of Protege and you should find it.
• Difference between quantity and quantitative Property? Where to put quantitative object attributes? Measured quantities? How to reference that classes have property such as thickness or area? Response: A Quantity expresses the value of a QuantitativeProperty. EMMO draws a distinction between quantities that are actually measured (e.g. a QuantitativeProperty) and quantities that are known from some other source like a specification sheet (a ConventionalQuantitativeProperty).
• How to store type, like float, integer, string? How to deal with units? E.g. why does length not have a reference to SI unit meter?
• How to reference composition? E.g. elements a layer is made of. Response: Probably best to use the Holistic Perspective, like hasHolisticPart
• A substrate has many cells. So this is a one to many relation. Is there a way to add an attribute to substrate which capture the number of cells it has or this is done by substrate hasCells some cells? Response: Using "some" indicates that there is at least one, but does not put limits on how many. You can use other modifiers like "exactly X" or "min Y" (where X and Y are integers) if you want to place additional constraints.
• Difference between skos:preflabel and rdfs:label? Response: rdfs and skos refer to different vocabularies from the W3C for describing information on the web. In this case skos:prefLabel and skos:altLabel are subclasses of rdfs:Label. Every entry has to have exactly one skos:prefLabel and can have as many skos:altLabel definitions as needed.
• Is there a possibility to check who added/changed something? Response: I suppose checking the git history would be the best way for that.
• How to deal with ranges, e.g. a quantative property has a min and a max value.
• A cell has two types of area, the total area and the effective area. Does it make sense to create classes CellAreaTotal and CellAreaMeasured? Or is it better to reference the existing area as hasQuantatiyValue exactly 1 Area and hasMeasuredQuantatiy exactly 1 Area?
• How to use data and object property? Should data property be used? Response: Object properties relate objects to each other. Data properties relate objects to some pieces of data.
• Where do we put processes, under holistic or persistence? I saw that for the battery ontology it is in both? Are synthesis processes intentitonal processes? Response: things can be included under multiple perspectives, based on their needs. I'd put a Synthesis under a Manufacturing
• Some classes have three white lines in their orange dot. What do they mean? E.g. ManufacturedActiveMaterial.
• LithiumCoboltOxideMolecule has circular reference?
• SubClass Of vs Equivalent To?
• Git merge procedure? Merging produces lots of errors when working in parallel, is there a better way?
• Is it possible to have a file which automatically loads the right ontologies without need of git or download manually? Always click the same file and get the newest update. Response: Yes
• (What is with descriptive quantities? What is with some to some relation? E.g. Cell architecture, each cell has an architecture.)

The README should be extended with purpose, goals, authors, acknowledgements, and other information.

Hey Casper,

I talked to Simon about this and he said I can ask you. Is it possible to have a .ttl file which loads the current version of the ontology from the github development branch.

The reason is that then by just opening this file people can browse the ontology without the need of downloading/pulling the recent updates.

Best Micha

Might exist in Battery Ontology

These items should be done before the repository is considered to be completely setup:

• Setup Deploy Onto! (onto-ns.com)
• Setup a "collective" ontology file (domain_photovoltaics.ttl or similar)
• Add meaningful catalog file for proper referencing (and importing) EMMO
• Add documentation setup, including continuous integration and deployment (CI/CD)