Re: [dxwg] Do we need a new property dcat:seriesMember defined as dcat:inSeries's inverse? (#1335)

Which aspect of that statement are you interested in here @riannella? Is it just the different serializations? 
That is not important - I used TTL because it is easier to type into a GitHub issue. No problem if you prefer one of the other serializations. 

The point I was trying to make is that if `dcat:seriesMember owl:inverseOf dcat:inSeries .` then 
```
<m99> dcat:inSeries <s88> . 
```
provides exactly the same information as 
```
<s88> dcat:seriesMember <m99> . 
```
and it is just as easy to add one of these to the graph as the other. And SPARQL works both ways just as easily. So we might as well standardize on just one direction, so we avoid the inconsistency situation that you describe altogether . (I think this is what @agreiner and @jakubklimek are saying too.) 

-- 
GitHub Notification of comment by dr-shorthair
Please view or discuss this issue at https://github.com/w3c/dxwg/issues/1335#issuecomment-805483038 using your GitHub account


-- 
Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config

Received on Wednesday, 24 March 2021 04:36:03 UTC