emmo-repo / emmo Goto Github PK
View Code? Open in Web Editor NEWElementary Multiperspective Material Ontology (EMMO)
License: Other
Elementary Multiperspective Material Ontology (EMMO)
License: Other
From running OntOlogy Pitfall skanner! (OOPS!) on http://oops.linkeddata.es/
Results for P13: Inverse relationships not explicitly declared.17 cases | Minor
This pitfall appears when any relationship (except for those that are defined as symmetric properties using owl:SymmetricProperty) does not have an inverse relationship (owl:inverseOf) defined within the ontology.
• OOPS! has the following suggestions for the relationships without inverse:
› http://emmo.info/perspectives/emmo-existent.owl#EMMO_b2282816_b7a3_44c6_b2cb_3feff1ceb7fe could be inverse of http://emmo.info/perspectives/emmo-existent.owl#EMMO_a50d920d_1ee3_4668_9a73_5d80a1c6fe15
› http://emmo.info/base/emmo-mereotopology.owl#EMMO_7afbed84_7593_4a23_bd88_9d9c6b04e8f6 could be inverse of http://emmo.info/base/emmo-4d.owl#EMMO_f68030be_94b8_4c61_a161_886468558054
› http://emmo.info/base/emmo-4d.owl#EMMO_f68030be_94b8_4c61_a161_886468558054 could be inverse of http://emmo.info/base/emmo-4d.owl#EMMO_6e046dd0_9634_4013_b2b1_9cc468087c83
• Sorry, OOPS! has no suggestions for the following relationships without inverse:
› http://emmo.info/perspectives/emmo-existent.owl#EMMO_65a2c5b8_e4d8_4a51_b2f8_e55effc0547d
› http://emmo.info/perspectives/emmo-semiotics.owl#EMMO_eb3518bf_f799_4f9e_8c3e_ce59af11453b
› http://emmo.info/perspectives/emmo-semiotics.owl#EMMO_60577dea_9019_4537_ac41_80b0fb563d41
› http://emmo.info/perspectives/emmo-semiotics.owl#EMMO_39c3815d_8cae_4c8f_b2ff_eeba24bec455
› http://emmo.info/perspectives/emmo-semiotics.owl#EMMO_297999d6_c9e4_4262_9536_bd524d1c6e21
› http://emmo.info/perspectives/emmo-semiotics.owl#EMMO_2337e25c_3c60_43fc_a8f9_b11a3f974291
› http://emmo.info/base/emmo-mereotopology.owl#EMMO_03212fd7_abfd_4828_9c8e_62c293052d4b
› http://emmo.info/base/emmo-mereotopology.owl#EMMO_9380ab64_0363_4804_b13f_3a8a94119a76
› http://emmo.info/base/emmo-mereotopology.owl#EMMO_8c898653_1118_4682_9bbf_6cc334d16a99
› http://emmo.info/base/emmo-mereotopology.owl#EMMO_6b7276a4_4b9d_440a_b577_0277539c0fc4
› http://emmo.info/base/emmo-mereotopology.owl#EMMO_ec2472ae_cf4a_46a5_8555_1556f5a6c3c5
We need a semantic way to describe chemical compositions and other physical quantities that are specific to a constituent (atom or molecule).
This is a long-needed feature that has been discussed a lot, but never went into EMMO.
This issue is different from issue #99, since chemical compositions are unordered.
Turtle is a more readable and git-friendly file format than the current rdf/xml.
The idea is therefore to change the file format of the development version of EMMO from current rdf/xml to turtle. However, since rdf/xml is subborted by more tools we must at the same time set up automatic tools that converts both the asserted and inferred ontology to rdf/xml and publish them on GitHub Pages. New columns for rdf/xml and turtle (and maybe other formats) should be added to the table on https://emmo-repo.github.io/.
This requires issue #121 to be implemented first.
The documentation of all top and middle EMMO modules are currently the same as http:emmo-repo.info/emmo. But it would make sense to replace dcterms:abstract with a description of the different modules.
dcterms:title should maybe also be updated.
The branch emmo-units adds base units to emmo. It adds domains/emmo-units.owl which includes:
Dear @emanueleghedini , @jesper-friis ,
I hope you are doing well.
While using the emmo-inferred.owl file I notice some a minor inconsistency I guess. For instance the second line of the following excerpt of code is xml:lang="unibo.it"
instead of xml:lang="en"
. Please let me know what you think.
Version 1.0.0-alpha2</owl:versionInfo>
<rdfs:comment xml:lang="unibo.it">Contacts:
Gerhard Goldbeck
Goldbeck Consulting Ltd (UK)
email: [email protected]
Many thanks!
Kind Regards,
Joana
From running OntOlogy Pitfall skanner! (OOPS!) on http://oops.linkeddata.es/
Results for P36: URI contains file extension.ontology* | Minor
This pitfall occurs if file extensions such as ".owl", ".rdf", ".ttl", ".n3" and ".rdfxml" are included in an ontology URI. This pitfall is related with the recommendations provided in [9].
*This pitfall applies to the ontology in general instead of specific elements.
[9] Archer, P., Goedertier, S., and Loutas, N. (2012). D7. 1.3-study on persistent URIs, with identification of best practices and recommendations on the topic for the Mss and the EC. PwC EU Services.
Currently EMMO refers to other resources and ontologies using subproperties of rdfs:seeAlso. I think replacing these with subproperties of skos:exactMatch and skos:closeMatch would improve interoperability.
currently a physics quantity has a number and unit, however, this may mean (if we ugnore transitivness) that emmo only supports scalar quanititeis like mass or Temperature, not e.g., force or velocity etc which are vector quantities or tensor quanitities that descrive how a physics quantitiy is represented int time-space.
NOTE this is not about the data type which should not be part of EMMO it self, but the implementations, this is about the representation of physics quantities that are not simple numbers (the data type may refer for example to double or float, in emmo it is simply a read number).
From running OntOlogy Pitfall skanner! (OOPS!) on http://oops.linkeddata.es/
Results for P41: No license declared.ontology* | Important Important
The ontology metadata omits information about the license that applies to the ontology.
*This pitfall applies to the ontology in general instead of specific elements.
The inferred ontology produced with FaCT++ includes some redundant isA (isSubclassOf) relations that would be nice to get rid of.
Examples of such redundant relations:
Matter isA Physical (redundant because Matter isA Physicalistic isA Perspective isA Physical)
Field isA Physical (redundant because Field isA Physicalistic isA Perspective isA Physical)
Process isA Physical (redundant because Process isA Holistic isA Perspective isA Physical)
Participant isA Physical (redundant because Participant isA Holistic isA Perspective isA Physical)
Since the reasoner does not add all isA
relations to all possible ancestors, tools using the ontology must anyway check the list of ancestors. To avoid double-counting because of these redudant isA relations, the tools must add additional tests complicating their implementation.
This would require that we add an additional tool.
From running OntOlogy Pitfall skanner! (OOPS!) on http://oops.linkeddata.es/
Results for P24: Using recursive definitions.5 cases | Important
An ontology element (a class, an object property or a datatype property) is used in its own definition. Some examples of this would be: (a) the definition of a class as the enumeration of several classes including itself; (b) the appearance of a class within its owl:equivalentClass or rdfs:subClassOf axioms; (c) the appearance of an object property in its rdfs:domain or range rdfs:range definitions; or (d) the appearance of a datatype property in its rdfs:domain definition.
• This pitfall appears in the following elements:
› http://emmo.info/base/emmo-physical.owl#EMMO_0f795e3e_c602_4577_9a43_d5a231aa1360
› http://emmo.info/base/emmo-physical.owl#EMMO_29072ec4_ffcb_42fb_bdc7_26f05a2e9873
› http://emmo.info/base/emmo-physical.owl#EMMO_c5ddfdba_c074_4aa4_ad6b_1ac4942d300d
› http://emmo.info/domains/emmo-material.owl#EMMO_70dac51e_bddd_48c2_8a98_7d8395e91fc2
› http://emmo.info/domains/emmo-material.owl#EMMO_5b2222df_4da6_442f_8244_96e9e45887d1
The corresponding labels are:
If we add the following redirections to http://emmo.info
http://emmo.info/emmo/emmo-inferred.owl -> https://emmo-repo.github.io/versions/latest/emmo-inferred.owl
http://emmo.info/emmo/<VERSION>/emmo-inferred.owl -> https://emmo-repo.github.io/versions/<VERSION>/emmo-inferred.owl
we can delete emmo-inferred.owl from the repository. That will prevent growing the EMMO repository unnessesary much, making slow and large to clone.
EMMO defines a set of annotations under the annotations namespace. For increased interoperability with standard tooling, it would be better to use standards like Dublin Core and SKOS as follows:
dcterms:contributor
insteaddcterms:license
insteadskos:definition
insteadskos:example
insteadrdfs:comment
, but I think it is more consistent to change it to a subproperty of skos:note
(which itself is a subproperty of rdfs:comment
).skos:altLabel
insteadskos:prefLabel
instead. This is according to best practices. It is already included in the SKOS standard that an entity should only have one skos:prefLabel
.For annotating the ontology itself, dcterms provides some additional useful properties like dcterms:title
, dcterms:abstract
, dcterms:date
, ...
This enhancement will also fix issue #23.
SKOS also defines skos:Collection
and skos:OrderedCollection
which might useful when defining compositions and arrays, respectively, in EMMO.
This enhancement require that we add the following namespaces to all owl files:
xmlns:dcterms="http://purl.org/dc/terms/"
xmlns:skos="http://www.w3.org/2004/02/skos/core#"
the catalogue file under domains in the emmo-units branch (see #15 ) contains some wrong references:
<uri id="Automatically generated entry, Timestamp=1577294513690" name="http://emmo.info/domains/emmo-si-units.owl" uri="emmo-si-units.owl"/>
--> there is no emmo-si-units under domains.
also need to replace local references as in:
<uri id="Imports Wizard Entry" name="http://emmo.info/emmo.owl" uri="file:/home/jesperf/prosjekter/EMMC/emmo/emmo.owl"/>
While EMMO has had developed physical quantities quite far, the description of models is lacking behind.
Currently the EMMO domain ontologies hosted on github are prefixed with "domain-". Is this really nessesary?
Discuss and document what we agree on in the governance document.
This allows introducing ordering and is very important for concepts like 'string', 'serialisation', ordering of dimensions, etc
This is an essential and long-needed feature for providing a semantic description of dimensional properties.
A more general implementation of ordering would be LISP-like (head rest) tuples or "compartments". The 'head' of a compartment would be a reference the class or individual that should be ordered, while the 'rest' or a compartment would be a reference to another compartment or owl:Nothing.
In current EMMO a property appears both under (subclass of) symbol and sign. Property under sign makes sense in a semiotic way, i.e., it is related to something that in fact is related to an object (which is related to a physical). "Property " under symbol is an arbitrary graphical (think of a blob of ink or the alphabet on your keyboard). The graphical is not necessary a sign, and hence not a property always.
** solution proposed by @emanueleghedini (please correct if wrong of course). **
remove property under graphical and define instead a "property_representation" or "property_symbol" that stands for a property (sign) in a mathematical model.
property under sign should be one that can be represented by mathematical symbols that stand for property (the property_symbols..)
currently IRIs are complex, e.g., http://emmo.info/latest/domains/emmo-material.owl#EMMO_a2b006f2_bbfd_4dba_bcaa_3fca20cd6be1
for a machine it does not matter if its like that or something like http://emmo.info/latest/domains/emmo-material.owl#EMMO_UNIT_MASS
the latter is much simpler. Are there any advantages for UUID like IRI#s?
Example:
http://emmo.info/emmo/1.0.0-beta/top is supposed to be redirected to https://github.com/emmo-repo/EMMO/raw/1.0.0-beta/top/top.owl but unfortunately it is redirected to https://github.com/emmo-repo/EMMO/raw/1.0.0-beta/emmo.owl which is the top-level EMMO itself.
The same is the case for all other modules.
A few missing restrictions:
Measurement hasParticipant some QuantitativeProperty
, which is a refinement of the observation having a property as a participant.Hi, I have a question concerning issue #85 .
in 1.0.0-alpha2, hasSymbolData
has domain Symbol and is functional. That still means that every Symbol, including math.Integer or math.Real must have that relationship, right?
<owl:DatatypeProperty rdf:about="http://emmo.info/emmo/middle/perceptual#EMMO_23b579e1_8088_45b5_9975_064014026c42">
<rdf:type rdf:resource="http://www.w3.org/2002/07/owl#FunctionalProperty"/> # it is functional
<rdfs:domain rdf:resource="http://emmo.info/emmo/middle/perceptual#EMMO_a1083d0a_c1fb_471f_8e20_a98f881ad527"/> # domain is symbol
<rdfs:range rdf:resource="http://www.w3.org/2001/XMLSchema#string"/>
<skos:prefLabel xml:lang="en">hasSymbolData</skos:prefLabel>
</owl:DatatypeProperty>
From running OntOlogy Pitfall skanner! (OOPS!) on http://oops.linkeddata.es/
Results for P04: Creating unconnected ontology elements.7 cases | Minor
Ontology elements (classes, object properties and datatype properties) are created isolated, with no relation to the rest of the ontology.
• This pitfall appears in the following elements:
› http://emmo.info/domains/emmo-material.owl#EMMO_7db59e56_f68b_48b7_ae99_891c35ae5c3b
› http://emmo.info/domains/emmo-material.owl#EMMO_eb3c61f0_3983_4346_a0c6_e7f6b90a67a8
› http://emmo.info/domains/emmo-material.owl#EMMO_4588526f_8553_4f4d_aa73_a483e88d599b
› http://emmo.info/domains/emmo-properties.owl#EMMO_2a888cdf_ec4a_4ec5_af1c_0343372fc978
› http://emmo.info/domains/emmo-material.owl#EMMO_25f8b804_9a0b_4387_a3e7_b35bce5365ee
› http://emmo.info/domains/emmo-properties.owl#EMMO_251cfb4f_5c75_4778_91ed_6c8395212fd8
› http://emmo.info/domains/emmo-material.owl#EMMO_db03061b_db31_4132_a47a_6a634846578b
From running OntOlogy Pitfall skanner! (OOPS!) on http://oops.linkeddata.es/
Results for P32: Several classes with the same label.3 cases | Minor
Two or more classes have the same content for natural language annotations for naming, for example the rdfs:label annotation. This pitfall might involve lack of accuracy when defining terms.
• The following classes contains the same label, maybe they should be replaced by one class with several labels or might be equivalent classes:
› http://emmo.info/domains/emmo-geometry.owl#EMMO_0c576e13_4ee7_4f3d_bfe9_1614243df018, http://emmo.info/domains/emmo-geometry.owl#EMMO_9268958f_7f54_48ab_a693_febe2645892b, http://emmo.info/domains/emmo-geometry.owl#EMMO_0ab0485c_9e5b_4257_a679_90a2dfba5c7c (1-manifold, 2-manifold)
› http://emmo.info/domains/emmo-geometry.owl#EMMO_0c576e13_4ee7_4f3d_bfe9_1614243df018, http://emmo.info/domains/emmo-geometry.owl#EMMO_0ab0485c_9e5b_4257_a679_90a2dfba5c7c (1-manifold, 0-manifold)
› http://emmo.info/domains/emmo-geometry.owl#EMMO_0c576e13_4ee7_4f3d_bfe9_1614243df018, http://emmo.info/domains/emmo-geometry.owl#EMMO_9268958f_7f54_48ab_a693_febe2645892b, http://emmo.info/domains/emmo-geometry.owl#EMMO_46f0f8df_4dc6_418f_8036_10427a3a288e, http://emmo.info/domains/emmo-geometry.owl#EMMO_0ab0485c_9e5b_4257_a679_90a2dfba5c7c (1-manifold, 2-manifold, 3-manifold, 0-manifold)
The IRI of Newton and Farad contains the version 1.0.0-alpha or 1.0.0-alpha2. This must be a mistake.
in many cases in physics and materials science we need to relate a quantity to multiple "keys". Having a data structure supported for this in the ontology like in #27 may lead to overuse and to "injection" of EAV data paradigms with lower semantic power than is presented in EMMO.
here another solution is proposed that alleviates the need for arbitrary keys in data structures. As an example we consider the chemical composition: "$Al 40 %, O 60 %" of some crystal.
here obviously one needs to specify an element, and a corresponding physical quantity (the mass %). instead of defining a map with arbitrary strings, like "Al" --> value "40 %" we can and "O" --> "60 %", we can define that
chemical composition is a physical quantity that has in addition to number and unit an IUPAC chemical element (or molecule).
then the chemical composition of an alloy can simply have properties of all chemical composition instances, without the need for explicit keys.
From running OntOlogy Pitfall skanner! (OOPS!) on http://oops.linkeddata.es/
Results for P30: Equivalent classes not explicitly declared.4 cases | Important
This pitfall consists in missing the definition of equivalent classes (owl:equivalentClass) in case of duplicated concepts. When an ontology reuses terms from other ontologies, classes that have the same meaning should be defined as equivalent in order to benefit the interoperability between both ontologies.
• The following classes might be equivalent:
› http://emmo.info/domains/emmo-geometry.owl#EMMO_d7bf784a_db94_4dd9_861c_54f262846fbf, http://emmo.info/domains/emmo-material.owl#EMMO_70dac51e_bddd_48c2_8a98_7d8395e91fc2 (sphere, field)
› http://emmo.info/domains/emmo-geometry.owl#EMMO_39362460_2a97_4367_8f93_0418c2ac9a08, http://emmo.info/base/emmo-mereotopology.owl#EMMO_eb3a768e_d53e_4be9_a23b_0714833c36de (point, item)
› http://emmo.info/domains/emmo-material.owl#EMMO_3397f270_dfc1_4500_8f6f_4d0d85ac5f71, http://emmo.info/domains/emmo-material.owl#EMMO_eb77076b_a104_42ac_a065_798b2d2809ad (molecule, atom)
› http://emmo.info/base/emmo-physical.owl#EMMO_29072ec4_ffcb_42fb_bdc7_26f05a2e9873, http://emmo.info/domains/emmo-material.owl#EMMO_3c218fbe_60c9_4597_8bcf_41eb1773af1f (void, vacuum)
In technological applications many actions are intentional. We need to cover it in EMMO.
A proposal to add a "triangle with a central element" similar to Semiotic Triangle is suggested:
nodes:
the center of the triangle has the agent.
All the above is contained in an intentional process, like the sign, object etc are contained in the semiotic process.
The semiotic process can also have its on "intentional triangle" to describe how the measurement is done for example, and by whom etc.
Dear EMMO developers,
I have been recently looking into EMMO an it’s seems to be a great ontology in the materials domain.
It is very well documented (e.g. training), however, I am missing an examples section where hands-on examples are presented. Maybe I just did not find them?
From other well known ontologies, e.g. SOSA https://www.w3.org/TR/vocab-ssn/#examples, these kind of examples are provided, which are very helpful to figure out the usage.
For instance it would be interesting to represent the following data:
Material: 55NiCrMoV6
CHEMICAL COMPOSITION (WEIGHT %)
C (%): 0.50 ~ 0.60
Si(%): 0.10 ~ 0.40
Mn(%): 0.65 ~ 0.95
P(%)≤: 0.030
S(%)≤: 0.030
Cr(%): 0.60 ~ 0.80
Mo(%): 0.25 ~ 0.35
V(%): 0.07 ~ 0.12
Other(%): Ni 1.50 ~ 1.80
MECHANICAL PROPERTIES - HOT WORKING, HEAT TREATMENT AND HARDNESS
Hot working tenperature /℃: 1050~850
Annealing temperature /℃: 650-710
Hardness after annealing ≤HBW: 240
Quenching temperature /℃: 830 - 870
Best
Georg
Please indicate how to create inferences with this ontology. Thanks,
Can we please add the VIMMP, MarketPlace and OntoTrans projects to the acknowledgements. GCL used resources from these projects to contribute. Should be done for alpha-2
This work is conducted under the framework of the VIMMP project (2018-2021), that receives funding from the European Union’s Horizon 2020 Research and Innovation Programme, under Grant Agreement n. 760907
This work is conducted under the framework of the MarketPlace project (2018-2022), that receives funding from the European Union’s Horizon 2020 Research and Innovation Programme, under Grant Agreement n. 760173
This work is conducted under the framework of the OntoTrans project (2020-2024), that receives funding from the European Union’s Horizon 2020 Research and Innovation Programme, under Grant Agreement n. 862136
In the Middle Level description text there are four paragraphs entitled: Reductionistic, Holistic, Phenomenic and Physics while in the picture and in the owl file names are slightly different, this might be confusing.
Hello,
I get the following error, when parsing EMMO using rdflib:
File "/home/urba/miniconda3/envs/osp/lib/python3.8/site-packages/rdflib/term.py", line 566, in __new__
raise Exception("'%s' is not a valid language tag!"%lang)
Exception: 'unibo.it' is not a valid language tag!
I guess this is the reason:
<rdfs:comment xml:lang="unibo.it">Contacts:
Gerhard Goldbeck
Goldbeck Consulting Ltd (UK)
email: [email protected]
Emanuele Ghedini
University of Bologna (IT)
email: emanuele.ghedini</rdfs:comment>
AllegroGraph was not able to import EMMO because siunits.owl use xsd:decimal, which does not support scientific notation.
Changed xsd:decimal to xsd:float in the file and imported the ontology successfully into the triplestore.
See https://github.com/quaat/EMMO/blob/master/middle/siunits.owl
This is a first draft for adding datatypes to EMMO. Datatypes (here called Value) are essential for using EMMO in actual applications.
Would it be better to rename "Value" to "Datatype"? I have been using Value here, since it feels more natural to say that a property has part Value than DataType.
The SumType is an interesting suggestion by Petter that needs to be discussed to get right. It will allow an EMMO-based application ontology to specify that e.g. salt concentration may be represented with either a single average value, a statistical distribution or spatially resolved grid.
Edit: Updated CompoundItem
.
Value
Number
Boolean
CompoundItem
A CompoundItem has two spatial parts, 'item' and 'value'. It makes a
connection between an already defined concept (an EMMO Item) and a corresponding value.
Dimension
Dimensions are used to construct arrays. They have a size and may be chained using hasNextDimension to provide an ordered list of dimensions. It would also be very useful to assign a name to each dimension or a quantity. Should we use value restrictions for that?
hasValue
hasKey
hasDimension
Cardinality may be used to specify exact, max or min size of a dimension.
Otherwise the dimension size must be assigned at instantiation.
hasNextDimension
The ontology URL (http://emmo.info/emmo.owl) (see README.md) is broken: HTTP 404 (Not Found).
I agree we need to standardise on SI units, however, we not make it more explicit and open and consistent as follows:
In this way we eliminate the clutter in the actual quantities having to add possible units in the class definition. For example:
for Area, we simply put
hasUnit Some AreaUnit,
isn't this much more elegant?
@emanueleghedini @jesper-friis your comments please?
thanks.
Make a new repository with tools for publishing
for each release.
This should be easy to use on both github and gitlab supporting GitHub Pages, GitLab Pages, +++ as targets.
From running OntOlogy Pitfall skanner! (OOPS!) on http://oops.linkeddata.es/
Results for P08: Missing annotations.87 cases | Minor
This pitfall consists in creating an ontology element and failing to provide human readable annotations attached to it. Consequently, ontology elements lack annotation properties that label them (e.g. rdfs:label, lemon:LexicalEntry, skos:prefLabel or skos:altLabel) or that define them (e.g. rdfs:comment or dc:description). This pitfall is related to the guidelines provided in [5].
[5] Vrandecic, D. (2010). Ontology Evaluation. PhD thesis.
• The following elements have neither rdfs:comment or skos:definition defined:
› http://emmo.info/domains/emmo-models.owl#EMMO_4456a5d2_16a6_4ee1_9a8e_5c75956b28ea
› http://emmo.info/domains/emmo-models.owl#EMMO_53935db0_af45_4426_b9e9_244a0d77db00
› http://emmo.info/domains/emmo-models.owl#EMMO_22522299_4091_4d1f_82a2_3890492df6db
› http://emmo.info/domains/emmo-models.owl#EMMO_9c32fd69_f480_4130_83b3_fb25d9face14
› http://emmo.info/domains/emmo-models.owl#EMMO_f7ed665b_c2e1_42bc_889b_6b42ed3a36f0
› http://emmo.info/domains/emmo-models.owl#EMMO_b29fd350_39aa_4af7_9459_3faa0544cba6
› http://emmo.info/domains/emmo-models.owl#EMMO_f19ff3b4_6bfe_4c41_a2b2_9affd39c140b
› http://emmo.info/domains/emmo-models.owl#EMMO_6eca09be_17e9_445e_abc9_000aa61b7a11
› http://emmo.info/domains/emmo-models.owl#EMMO_314d0bd5_67ed_437e_a609_36d46147cea7
› http://emmo.info/domains/emmo-models.owl#EMMO_db9a009e_f097_43f5_9520_6cbc07e7610b
› http://emmo.info/domains/emmo-models.owl#EMMO_a4b14b83_9392_4a5f_a2e8_b2b58793f59b
› http://emmo.info/domains/emmo-models.owl#EMMO_6c739b1a_a774_4416_bb31_1961486fa9ed
› http://emmo.info/domains/emmo-models.owl#EMMO_84cadc45_6758_46f2_ba2a_5ead65c70213
› http://emmo.info/domains/emmo-material.owl#EMMO_df808271_df91_4f27_ba59_fa423c51896c
› http://emmo.info/domains/emmo-material.owl#EMMO_5b2222df_4da6_442f_8244_96e9e45887d1
› http://emmo.info/domains/emmo-material.owl#EMMO_50781fd9_a9e4_46ad_b7be_4500371d188d
› http://emmo.info/domains/emmo-material.owl#EMMO_eb3c61f0_3983_4346_a0c6_e7f6b90a67a8
› http://emmo.info/domains/emmo-material.owl#EMMO_174cf221_9d16_427c_abea_e217a948969b
› http://emmo.info/domains/emmo-material.owl#EMMO_1067b97a_84f8_4d22_8ace_b842b8ce355c
› http://emmo.info/domains/emmo-material.owl#EMMO_87ac88ff_8379_4f5a_8c7b_424a8fff1ee8
› http://emmo.info/domains/emmo-material.owl#EMMO_70dac51e_bddd_48c2_8a98_7d8395e91fc2
› http://emmo.info/domains/emmo-material.owl#EMMO_f835f4d4_c665_403d_ab25_dca5cc74be52
› http://emmo.info/domains/emmo-material.owl#EMMO_e5488299_8dab_4ebb_900a_26d2abed8396
› http://emmo.info/domains/emmo-material.owl#EMMO_25f8b804_9a0b_4387_a3e7_b35bce5365ee
› http://emmo.info/domains/emmo-material.owl#EMMO_7d66bde4_b68d_41cc_b5fc_6fd98c5e2ff0
› http://emmo.info/domains/emmo-material.owl#EMMO_8f87e700_99a8_4427_8ffb_e493de05c217
› http://emmo.info/domains/emmo-material.owl#EMMO_8043d3c6_a4c1_4089_ba34_9744e28e5b3d
› http://emmo.info/domains/emmo-material.owl#EMMO_3c218fbe_60c9_4597_8bcf_41eb1773af1f
› http://emmo.info/domains/emmo-material.owl#EMMO_5c4aff3c_c30c_4507_86d5_b4df41eb9f2f
› http://emmo.info/domains/emmo-material.owl#EMMO_a2b006f2_bbfd_4dba_bcaa_3fca20cd6be1
› http://emmo.info/domains/emmo-material.owl#EMMO_7db59e56_f68b_48b7_ae99_891c35ae5c3b
› http://emmo.info/domains/emmo-material.owl#EMMO_385b8f6e_43ac_4596_ad76_ac322c68b7ca
› http://emmo.info/domains/emmo-material.owl#EMMO_72d53756_7fb1_46ed_980f_83f47efbe105
› http://emmo.info/domains/emmo-material.owl#EMMO_4588526f_8553_4f4d_aa73_a483e88d599b
› http://emmo.info/domains/emmo-math.owl#EMMO_fe7e56ce_118b_4243_9aad_20eb9f4f31f6
› http://emmo.info/domains/emmo-math.owl#EMMO_1a663927_3b68_4618_acd3_a8aa0d406329
› http://emmo.info/domains/emmo-math.owl#EMMO_031d61af_6405_41de_8880_df2f85a53383
› http://emmo.info/domains/emmo-physical-properties.owl#EMMO_f2d5d3ad_2e00_417f_8849_686f3988d929
› http://emmo.info/domains/emmo-physical-properties.owl#EMMO_dd4a7f3e_ef56_466c_ac1a_d2716b5f87ec
› http://emmo.info/domains/emmo-physical-properties.owl#EMMO_c46f091c_0420_4c1a_af30_0a2c8ebcf7d7
› http://emmo.info/domains/emmo-physical-properties.owl#EMMO_b081b346_7279_46ef_9a3d_2c088fcd79f4
› http://emmo.info/domains/emmo-physical-properties.owl#EMMO_909415d1_7c43_4d5e_bbeb_7e1910159f66
› http://emmo.info/domains/emmo-physical-properties.owl#EMMO_463bcfda_867b_41d9_a967_211d4d437cfb
› http://emmo.info/domains/emmo-geometry.owl#EMMO_0ef4ff4a_5458_4f2a_b51f_4689d472a3f2
› http://emmo.info/domains/emmo-geometry.owl#EMMO_46f0f8df_4dc6_418f_8036_10427a3a288e
› http://emmo.info/domains/emmo-geometry.owl#EMMO_25f5ca8e_8f7f_44d8_a392_bd3fe8894458
› http://emmo.info/domains/emmo-geometry.owl#EMMO_9268958f_7f54_48ab_a693_febe2645892b
› http://emmo.info/domains/emmo-geometry.owl#EMMO_0c576e13_4ee7_4f3d_bfe9_1614243df018
› http://emmo.info/domains/emmo-geometry.owl#EMMO_d7bf784a_db94_4dd9_861c_54f262846fbf
› http://emmo.info/domains/emmo-geometry.owl#EMMO_0ab0485c_9e5b_4257_a679_90a2dfba5c7c
› http://emmo.info/domains/emmo-geometry.owl#EMMO_5f278af9_8593_4e27_a717_ccc9e07a0ddf
› http://emmo.info/domains/emmo-geometry.owl#EMMO_86060335_31c2_4820_b433_27c64aea0366
› http://emmo.info/domains/emmo-geometry.owl#EMMO_b2a234a8_579a_422c_9305_b8f7e72c76cd
› http://emmo.info/domains/emmo-geometry.owl#EMMO_39362460_2a97_4367_8f93_0418c2ac9a08
› http://emmo.info/domains/emmo-geometry.owl#EMMO_3e309118_e8b7_4021_80f4_642d2df65d94
› http://emmo.info/domains/emmo-usercase.owl#EMMO_e775e341_5687_4d45_b50c_379b098a8c26
› http://emmo.info/domains/emmo-usercase.owl#EMMO_494b372c_cfdf_47d3_a4de_5e037c540de8
› http://emmo.info/perspectives/emmo-semiotics.owl#EMMO_008fd3b2_4013_451f_8827_52bceab11841
› http://emmo.info/perspectives/emmo-semiotics.owl#EMMO_0527413c_b286_4e9c_b2d0_03fb2a038dee
› http://emmo.info/perspectives/emmo-semiotics.owl#EMMO_0cd58641_824c_4851_907f_f4c3be76630c
› http://emmo.info/perspectives/emmo-semiotics.owl#EMMO_054af807_85cd_4a13_8eba_119dfdaaf38b
› http://emmo.info/domains/emmo-properties.owl#EMMO_1b52ee70_121e_4d8d_8419_3f97cd0bd89c
› http://emmo.info/domains/emmo-properties.owl#EMMO_10a5fd39_06aa_4648_9e70_f962a9cb2069
› http://emmo.info/perspectives/emmo-processual.owl#EMMO_0277f24a_ea7f_4917_81b7_fb0406c8fc62
› http://emmo.info/domains/emmo-models.owl#EMMO_24c71baf_6db6_48b9_86c8_8c70cf36db0c
› http://emmo.info/domains/emmo-math.owl#EMMO_3446e167_c576_49d6_846c_215bb8878a55
› http://emmo.info/perspectives/emmo-existent.owl#EMMO_b2282816_b7a3_44c6_b2cb_3feff1ceb7fe
› http://emmo.info/perspectives/emmo-existent.owl#EMMO_a50d920d_1ee3_4668_9a73_5d80a1c6fe15
› http://emmo.info/perspectives/emmo-existent.owl#EMMO_65a2c5b8_e4d8_4a51_b2f8_e55effc0547d
› http://emmo.info/perspectives/emmo-semiotics.owl#EMMO_eb3518bf_f799_4f9e_8c3e_ce59af11453b
› http://emmo.info/perspectives/emmo-semiotics.owl#EMMO_60577dea_9019_4537_ac41_80b0fb563d41
› http://emmo.info/perspectives/emmo-semiotics.owl#EMMO_39c3815d_8cae_4c8f_b2ff_eeba24bec455
› http://emmo.info/perspectives/emmo-semiotics.owl#EMMO_297999d6_c9e4_4262_9536_bd524d1c6e21
› http://emmo.info/perspectives/emmo-semiotics.owl#EMMO_2337e25c_3c60_43fc_a8f9_b11a3f974291
› http://emmo.info/domains/emmo-properties.owl#EMMO_e1097637_70d2_4895_973f_2396f04fa204
› http://emmo.info/perspectives/emmo-processual.owl#EMMO_c5aae418_1622_4d02_93c5_21159e28e6c1
› http://emmo.info/base/emmo-mereotopology.owl#EMMO_7afbed84_7593_4a23_bd88_9d9c6b04e8f6
› http://emmo.info/base/emmo-4d.owl#EMMO_f68030be_94b8_4c61_a161_886468558054
› http://emmo.info/base/emmo-4d.owl#EMMO_6e046dd0_9634_4013_b2b1_9cc468087c83
› http://emmo.info/base/emmo-mereotopology.owl#EMMO_4d6504f1_c470_4ce9_b941_bbbebc9ab05d
› http://emmo.info/base/emmo-mereotopology.owl#EMMO_d893d373_b579_4867_841e_1c2b31a8d2c6
› http://emmo.info/base/emmo-mereotopology.owl#EMMO_9380ab64_0363_4804_b13f_3a8a94119a76
› http://emmo.info/base/emmo-mereotopology.owl#EMMO_517dfaf9_4970_41ac_81ee_d031627d2c7c
› http://emmo.info/base/emmo-mereotopology.owl#EMMO_6b7276a4_4b9d_440a_b577_0277539c0fc4
› http://emmo.info/base/emmo-mereotopology.owl#EMMO_ec2472ae_cf4a_46a5_8555_1556f5a6c3c5
› http://emmo.info/base/emmo-mereotopology.owl#EMMO_17e27c22_37e1_468c_9dd7_95e137f73e7f
› http://emmo.info/base/emmo-mereotopology.owl#EMMO_9cb984ca_48ad_4864_b09e_50d3fff19420
The reason that EMMO is divided into several modules is to organise the ontology into topical related concepts, not impose namespaces.
All names and skos:prefLabels are required to be unique within EMMO top and middle. Hence, there are no need for namespacing within EMMO top and middle. As suggested by Matthias, using a single namespace will make it simpler to move entities between modules and thereby simplify maintainance.
If we go for this, remember to document it in the governance document.
From running OntOlogy Pitfall skanner! (OOPS!) on http://oops.linkeddata.es/
SUGGESTION: symmetric or transitive object properties.3 cases
The domain and range axioms are equal for each of the following object properties. Could they be symmetric or transitive?
› http://emmo.info/perspectives/emmo-existent.owl#EMMO_b2282816_b7a3_44c6_b2cb_3feff1ceb7fe (has spatial direct part)
› http://emmo.info/perspectives/emmo-existent.owl#EMMO_a50d920d_1ee3_4668_9a73_5d80a1c6fe15 (has spatiotemporal direct part)
› http://emmo.info/base/emmo-mereotopology.owl#EMMO_ec2472ae_cf4a_46a5_8555_1556f5a6c3c5 (emmo relation)
Within manufacturing, the term "continuous manufacturing" is normally used for a manufacturing process that is continuous in time as opposed to manufacturing in batches. This is not the same as 'ContinuousManufacturing' in EMMO, which is currently used for a manufacturing process whose product is the result of the combination of more substances.
Is it possible to find another term for this that will be understod correctly within the manufacturing domain?
When exporting the inferred ontology from Protege, all superproperties of annotations are stripped off. This seems to be a bug in Protege, but might also be a result of that OWL-DL does not support annotation superproperties. Nevertheless, we want the superproperties back in the inferred ontology.
Create a script that adds the annotation superproperties back to the inferred ontology.
A declarative, efficient, and flexible JavaScript library for building user interfaces.
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
An Open Source Machine Learning Framework for Everyone
The Web framework for perfectionists with deadlines.
A PHP framework for web artisans
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
Some thing interesting about web. New door for the world.
A server is a program made to process requests and deliver data to clients.
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
Some thing interesting about visualization, use data art
Some thing interesting about game, make everyone happy.
We are working to build community through open source technology. NB: members must have two-factor auth.
Open source projects and samples from Microsoft.
Google ❤️ Open Source for everyone.
Alibaba Open Source for everyone
Data-Driven Documents codes.
China tencent open source team.