[rfc-i] draft-flanagan-rfc-framework-02 composition tools

Joe Hildebrand (jhildebr) jhildebr at cisco.com
Fri Oct 31 08:14:31 PDT 2014


On 10/30/14, 9:15 PM, "Joe Touch" <touch at isi.edu> wrote:

>On 10/30/2014 2:09 PM, Joe Hildebrand (jhildebr) wrote:
>> On 10/30/14, 6:54 PM, "Joe Touch" <touch at isi.edu> wrote:
>> 
>>> I had plans to organize that sort of translator when the dust settled 
>>>on
>>> this new format, time/effort permitting. My fear is that the format has
>>> gone off into esoterica-land in ways that might make it very difficult
>>> to do that translation.
>> 
>> Give one example. Your fear may be based on outdated information.  
>>After 
>> spending a lot of time with v3 in the last several weeks, I don't see 
>>much 
>> that I would trim out that isn't already deprecated.
>
>Give an example of a feature you know would support a translation.
>
>More to the point, give me a feature you know more than 5 people will
>ever use that is worth this exercise, vs using a COTS word processor,
>and then explain how you know that feature won't interfere with such
>translation.

I just wanted to note that your answer-a-question-with-a-question approach 
to distracting the discussion was successful.  I'm going to assume that 
you do not have an example of "esoterica-land" for the moment.

-- 
Joe Hildebrand





More information about the rfc-interest mailing list