Code Monkey home page Code Monkey logo

ecrm's People

Contributors

knurg avatar reinfandt avatar vladimiralexiev avatar

Stargazers

 avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar

Watchers

 avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar

ecrm's Issues

P7 took place at / P7 witness appears in the cardinality restriction ObjectMinCardinality

Hello, I think there is a bug in the ontology: P7 took place at can't be exactly 1.

Context:
Protégé 5.2.0 on macOS 10.13.5 with Hermit 1.3.8.413, erlangen imported from url: http://erlangen-crm.org/ontology/ecrm/ecrm_170309.owl

HOW TO REPRODUCE:

Define a new activity (disjoint from siblings) with:

'P7 took place at' exactly 1 'E53 Place' and 'P7 took place at' only 'E53 Place'

running Hermit fails, with protege.log:


------------------------------- Running Reasoner -------------------------------
2018-06-15 18:41:07.217 [Classification Thread] INFO  OWLReasonerManager    
2018-06-15 18:41:07.218 [Classification Thread] ERROR OWLReasonerManager    An error occurred during reasoning: Non-simple property '<http://erlangen-crm.org/170309/P7_took_place_at>' or its inverse appears in the cardinality restriction 'ObjectMinCardinality(2 <http://erlangen-crm.org/170309/P7_took_place_at> <http://erlangen-crm.org/170309/E53_Place>)'..
java.lang.IllegalArgumentException: Non-simple property '<http://erlangen-crm.org/170309/P7_took_place_at>' or its inverse appears in the cardinality restriction 'ObjectMinCardinality(2 <http://erlangen-crm.org/170309/P7_took_place_at> <http://erlangen-crm.org/170309/E53_Place>)'.
	at org.semanticweb.HermiT.structural.ObjectPropertyInclusionManager.rewriteAxioms(ObjectPropertyInclusionManager.java:123) ~[na:na]
	at org.semanticweb.HermiT.structural.OWLClausification.preprocessAndClausify(OWLClausification.java:161) ~[na:na]
	at org.semanticweb.HermiT.Reasoner.loadOntology(Reasoner.java:208) ~[na:na]
	at org.semanticweb.HermiT.Reasoner.<init>(Reasoner.java:199) ~[na:na]
	at org.semanticweb.HermiT.Reasoner.<init>(Reasoner.java:173) ~[na:na]
	at org.semanticweb.HermiT.ReasonerFactory.createHermiTOWLReasoner(ReasonerFactory.java:51) ~[na:na]
	at org.semanticweb.HermiT.ReasonerFactory.createReasoner(ReasonerFactory.java:19) ~[na:na]
	at org.protege.editor.owl.model.inference.ReasonerUtilities.createReasoner(ReasonerUtilities.java:20) ~[na:na]
	at org.protege.editor.owl.model.inference.OWLReasonerManagerImpl$ClassificationRunner.ensureRunningReasonerInitialized(OWLReasonerManagerImpl.java:428) ~[na:na]
	at org.protege.editor.owl.model.inference.OWLReasonerManagerImpl$ClassificationRunner.run(OWLReasonerManagerImpl.java:386) ~[na:na]
	at java.lang.Thread.run(Thread.java:745) ~[na:1.8.0_40]


To me it seems like I have no control on this issue, I think it may be something on your side?

Add P81a, P81b, P82a and P82b data properties

The RDFS 6.2.1 version of CIDOC CRM contains the properties P81a, P81b, P82a and P82b which allow to assign datetimes to the P81 and P82 properties.

They should be added to ECRM.

Here is a copy/paste definition of those properties:

<rdf:Property rdf:about="P81a_end_of_the_begin">
  <rdfs:label xml:lang="en">end of the begin</rdfs:label>
  <rdfs:label xml:lang="el">τέλος της αρχής</rdfs:label>
  <rdfs:label xml:lang="de">Ende des Anfangs</rdfs:label>
  <rdfs:label xml:lang="fr">fin du début</rdfs:label>
  <rdfs:label xml:lang="ru">конец начала</rdfs:label>
  <rdfs:label xml:lang="pt">fim do início</rdfs:label>
  <rdfs:comment>
    This is defined as the first boundary of the property P81
  </rdfs:comment>
  <rdfs:domain rdf:resource="E52_Time-Span"/>
  <rdfs:range rdf:resource="http://www.w3.org/2001/XMLSchema#dateTime"/>
  <rdfs:subPropertyOf rdf:resource="P81_ongoing_throughout"/>
</rdf:Property>
<rdf:Property rdf:about="P81b_begin_of_the_end">
  <rdfs:label xml:lang="en">begin of the end</rdfs:label>
  <rdfs:label xml:lang="fr">début de la fin</rdfs:label>
  <rdfs:label xml:lang="el">αρχή του τέλους</rdfs:label>
  <rdfs:label xml:lang="de">Anfang vom Ende</rdfs:label>
  <rdfs:label xml:lang="ru">начать в конце</rdfs:label>
  <rdfs:label xml:lang="pt">começar do fim</rdfs:label>
  <rdfs:comment>
    This is defined as the second boundary of the property P81
  </rdfs:comment>
  <rdfs:domain rdf:resource="E52_Time-Span"/>
  <rdfs:range rdf:resource="http://www.w3.org/2001/XMLSchema#dateTime"/>
  <rdfs:subPropertyOf rdf:resource="P81_ongoing_throughout"/>
</rdf:Property>
<rdf:Property rdf:about="P82a_begin_of_the_begin">
  <rdfs:label xml:lang="en">begin of the begin</rdfs:label>
  <rdfs:label xml:lang="fr">début du début</rdfs:label>
  <rdfs:label xml:lang="el">αρχή της αρχής</rdfs:label>
  <rdfs:label xml:lang="de">Anfang des Anfangs</rdfs:label>
  <rdfs:label xml:lang="ru">начать с начала</rdfs:label>
  <rdfs:label xml:lang="pt">começar do início</rdfs:label>
  <rdfs:comment>
    This is defined as the first boundary of the property P82
  </rdfs:comment>
  <rdfs:domain rdf:resource="E52_Time-Span"/>
  <rdfs:range rdf:resource="http://www.w3.org/2001/XMLSchema#dateTime"/>
  <rdfs:subPropertyOf rdf:resource="P82_at_some_time_within"/>
</rdf:Property>
<rdf:Property rdf:about="P82b_end_of_the_end">
<rdfs:label xml:lang="en">end of the end</rdfs:label>
<rdfs:label xml:lang="fr">fin de la fin</rdfs:label>
<rdfs:label xml:lang="el">τέλος του τέλους</rdfs:label>
<rdfs:label xml:lang="de">Ende vom Ende</rdfs:label>
<rdfs:label xml:lang="ru">конец конец</rdfs:label>
<rdfs:label xml:lang="pt">fim do fim</rdfs:label>
<rdfs:comment>
This is defined as the second boundary of the property P82
</rdfs:comment>
<rdfs:domain rdf:resource="E52_Time-Span"/>
<rdfs:range rdf:resource="http://www.w3.org/2001/XMLSchema#dateTime"/>
<rdfs:subPropertyOf rdf:resource="P82_at_some_time_within"/>
</rdf:Property>

Here is the corresponding file: http://www.cidoc-crm.org/sites/default/files/cidoc_crm_v6.2.1-2018April.rdfs

P106_has_component / P106_is_composed_of

Hello,

We are working on a new ontology for music called DOREMUS and extending CIDOC CRM and FRBRoo.
We import ecrm: http://erlangen-crm.org/current/
and efrbroo: http://erlangen-crm.org/efrbroo/

We noticed there are two P106 properties imported:

  • P106_has_component
  • P106_is_composed_of

Both are superproperties of different FRBRoo properties.

To be complete, I should also mention that
(1) the official name of P106 in CRM is "is composed of"
(2) P106_has_component only has one FRBRoo subproperty : R14_incorporates, which is deprecated.

Can you be so kind as to check where the problem lies?
With all best wishes,
Pierre Choffé

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. 📊📈🎉

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google ❤️ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.