- From: Robert Sanderson <azaroth42@gmail.com>
- Date: Tue, 22 Jan 2013 15:04:21 -0700
- To: Antoine Isaac <aisaac@few.vu.nl>
- Cc: public-openannotation <public-openannotation@w3.org>
A few specific questions: > 9. Text normalization > 3.2.2.1 (Text Position selectors) says the text should be normalized before > counting characters. Fine, but: > - is it a SHOULD? > - if yes, could there be a link that tells implementers what kind of > normalization it is? It's really a MUST, or you can't do string comparison. And... is this the right normalization to link to? http://www.w3.org/TR/2004/REC-xml11-20040204/#dt-fullnorm As referenced from: http://www.w3.org/TR/DOM-Level-3-Core/core.html#ID-5DFED1F0 In essence, the right answer is "whatever the browser does before you select the text". Which may be slightly different in different products and implementations, of course :( > 10. Fig 3.3.2 > A specific header request would be really helpful, instead of "headers1". This goes against the abstract examples, but so do the other Selectors. (integer1 would be worse!) > 12. Levels of Scopes > The current proposal where oa:hasScope is attached to specific resources > makes much sense. Cases where there are multiple specific resources and/or > scopes involved in an annotation come to mind... Multiple specific resources with different scopes, but the same source resource?
Received on Tuesday, 22 January 2013 22:04:49 UTC