W3C home > Mailing lists > Public > public-dxwg-wg@w3.org > May 2022

Re: [dxwg] Addressing issue #1503 (#1505)

From: Andrea Perego via GitHub <sysbot+gh@w3.org>
Date: Wed, 11 May 2022 09:21:29 +0000
To: public-dxwg-wg@w3.org
Message-ID: <issue_comment.created-1123417704-1652260887-sysbot+gh@w3.org>
@agbeltran said:

> @dr-shorthair good point, `next` is not in the ttl file but it is on the table here: https://w3c.github.io/dxwg/dcat/#inverse-properties; I suppose we need to add it to the ttl and leave it to DCAT users to follow the recommendation about inverses - please comment if you disagree

A possible option is that we do include all the inverse properties in the `.ttl`, but just to state that they are inverses:

dcat:inCatalog owl:inverseOf dcat:resource .

dcat:next owl:inverseOf dcat:prev .

dcat:nextVersion owl:inverseOf dcat:previousVersion .

dcat:isVersionOf owl:inverseOf dcat:hasVersion .

dcat:seriesMember owl:inverseOf dcat:inSeries .

Possibly, we can also include a usage note stating that they can be used in addition to (and not to replace) the relevant property.

GitHub Notification of comment by andrea-perego
Please view or discuss this issue at https://github.com/w3c/dxwg/pull/1505#issuecomment-1123417704 using your GitHub account

Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Wednesday, 11 May 2022 09:21:31 UTC

This archive was generated by hypermail 2.4.0 : Wednesday, 11 May 2022 09:21:33 UTC