- From: Stian Soiland-Reyes <soiland-reyes@cs.manchester.ac.uk>
- Date: Fri, 1 Feb 2013 16:23:03 +0000
- To: Robert Sanderson <azaroth42@gmail.com>
- Cc: public-openannotation <public-openannotation@w3.org>
This: > It is important to be aware of the consequences of using a Fragment URI, and the restrictions that using them places on implementations. Change to: > It is important to be aware of the consequences of using a Fragment URI for the purpose of identifying parts of a resource, and the restrictions that using them places on implementations. As you did not want to add a 'disclaimer' for Fragment URIs for semantic tags. (which is the norm). On Fri, Feb 1, 2013 at 3:55 PM, Robert Sanderson <azaroth42@gmail.com> wrote: > To summarize the changes, before Monday's launch: > > On Mon, Jan 28, 2013 at 4:08 PM, Robert Sanderson <azaroth42@gmail.com> wrote: > >> Antoine: >> * Homogeneity of JSON context names > Done. > >> * Named / Embedded Graphs > Rewritten and reordered as suggested. > >> * Lists and Containers > Choice and Composite are subclasses of Alt and Bag, List is > dual-classed with an extensive note describing the issues. > >> * Specific Resources with Style and Scope > 3.1 rewritten to not include the diagram, and clarify that style and > scope are included in the definition of the identity of the specific > resource. > >> * Lack of consensus on Textual Bodies > No change. > > Rob > -- Stian Soiland-Reyes, myGrid team School of Computer Science The University of Manchester
Received on Friday, 1 February 2013 16:23:50 UTC