This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.
RFC 2806 has been obsoleted by RFC 3966, which in particular classifies "fax" as historic. So unless this is a real world example I'd recommend to use either a "tel" URI, or choose a different example.
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: I don't this tel: would make a very good example (what would it mean for a Web site to register the tel: scheme?) but if you have any other suggestions, I'm very happy to change away from fax:. In practice, I think most examples are going to be people inventing new schemes and registering those, but I don't want to use that as an example since people might think it's ok to just make up schemes instead of registering them with IANA first.
If the best example you have is "fax" then maybe this feature isn't needed. On the other hand, wasn't "mailto" (-> gemail & friend) the main use case for this?
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: Partially Accepted Change Description: see diff given below Rationale: After looking at the registry for inspiration, I changed it to use the sms: scheme.
Checked in as WHATWG revision r4777. Check-in comment: fax: is apparently no longer in season. http://html5.org/tools/web-apps-tracker?from=4776&to=4777