Remove un-implemented List, Composite, Independents

w3c / web-annotation

Web Annotation Working Group repository, see README for links to specs

https://w3c.github.io/web-annotation/

Other

142 stars 30 forks source link

Closed azaroth42 closed 7 years ago

azaroth42 commented 7 years ago

In order to exit CR, we need to remove List, Composite and Independents as they are not implemented in any product.

If there isn't an implementation using them today, we need to take them out. If there is, then we need to get them tested and into the report.

If there's no implementation before 11/11/2016, they will be removed.

azaroth42 commented 7 years ago

iherman commented 7 years ago

Having checked with the director:

it is all right to put unimplemented, but at-risk features into an informative appendix, while remove it from the main spec
however, if a feature that was not identified as 'at risk' does not get through the exit criteria, then it should be removed (and may be put into the appendix) but, formally, a new CR should be published (albeit with a short short cycle) before going to Proposed Rec

As discussed on a call, that means that two documented implementations of 'Choice' would be necessary to go the Proposed Rec directly...

azaroth42 commented 7 years ago

Extended to include removal of Creator and Choice for Targets, and bodyValue property of the Annotation, lacking implementations.

iherman commented 7 years ago

With the publication of 3rd CR (22nd of November), this issue is now closed.