Re: Fwd: Last Call: 'Atom Threading Extensions' to Proposed Standard (draft-snell-atompub-feed-thread)
James M Snell <jasnell@gmail.com> Thu, 18 May 2006 17:47 UTC
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1FgmaZ-0001Cq-6T; Thu, 18 May 2006 13:47:07 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1FgWrV-00087e-Iu for discuss@apps.ietf.org; Wed, 17 May 2006 20:59:33 -0400
Received: from wr-out-0506.google.com ([64.233.184.233]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1FgWrT-0006Su-B8 for discuss@apps.ietf.org; Wed, 17 May 2006 20:59:33 -0400
Received: by wr-out-0506.google.com with SMTP id i12so326497wra for <discuss@apps.ietf.org>; Wed, 17 May 2006 17:59:30 -0700 (PDT)
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:user-agent:mime-version:to:cc:subject:references:in-reply-to:content-type:content-transfer-encoding; b=E2//mkDySf1RQDUIbKb2K7Cn27QmAKQi6WnikGUls6DFOmaLD70fjn01CTeQsHymDnv9d9CIQ6e6GZJe/TUJKCTHh0Lmhio9mZX2+ZAvLTjTLaxl9BaVCDRpF83OoSDyaHeWx6scI8EtXaK85hUuNfbPunmyOS25K2G0s4/ehDo=
Received: by 10.54.134.15 with SMTP id h15mr3150049wrd; Wed, 17 May 2006 17:59:30 -0700 (PDT)
Received: from ?192.168.1.104? ( [67.181.218.96]) by mx.gmail.com with ESMTP id g3sm216201wra.2006.05.17.17.59.29; Wed, 17 May 2006 17:59:30 -0700 (PDT)
Message-ID: <446BC6EE.9000902@gmail.com>
Date: Wed, 17 May 2006 17:59:26 -0700
From: James M Snell <jasnell@gmail.com>
User-Agent: Thunderbird 1.5.0.2 (X11/20060420)
MIME-Version: 1.0
To: Ned Freed <ned.freed@mrochek.com>
Subject: Re: Fwd: Last Call: 'Atom Threading Extensions' to Proposed Standard (draft-snell-atompub-feed-thread)
References: <01M2JCJVC2TG0008CX@mauve.mrochek.com>
In-Reply-To: <01M2JCJVC2TG0008CX@mauve.mrochek.com>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: 7bit
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 0ddefe323dd869ab027dbfff7eff0465
X-Mailman-Approved-At: Thu, 18 May 2006 13:47:05 -0400
Cc: discuss@apps.ietf.org, atom-protocol@imc.org, xml-dir@ietf.org
X-BeenThere: discuss@apps.ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: general discussion of application-layer protocols <discuss.apps.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/discuss>, <mailto:discuss-request@apps.ietf.org?subject=unsubscribe>
List-Post: <mailto:discuss@apps.ietf.org>
List-Help: <mailto:discuss-request@apps.ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/discuss>, <mailto:discuss-request@apps.ietf.org?subject=subscribe>
Errors-To: discuss-bounces@apps.ietf.org
Ned Freed wrote: >> FYI -- this is an individual submission yet intended for Proposed >> Standard, so input is most welcome. > > I have a couple of comments, all minor. > Thank you for taking the time. >[snip] > The "in-reply-to" element is used to indicate that an entry is a > response to another resource. The element MUST contain either or both the > "ref" and "href" attributes. > Yes, this makes sense. Also, I am changing this definition making ref required in all cases. > Now, I have a lot more experience with XML Schema than with Relax NG so > maybe I'm reading this wrong, but the Relax NG definition seems to say > that the source attribute can only appear when the ref attribute is present > and the type attribute can only appear when the href attribute is present. > But this isn't spelled out in the (normative) text. How about adding > "When the ref attribute is present" before "The 'source' attribute ..." and > "When the href attribute is present" before "The 'type' attribute ..."? > Yes. I'll make the change. > Finally, the document seems a bit short on specifics of how the > in-reply-to element is actually used. Although the underlying semantic > model here seems to be simpler than email's in-reply-to/references scheme > (a good thing IMO), perhaps some words about whether you need to list just > the parent(s) and not the grandparent(s) would be in order. There > were certainly differences of opinion about this in the days of RFC 822 > which RFC 2822 section 3.6.4 cleared up. > I will take another look at 2822 and see if I can strike the right balance. > That's it! > Thanks again. > Ned > >
- Fwd: Last Call: 'Atom Threading Extensions' to Pr… Lisa Dusseault
- Re: Fwd: Last Call: 'Atom Threading Extensions' t… Ned Freed
- Re: Fwd: Last Call: 'Atom Threading Extensions' t… James M Snell
- Re: [xml-dir] Re: Fwd: Last Call: 'Atom Threading… Ned Freed