Re: [web-annotation] item vs. member in multiplicity constructs

@BigBlueHat Dropping composite has been proposed. No actual agreement 
has been reached that I know of. I can see where most of the problems 
are though. There's a large disconnect between what collections, 
lists, aggregations are and how we serialize them. Because of 
serialization and the manner in which text gets parsed there's little 
use in differentiating between (so-called) unordered lists and ordered
 lists. The difference in serialization languages such as html is 
strictly presentational.

IMO all of these issues are out of scope for an annotation standard. 
We should leave these issues (choice, list, composite, etc.) for other
 working groups to solve.

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

Received on Wednesday, 27 January 2016 15:25:36 UTC