Giacomo De Colle

Would love to see this being implemented. We are lacking in resources to teach SPARQL to people and this would become an essential teaching tool for knowledge graph engineering and...

Also interested in seeing updates on this

Added this to map "contains" to "has continuant part". This seems to create inconsistencies when running a reasoner, so it will probably require more precise developments.

As an example d3f:Certificate is Digital Information Bearer, i.e. an IBE in CCO terms, which d3f:contains some d3f:PublicKey. d3f:PublicKey is a d3f:DigitalInformation, i.e. an ICE in CCO terms.  Now,...

Yes, the question is whether d3f:DigitalInformation (and d3f:DigitalInformationBearer) are material or not. The information model of CCO is currently under scrutiny for changes (see [this issue](https://github.com/CommonCoreOntology/CommonCoreOntologies/issues/564) for example). So, I...

Changed certificate parent term as per discussion with @netfl0 and per @hack-sentinel's comment. I am checking other classes that generate inconsistencies next. See issue 376 [https://github.com/d3fend/d3fend-ontology/issues/376](url) for a related point.

@netfl0 yes, the PR I opened a couple days ago solves these issues and adds new stuff. Incidentally, @hack-sentinel's comment on certificates here is potentially contradicting what we discussed last...

TODO: - [x] mappings from YAML to D3FEND to rewrite pipeline - [ ] Check queries with the new models and terms

@jravenel The terms to use to rebuild the slim and then the YAML are: - d3f:Agent - d3f:Digital Artifact - d3f:Event - d3f:DefensiveTactic and its subclasses - d3f:OffensiveTactic and its...

@aamedina Can I ask why you wanted to say that Adrian is a user account? If Adrian is a person, I would say that Adrian has a user account, not...