- From: Karol Szczepański via GitHub <sysbot+gh@w3.org>
- Date: Mon, 25 May 2020 08:54:09 +0000
- To: public-hydra-logs@w3.org
No, I'd leave it as it is now. I wouldn't introduce new constructs just for SHACL. I think `IriTemplateMapping` is good enough to cover any scenario.
Consider this:
```turtle
my:Class a rdfs:Class .
my:predicate a rdfs:Property;
rdfs:domain my:Class .
my:Class a owl:Class .
my:predicate a owl:FunctionalProperty;
rdfs:domain my:Class .
my:Class a sh:NodeShape;
sh:property [
sh:path my:predicate
] .
```
All of the above snippets defines same concept (more or less) of a class `my:class` with predicate `my:predicate`. From mapping point of view, you'll have an RDF graph of...:
```turtle
some:resource my:predicate "value .
```
...in which case it won't matter how the `my:predicate` is defined. You have to grab it's value and put it in the template. Simple as that.
--
GitHub Notification of comment by alien-mcl
Please view or discuss this issue at https://github.com/HydraCG/Specifications/issues/214#issuecomment-633460785 using your GitHub account
Received on Monday, 25 May 2020 08:54:11 UTC