- From: Ivan Herman via GitHub <sysbot+gh@w3.org>
- Date: Sat, 24 Sep 2016 04:57:15 +0000
- To: public-annotation@w3.org
@azaroth42, you are right. But that is also a practical reason why the context appendix should stay non-normative. If a (programming...) but appears in the context file on /ns that needs fixing after the Rec is published, then we have the freedom of fixing it, and that is essential because it makes software out there working. That also means that a discrepancy appears between the context file as appears in the document and the 'real' document on /ns. But as everything is informative, that is not a real problem. The situation would become more touchy if the context appendix were normative; in theory, that would imply that one should not change the file on /ns either... Long philosophical discussion ahead:-) which I think we should avoid. Let us keep that informative, in my view... -- GitHub Notification of comment by iherman Please view or discuss this issue at https://github.com/w3c/web-annotation/issues/354#issuecomment-249345437 using your GitHub account
Received on Saturday, 24 September 2016 04:57:23 UTC