[web-annotation] Including resource previews in annotations

gsergiu has just created a new issue for 
https://github.com/w3c/web-annotation:

== Including resource previews in annotations ==
The presentaion of Annotations (in client applications) to end users 
needs to be based on human readable information insted of URI. 
For example, when the Resources in the Annotations include the 
follwing URI  
`https://www.wikidata.org/wiki/Q43715`, at least the name of pe 
person, in this case "**Vlad Tepes**" , and eventually a depiction, in
 this case 
`https://commons.wikimedia.org/wiki/File:Vlad_Tepes_coloured_drawing.png`,
 should be displayed to the end users.

The generation of "previews" needs to be performed at creation time, 
either by client or by server, so that the retrieval of annotations 
and presentation of annotations should require only one http request. 
(This is especially important for annotations with multiple bodies 
and/or multiple targets)

The current specifications doesn't make any recommendations about how 
to include these previews in the Annotation serialization, even if the
 dc and foaf namespaces are  already included in the `@context`  

1. One possibility of including the previews is to embed them in the 
Resource Serialization like:
```
"body": {
    "id": "https://www.wikidata.org/wiki/Q43715",
    "format": "text/html",
    "dc:title": "Vlad Tepes - Wikidata"
  },
``` 
and 
```
"body": {
    "source": 
         { 
           "id" : "https://www.wikidata.org/wiki/Q43715",
           "format": "text/html",
          "dc:title": "Vlad Tepes - Wikidata"
       },
       "purpose" : "tagging"
  },
```
respectively.
  
2. Another posibility that would reduce verbosity is to use an own 
field for resourcePreview(s), like
"body": {
       "source":  "https://www.wikidata.org/wiki/Q43715",
        "purpose" : "tagging"
  },
 "resourcePreview": 
         { 
           "id" : "https://www.wikidata.org/wiki/Q43715",
           "format": "text/html",
          "dc:title": "Vlad Tepes - Wikidata"
       },

(PS: I didn't check the full syntactic correctness from the RDF 
perspective, but this can be done when the functionality is accepted 
for integration in the specifications)

So ... the two questions I have:
1. Can this functionality be included in the specifications before the
 CR?
2. Which should be the recommended way of adding previews, the option 
1, the option 2 or both?

Br,
Sergiu   



Please view or discuss this issue at 
https://github.com/w3c/web-annotation/issues/257 using your GitHub 
account

Received on Friday, 3 June 2016 08:52:09 UTC