- From: EnnexMB <notifications@github.com>
- Date: Mon, 08 Oct 2018 05:59:43 -0700
- To: whatwg/url <url@noreply.github.com>
- Cc: Subscribed <subscribed@noreply.github.com>
- Message-ID: <whatwg/url/issues/337/427821179@github.com>
Thanks @annevk. In your answer 1, it sounds like you're saying that the terminologies are synonymous. Therefore, the diagram I first [posted above](https://github.com/whatwg/url/issues/337#issuecomment-421627310) can be made bilingual by inserting the corresponding API terms in brackets below the non-API terms where they are different, as follows: ![url syntax with api tems](https://user-images.githubusercontent.com/40837471/46608770-7e3e8b00-cacb-11e8-830a-b34b4f9d56ee.png) This diagram has the problems already discussed above and is only used here to show the presentation of API terminology alongside the non-API terminology where they are different. I have taken the API terms from @TimothyGu's original postings ([first](https://github.com/whatwg/url/issues/337#issuecomment-327053468) and [second](https://github.com/whatwg/url/issues/337#issuecomment-327103388)) in this issue. @rubys, does this resolve your concern about the terminology? Can we move forward with developing the correct syntax diagrams in this way? @annevk, in your answer 2, is the view of the URL Standard authoritative, or is there some competing body that could disagree with you? If this view is authoritative, then I could propose that _Wikipedia_ state that the term "URI" is depricated and when we finish the syntax diagram here, that should be posted on _Wikipedia_ in the URL article with reference to the new diagram in the URL Standard. -- You are receiving this because you are subscribed to this thread. Reply to this email directly or view it on GitHub: https://github.com/whatwg/url/issues/337#issuecomment-427821179
Received on Monday, 8 October 2018 13:00:07 UTC