- From: Rob Sanderson via GitHub <sysbot+gh@w3.org>
- Date: Tue, 03 Nov 2015 00:46:16 +0000
- To: public-annotation@w3.org
azaroth42 has just created a new issue for https://github.com/w3c/web-annotation: == Simplification: Multiplicity and Collections == It was brought up at TPAC that there's quite a lot of semantic overlap between Composite and Collection, List and OrderedCollection. They all use the notion of items and the same basic construction of a wrapper around an rdf:List or repeated predicate. We could simplify this situation by dropping Composite and List in favor of the AS Collections. Further, we could require OrderedCollection and if you don't care about the order, then you won't care that there is an order. In assessing the impact, Benjamin and Rob could not find in a use case or think of any situation where this was damaging. Proposal: * Delete oa:Composite and oa:List, and just use as:OrderedCollection. * Make oa:Choice a subClassOf as:OrderedCollection * [Propose to ActivityStreams to drop non OrderedCollections as unnecessary] This is also related to a second issue, regarding the Selector (or indeed Specifier) workflow and that Choice/List are overkill for the intended functionality See https://github.com/w3c/web-annotation/issues/92
Received on Tuesday, 3 November 2015 00:46:20 UTC