Hi Tim, On Sat, Oct 17, 2009 at 9:48 PM, Tim Bray <[email protected]> wrote: > > Draft says "MAY use HTTP or HTTPS schemes. These URLs MAY have port > numbers specified; however, hubs MAY choose to disallow certain ports > based on their own policies (e.g., security) and return errors for > these requests. The topic URL can otherwise be free-form following the > URI spec". > > Do you mean MUST, i.e. topic/callback have to be either "http:" or > "https:"? I think so. If so, the "MAY" is confusing. I'm not sure > the section about port number helps... hubs could apply all sorts of > weird policies based on one part or another of the URI. You could > maybe shorten this whole section without loss of value by saying > something like: "The topic and anchor values MUST be URIs [RFC3986] > and MUST use either the "http:" or "https:" URI schemes. They MUST > NOT contain anchor fragments."
We're calling out port numbers specifically here because of some other questions that people have raised over time about specifically that issue. Otherwise, it's MAY instead of MUST so in the future a hub could support an XMPP URI as their callback address if they wanted to (need another companion spec for that, but we should leave room here). Maybe there's a better way to phrase it with that future in mind? Thanks, -Brett
