Rob Sanderson
Rob Sanderson
The discussion has been mostly in terms of predicates, but should this apply also to instance URIs?
Let's take it to the WG list, and I'll update this comment to leave a pointer.
In a review, Luc wrote as comment 22: oa:serializedBy is subProperty of prov:wasAttributedTo is problematic. If PROV reasoning is applied, it may lead to incorrect conclusions (possibly logical inconsistency). ```...
@lucmoreau Could you propose a solution? The options that occur to me: - Simply drop the subPropertyOf relationship to prov for serializedBy/At. This doesn't feel clean. - Split the annotation...
+1. Would be great if @gobengo and @elf-pavlik could join one of the Annotation calls in the not-too-distant future to discuss?
Pinging this issue to see if there's possible progress? Perhaps in coordination with SocialWeb?
The frames are imported into an Appendix in -vocab: https://www.w3.org/TR/annotation-vocab/#annotation-collection-frame So I think it's an errata (and we should fix in the repo)
Then we would have to define all of the processing classes and identities for well known processors. That's far far outside of the scope of this working group. Sorry, but...
This is an issue with respec. As you can see here: https://github.com/w3c/web-annotation/blob/gh-pages/model/wd2/index-nametemplate.html#L373 We don't manually name the anchors at all.
In other words, while I agree this would be useful, I do not believe it qualifies as "Errata" and proposed to remove ErratumRaised, and instead treat as guidance for future...