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

After I did the initial merge, there was much duplication.  As a concrete example, much of the definition of hosts dealt with parsing, and that was covered by the parsing rules.  So I guess another way to look at the question you raise: does it make sense to split the parsing rules and distribute them into multiple sections, or does it make sense to consolidate them?  For that matter, should hosts be split out into a separate standard?

My preference is that the parsing rules stay together, though this could be broken out into a separate section.  I have a similar preference for a consolidated authoring/writing/conformance instructions.  As to host APIs, that could be a new section if/when it is needed, much like URL APIs currently is a separate section.

For reference, here is the relevant sequence of commits:

 * https://github.com/webspecs/url/commit/3967bb2a12653b01b2cfb87d779bbcd1d6d71d59
 * https://github.com/webspecs/url/commit/9e0cc156451770794e7eedbc0d9f45055aedd66f
 * https://github.com/webspecs/url/commit/f016c47c665bf1cf3b22e807a4f70946319b4142
 * https://github.com/webspecs/url/commit/1e3d3e6da57119e0be86175f21cd3476901cb873

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