- From: gsergiu via GitHub <sysbot+gh@w3.org>
- Date: Mon, 18 Jan 2016 08:54:19 +0000
- To: public-annotation@w3.org
That is an option. My main concern here was the understanding of the text. If I understood correctly, than one of the specific attributes: State, Selector, Style, Scope, Role is mandatory for SpecifcResources. If that is the case, I would recommend to make this mroe explicit in the text. Even if that will be in the form of a "(Development) Note". Maybe it is not a bad idea to add also a "role" (purpose) to the example. In this case it would be ok to have "role" and "selector" in the example as the next two sections explain these properties. We can introduce references to the related sections in the introductory text. For me the following text looks like an summary of the section 4 ... (and I would place references on the State, Selector, Style, Scope, Role). The types of additional specificity that are available: State: Describe the desired representation of the source resource for the Annotation Selector: Describe the desired segment of the source resource for the Annotation Style: Describe the style in which the source resource should be presented for the Annotation Scope: Describe the scope in which the source resource applies for the Annotation Role: Describe the role that the source resource plays for the Annotation Sounds this like a good solution? -- GitHub Notification of comment by gsergiu Please view or discuss this issue at https://github.com/w3c/web-annotation/issues/138#issuecomment-172466640 using your GitHub account
Received on Monday, 18 January 2016 08:54:21 UTC