-
Notifications
You must be signed in to change notification settings - Fork 11
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
wn.ttl #33
Comments
We certainly could do this. Could you be more specific about which constraints you would like to import? |
Sorry for being so general. At this point, there are so many fundamental differences between the models that I don't know from where we can start. See screenshot. I was calling the attention for the restrictions on relations such as https://github.com/own-pt/openWordnet-PT/blob/master/wn30.ttl#L110-L121. But I have subtypes for the Synset class. I am assuming that the wn.ttl here was created to model the XML scheme inspired by (or adopting fully) Ontolex (based on Lemon), right? My model started from the https://www.w3.org/TR/wordnet-rdf/ (it precedes Lemon and Ontolex), with few changes and improvements. It is hard to compare the models because each one has its goals. My goal was to model the WN abstract model, as simple as possible (synsets, senses and word forms). We are trying to make a strong claim that Global Wordnet Association defines/suggests/specifies a single RDF model for encoding wordnets, which may not be true. We may decide by the current model following arguments such as the first sentence in http://john.mccr.ae/papers/mccrae2017ontolex.pdf:
But I really don't know what support this claim. |
Okay, I am not sure what exactly you want here... There is another issue (#20) on creating support for the RDF files based on the W3C ontology, so I am happy to support you if you want to make a pull request for this. |
We may consider some previous definitions from https://github.com/own-pt/openWordnet-PT/blob/master/wn30.ttl? See constraints on the relations.
The text was updated successfully, but these errors were encountered: