- From: Mark Nottingham <mnot@mnot.net>
- Date: Thu, 9 Jul 2009 17:43:17 +1000
- To: Ian Hickson <ian@hixie.ch>
- Cc: Julian Reschke <julian.reschke@gmx.de>, Adam Barth <w3c@adambarth.com>, collinj@cs.stanford.edu, HTTP Working Group <ietf-http-wg@w3.org>
Try defining new terms to be unique and distinguished; hyphenation comes in handy for this (e.g., origin-URI, host-value, port-value). Explicitly importing (A)BNF terms from other specs and defining new ones helps distinguish them as well; however, it looks like most of this spec is defining an abstract model, not syntax (I wonder if it could be refactored that way, however). I agree it's not an ideal situation. Cheers, On 09/07/2009, at 5:33 PM, Ian Hickson wrote: > On Thu, 9 Jul 2009, Julian Reschke wrote: >> Ian Hickson wrote: >>> On Thu, 9 Jul 2009, Julian Reschke wrote: >>>> No, there is no standard way in IETF documents to do so. As far >>>> as I can >>>> tell, decorating terms with "_" or "/" is uncommon and is >>>> unlikely to be >>>> accepted by the RFC Editor. >>> >>> What should we do instead? >> >> Write the text in a way that it's understandable without decorations. > > I originally did, but then I had to convert it to plain text. :-( > > Oh well. > > -- > Ian Hickson U+1047E ) > \._.,--....,'``. fL > http://ln.hixie.ch/ U+263A /, _.. \ _ > \ ;`._ ,. > Things that are impossible just take longer. `._.-(,_..'-- > (,_..'`-.;.' -- Mark Nottingham http://www.mnot.net/
Received on Thursday, 9 July 2009 07:43:57 UTC