(This is the last mail in this series:-) I have run into some statements in the document that are in the text without real justification. I may or may not agree with those but, in any case, a reason should be given. • Section 3.1. "The Annotation class MUST be associated with an Annotation using @type." Why MUST? This may be the only place where associating a type is a MUST. Personally, a SHOULD ought to be enough. • Section 4.2.1. "It is RECOMMENDED to use FragmentSelector as a consistent method compatible with other means of describing SpecificResources, rather than using the Fragment URI directly. " Why? • Section 5.3. "The option of having a simple string literal for the body is not possible when using Multiplicity constructs, and the embedded textual body resource pattern must be used." Why? A list can have a mixture of objects and literals… Ivan ---- Ivan Herman, W3C Digital Publishing Lead Home: http://www.w3.org/People/Ivan/ mobile: +31-641044153 ORCID ID: http://orcid.org/0000-0003-0782-2704
Received on Friday, 16 October 2015 11:54:30 UTC