10556 2010-09-06 13:54:56 +0000 Document tells people to register canvas context types at WhatWG 2010-10-04 14:45:50 +0000 1 1 1 Unclassified HTML WG pre-LC1 HTML5 spec (editor: Ian Hickson) unspecified Macintosh Mac System 9.x RESOLVED NEEDSINFO NE P3 normal --- 1 shelleyp ian ian julian.reschke kornel mike public-html-admin public-html-wg-issue-tracking shelleyp public-html-bugzilla oldest_to_newest 38483 0 shelleyp 2010-09-06 13:54:56 +0000 The Canvas section in the document has a link to the WhatWG wiki in order to "register" new context types. The problem with this is that the WhatWG web site is a personal web site maintained by one person (Ian Hickson), owned by one person (Ian Hickson), with no formal structure, or guarantee of reliability. In fact, reliability of the web site has been a problem in the past, as it is based in Dreamhost, a host notorious for interruptions of service. Secondly, there is no mechanism in place to ensure the security of the data, nor to deal with conflicts if any arise. A wiki is no place on which to build a standard. Only a neophyte would consider a wiki a good place to order to register _anything_ so that all application builders can rely on what's registered. Lastly, the W3C document should not contain any link to WhatWG documents, because the WhatWG is not a formal organization, with legal structure, or patent policy in place. Without a formal organization backing the site, there is no guarantee that any links will continue point to any one document in the future -- for all we know, the WhatWG web site could be bought by spammers someday and the linked document then becomes a page of ads for herbal supplements. Even if the WhatWG domain remains, there is no guarantee that the sole owner of the web site won't change the contents of documents in such a way as to cause confusion or even disruption. 38484 1 kornel 2010-09-06 14:16:04 +0000 I've grepped spec document and found links to domains that might be in similar situation: microformats.org, opensearch.org, publicsuffix.org, keithp.com. Would you like these links removed as well? 38485 2 shelleyp 2010-09-06 14:26:26 +0000 (In reply to comment #1) > I've grepped spec document and found links to domains that might be in similar > situation: microformats.org, opensearch.org, publicsuffix.org, keithp.com. > > Would you like these links removed as well? Depends on the context of the usage. Where in the document are these links? Were these links to wiki pages where one is instructed to register types? 38486 3 shelleyp 2010-09-06 14:32:43 +0000 (In reply to comment #1) > I've grepped spec document and found links to domains that might be in similar > situation: microformats.org, opensearch.org, publicsuffix.org, keithp.com. > > Would you like these links removed as well? And were the links to pages that already exist among the W3C HTML WG documents? 38487 4 julian.reschke 2010-09-06 14:49:31 +0000 (In reply to comment #1) > I've grepped spec document and found links to domains that might be in similar > situation: microformats.org, opensearch.org, publicsuffix.org, keithp.com. > > Would you like these links removed as well? - microformats.org only appears in a comment - opensearch.org is a note, which should be harmless - publicsuffix.org probably needs to be discussed (I think the cookie spec has a similar need and currently only cites it as example) - keithp.com -- I don't see that in the spec 38629 5 ian 2010-09-08 08:22:18 +0000 I just used the WHATWG wiki because doing so was easy and solved the problem. If anyone has a better idea, I'm all for it. I don't think stability is a worry, though. If the server went down, or I went nuts and started changing it in ways incompatible with reality, or something like that, the community could just move it elsewhere and update the spec. Anyway, if anyone has an idea of a good place to host this list of context names that is freely editable by anyone and who would be happy to host this, let me know and I'll be happy to update the spec. EDITOR'S RESPONSE: This is an Editor's Response to your comment. If you are satisfied with this response, please change the state of this bug to CLOSED. If you have additional information and would like the editor to reconsider, please reopen this bug. If you would like to escalate the issue to the full HTML Working Group, please add the TrackerRequest keyword to this bug, and suggest title and text for the tracker issue; or you may create a tracker issue yourself, if you are able to do so. For more details, see this document: http://dev.w3.org/html5/decision-policy/decision-policy.html Status: Did Not Understand Request Change Description: no spec change Rationale: No suitable alternative is apparent; suggestions welcome. 38661 6 shelleyp 2010-09-08 12:24:23 +0000 (In reply to comment #5) > I just used the WHATWG wiki because doing so was easy and solved the problem. > If anyone has a better idea, I'm all for it. I don't think stability is a > worry, though. If the server went down, or I went nuts and started changing it > in ways incompatible with reality, or something like that, the community could > just move it elsewhere and update the spec. > > Anyway, if anyone has an idea of a good place to host this list of context > names that is freely editable by anyone and who would be happy to host this, > let me know and I'll be happy to update the spec. > > > EDITOR'S RESPONSE: This is an Editor's Response to your comment. If you are > satisfied with this response, please change the state of this bug to CLOSED. If > you have additional information and would like the editor to reconsider, please > reopen this bug. If you would like to escalate the issue to the full HTML > Working Group, please add the TrackerRequest keyword to this bug, and suggest > title and text for the tracker issue; or you may create a tracker issue > yourself, if you are able to do so. For more details, see this document: > http://dev.w3.org/html5/decision-policy/decision-policy.html > > Status: Did Not Understand Request > Change Description: no spec change > Rationale: No suitable alternative is apparent; suggestions welcome. Did you discuss this in the HTML WG?