- From: gsergiu via GitHub <sysbot+gh@w3.org>
- Date: Mon, 30 May 2016 20:54:13 +0000
- To: public-annotation@w3.org
gsergiu has just created a new issue for
https://github.com/w3c/web-annotation:
== Consistent definitions of the id for External Web Resources and
Specific Resources ==
The id property of the bodies and targets should have a consistent
definition
The current definitions:
1. For External Web Resouces states that the id is:
> The IRI that identifies the Body or Target resource.
> Bodies or Targets which are External Web Resources MUST have exactly
1 id with the value of the resource's IRI.
https://www.w3.org/TR/annotation-model/#external-web-resources
example 17:
```
"body": {
"id": "http://example.net/review1",
"rights": "http://creativecommons.org/licenses/by/4.0/"
}
```
With the given definition I would expect that the URI
http://example.net/review1, in combination with the
Accept:application/json should return:
{
"id": "http://example.net/review1",
"rights": "http://creativecommons.org/licenses/by/4.0/"
}
2. For Specific Resources, the id is:
> The identity of the Specific Resource
> A Specific Resource MAY have exactly 1 IRI that identifies it.
Syntactically correct Example (semantically .. probably not)
```
"body": {
"id": "http://example.net/resource1",
"source": "http://example.net/review1",
}
```
Again with the given definition of the id I would expect to get the
following json when using the application/json in the accept header
for http://example.net/resource1
{
"id": "http://example.net/resource1",
"source": "http://example.net/review1",
}
I think that these definitions are slightly ambiguous, and I assume
that their meaning will be better explained through the following:
1. For External Web Resources:
id: The IRI that identifies the External Resource referenced by the
Body or Target
2. For Specific Resources
id: The IRI that identifies the Body or Target representing the
SpecificResource
Still an open question remains:
Why should the ids of Bodies and Targets have different meanings
depending on their type?
Please view or discuss this issue at
https://github.com/w3c/web-annotation/issues/247 using your GitHub
account
Received on Monday, 30 May 2016 20:54:16 UTC