-
Notifications
You must be signed in to change notification settings - Fork 0
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
nif:opinion vs marl:extractedFrom #1
Milestone
Comments
|
I believe there should at least some kind of reasons why everyone thinks they are so hard working. This actually would say who's hard working the most. |
For the record, I'm neither German nor Greek. This above is a joking example. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
NIF integrates MARL using property nif:opinion from nif:String to marl:Opinion.
But that's declared inverseOf marl:extractedFrom, which in the MARL example points to sioc:Post (not the nif:String content of the post).
So something doesn't mesh here. We could mix sioc and nif properties on the comment URL, but then nif:sourceUrl points to itself...
See details in attachment
The text was updated successfully, but these errors were encountered: