Re: [web-annotation] HTML Serialization Use Cases

# Use case: Dynamically extending a Web page with annotation(s)

An interactive annotation system incorporates the annotation into the 
annotated HTML page. This is done by extending the DOM of the HTML 
page at load (or interaction) time (eg, retrieving the annotations 
from a server), using the (DOM version of the) HTML serialization of 
each annotation. By doing so, it leaves the display of the annotation 
to the browser's (or the reading system's) display engine.

The user/reader of the HTML page can add CSS statements to style the 
annotations themselves. Because the annotations use a standard, the 
CSS can refer to the standard set of elements and attributes; the 
effect will be the same regardless of which annotation system is used.

In effect, by using a standard HTML serialization, the content and the
 style becomes strictly separated.

## Characterizations
* It is immaterial whether the serialization is defined in terms of 
new elements and/or new attributes (as extensions to HTML) or specific
 values for already existing attributes (eg, RDFa or microdata), as 
long as it is clear how to make the right CSS selections.
* In this use case the target and most of the body (eg, the textual 
body, but possibly other media, too) are, after the DOM injection, in 
the same document as far as the browser is concerned. But, because 
this is done dynamically at load time, this may not have much 
influence on the serialization.


-- 
GitHub Notification of comment by iherman
Please view or discuss this issue at 
https://github.com/w3c/web-annotation/issues/147#issuecomment-177978970
 using your GitHub account

Received on Monday, 1 February 2016 13:51:05 UTC