Skip to content
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

sto:hasTag punning as DataProperty and ObjectPropery #55

Closed
SpyrosKou opened this issue Sep 10, 2018 · 4 comments
Closed

sto:hasTag punning as DataProperty and ObjectPropery #55

SpyrosKou opened this issue Sep 10, 2018 · 4 comments

Comments

@SpyrosKou
Copy link
Contributor

Hello again,
I noticed that sto:hasTag is declared both as a DataProperty and an ObjectPropery.
In particular:

###  https://w3id.org/i40/sto#hasTag
sto:hasTag rdf:type owl:ObjectProperty ;
           rdfs:domain sto:Publication .
###  https://w3id.org/i40/sto#hasTag
sto:hasTag rdf:type owl:DatatypeProperty ;
           rdfs:range muto:Tag ,
                      rdfs:Literal .

The individuals currently using the sto:hasTag exclusively use it as a DataProperty. (138 occurencies)
Perhaps it would be best to remove the ObjectPropery sto:hasTag definition since punning an IRI for more than one property types is currently unsupported.
See: https://www.w3.org/TR/owl2-new-features/#F12:_Punning

I could create a pull request if you agree.

@igrangel
Copy link
Contributor

Yes, definitely a mistake. The initial idea was to reuse the muto:tag but it was complicated for the need we have. So, please go ahead.

@igrangel
Copy link
Contributor

I merged everything into the master branch since we had other branches but I think now is fine.

@SpyrosKou
Copy link
Contributor Author

Thank you,

I created a pull request.

@igrangel
Copy link
Contributor

Please, create a link to the line of code when this type of issues occur.

@igrangel igrangel reopened this Sep 10, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants