- From: Renato Iannella <renato.iannella@monegraph.com>
- Date: Fri, 23 Jun 2017 11:09:51 +1000
- To: W3C POE WG <public-poe-wg@w3.org>
- Message-Id: <5E2A6290-1F7C-4BFE-9CD7-3675FD9CB7B3@monegraph.com>
I have been looking at Exit Criteria [1][2] and Test Cases [3][4] for the Activity Streams and Annotations deliverables (as they are closest to us in terms of having model/vocab documents and “describing/representing” stuff). From what I can tell, the test cases are focussed on the ability to create the correct/valid expression. They don’t go into deep “evaluating” the expression. For example, look at Example 27 here: https://www.w3.org/TR/2016/CR-annotation-model-20160906/#text-position-selector <https://www.w3.org/TR/2016/CR-annotation-model-20160906/#text-position-selector> They express the text position selector (some numbers) but they don’t test if the implementation actually did that. Renato Iannella, Monegraph Co-Chair, W3C Permissions & Obligations Expression (POE) Working Group [1] https://www.w3.org/TR/2016/CR-annotation-model-20160906/#candidate-recommendation-exit-criteria <https://www.w3.org/TR/2016/CR-annotation-model-20160906/#candidate-recommendation-exit-criteria> [2] https://www.w3.org/TR/2016/CR-activitystreams-core-20160906/#exit-criteria <https://www.w3.org/TR/2016/CR-activitystreams-core-20160906/#exit-criteria> [3] https://w3c.github.io/test-results/annotation-model/all.html <https://w3c.github.io/test-results/annotation-model/all.html> [4] https://github.com/w3c/activitystreams/tree/master/test <https://github.com/w3c/activitystreams/tree/master/test>
Received on Friday, 23 June 2017 01:10:31 UTC