- From: Rob Sanderson via GitHub <sysbot+gh@w3.org>
- Date: Thu, 05 Nov 2015 17:43:26 +0000
- To: public-annotation@w3.org
If you're okay with List and Choice we could go ahead with that part
and save the discussion of Composite until you have time.
What would be most useful is concrete use cases in which List could
not fulfill the role of Composite and implementations would be
meaningfully impacted. Remember that inferencing and reasoning are
not critical requirements, so please try to come up with UCs that
aren't based on them. For example, in what way does the collage of
images require there to be no order at all (especially given that
there will be an order inherent in the serialization), rather than
just ignoring that order. In JSON-LD, our primary serialization, both
are going to look identical after all:
```
{
"type": "Composite",
"items": [ "iron", "iron", "iron", "bonemeal"] // an @set
}
{
"type": "List":,
"items": ["iron", "iron", "iron", "bonemeal"] // an @list
}
```
--
GitHub Notif of comment by azaroth42
See
https://github.com/w3c/web-annotation/issues/92#issuecomment-154134387
Received on Thursday, 5 November 2015 17:43:28 UTC