- From: Rob Sanderson via GitHub <sysbot+gh@w3.org>
- Date: Tue, 29 Mar 2016 17:54:10 +0000
- To: public-annotation@w3.org
Currently, each item in a set of states is an alternative (e.g. avoiding an explicit choice node for those states) and the same for a set of selectors, but we don't say (and should) how to interpret them. We used to have: > It is expected that if a State is present, it will be processed first to ensure the correct representation is retrieved. Then, if there is a Selector, it would be applied to determine the correct segment of the representation. Finally, if there is a Style, it would be applied to ensure the correct rendering or the resource or segment. As Scopes do not affect the rendering directly, they may be processed in any way deemed appropriate for the user interface or application. And even further back had a workflow diagram, but it was seen as too prescriptive. -- GitHub Notification of comment by azaroth42 Please view or discuss this issue at https://github.com/w3c/web-annotation/issues/195#issuecomment-203025846 using your GitHub account
Received on Tuesday, 29 March 2016 17:54:12 UTC