Re: [protege-user] people example

Michael DeBellis <[email protected]>
Newsgroups gmane.comp.misc.ontology.protege.owl
Message-ID <CALGFikc6xWoq2Vo-KbmmgiC=76d0zZCWvQspD3OHRo3kRNknQA@mail.gmail.com>
I have a People ontology on my blog and I talk about the OWA and give
examples of how certain axioms that one would expect to trigger reasoning
(e.g., a Hermit is a subclass of Person with 0 hasSocialRelation) don't due
to the OWA: https://www.michaeldebellis.com/post/the-people_example-ontology
But I never wrote SHACL to show how to correctly deal with such constraints
for the ontology (although I have thought about doing it, just never got
around to it). I do mention SHACL in the document that describes the
ontology but I just double checked and I don't actually walk through how to
use the SHACL plugin in that document.

In the revised Pizza tutorial:
https://www.michaeldebellis.com/post/new-protege-pizza-tutorial I do have
SHACL examples in chapter 11 (e.g., each Employee at the Pizza restaurant
must have exactly one socialSecurityNumber and it must have the format
NNN-NN-NNNN, where N is an integer). I think it would be rather straight
forward to take those examples and make them work with the People ontology.
If you want to do that take a look at what I wrote and give it a shot and
if you have problems let me know, I can probably help you get it to work.

Michael
https://www.michaeldebellis.com/blog

On Tue, Feb 4, 2025 at 12:24 AM stathoula terzidou <[email protected]>
wrote:

> Hello think i saw somewhere a tutorial with workarounds for owa about the
> people example but cant find it now anyone have it?
> _______________________________________________
> protege-user mailing list
> [email protected]
> https://mailman.stanford.edu/mailman/listinfo/protege-user
>

_______________________________________________
protege-user mailing list
[email protected]
https://mailman.stanford.edu/mailman/listinfo/protege-user
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.