Re: [url] Why is Hosts not a separate section? (#9)

> I don't understand. Host parsing was never duplicated.

I was unclear.  When I replaced step 8 (and inadvertently step 9... oops) of https://url.spec.whatwg.org/#concept-basic-url-parser, I was left with duplication.  When I eliminated the duplication in favor of my new work, I was left with sections that were gutted.  When I rearranged, I ended up with what you see.  I must say that I like the fact that where I ended up, the specification named "URL" starts out with a definition of that term.  I'd like to keep that.

> The main reason I think hosts deserves to be its own section is because it's something that is used independently from the rest of the URL parser and I don't want specifications to build on any random part of the URL parser, just sanctioned bits.

The operative question here is what do we sanction, not how do we arrange the text in the specification.  If somebody wants to build on this specification and they need hooks or IDL or whatever, we will deal with those requests when they occur.

> Having hosts separately and having a place to put all definitions around hosts, including certificate stuff eventually about how to match *.html5.org (x.x.html5.org is not a match) seems like a win.

Perhaps ultimately hosts should be split out to a separate specification.  I'd be fine with that should we come to that point.  Meanwhile, is there anybody actively working on definitions for certificate stuff and the like?  Again, we should deal with those requests when they occur.


---
Reply to this email directly or view it on GitHub:
https://github.com/webspecs/url/issues/9#issuecomment-66624204