- From: Karol Szczepański via GitHub <sysbot+gh@w3.org>
- Date: Wed, 13 Feb 2019 21:12:53 +0000
- To: public-hydra-logs@w3.org
> For the record - and I think this will perhaps come up again: No problem with that - if some real case pops out, we can discuss it. > I disagree that this would make "implementing clients a nightmare". It will. RDF does not make things easy. While we try to mention in the spec to explicitly type resources we we can hookup correct logic in the client, we won't be able to enforce that rule and the client needs to understand RDF basics including range/domain rules. I wouldn't like to use any advance reasoning mechanism within the client, thus implementing basics is quite complicated. Throwing `@reverse`, which is conceptually equal to `owl:inverseOf` will make things even more complicated. Unless JSON-LD API resolves it to some simple form, taking special care of `@reverse` complicate things from my perspective. -- GitHub Notification of comment by alien-mcl Please view or discuss this issue at https://github.com/HydraCG/Specifications/issues/40#issuecomment-463373398 using your GitHub account
Received on Wednesday, 13 February 2019 21:12:56 UTC