Hello David, At 02:52 06/09/21, David Conrad wrote: >Internally, we use subversion for version control. It would be >relatively straight forward for us to provide an opt-in mailing list >that broadcasts the contextual diffs of any registry update. We can, >of course, also look at other alternatives people might suggest. If you use subversion internally already, the best way to allow differential updates would be to make subversion available publicly. I understand that it would have to be considered carefully, but it's really the protocol designed for the job. Also, as an alternative to mail broadcasts, I'd suggest using Atom (RFC 4287). Regards, Martin. #-#-# Martin J. Du"rst, Assoc. Professor, Aoyama Gakuin University #-#-# http://www.sw.it.aoyama.ac.jp mailto:duerst at it.aoyama.ac.jp _______________________________________________ Ltru mailing list Ltru at ietf.org https://www1.ietf.org/mailman/listinfo/ltru t) with SMTP id k8L9tF35023420 for <ltru at ietf.org>; Thu, 21 Sep 2006 18:55:15 +0900 (JST) Received: from (133.2.206.133) by scmse1.scbb.aoyama.ac.jp via smtp id 2a9c_48004e78_4957_11db_92f9_0014221fa3c9; Thu, 21 Sep 2006 18:55:15 +0900 X-AuthUser: duerst at it.aoyama.ac.jp Received: from Tanzawa.it.aoyama.ac.jp ([133.2.210.1]:54217) by itmail.it.aoyama.ac.jp with [XMail 1.22 ESMTP Server] id <S25761> for <ltru at ietf.org> from <duerst at it.aoyama.ac.jp>; Thu, 21 Sep 2006 18:55:17 +0900 Message-Id: <6.0.0.20.2.20060921182425.09d3a8b0 at localhost> X-Sender: duerst at localhost X-Mailer: QUALCOMM Windows Eudora Version 6J Date: Thu, 21 Sep 2006 18:28:23 +0900 To: David Conrad <david.conrad at icann.org>, John Cowan <cowan at ccil.org> From: Martin Duerst <duerst at it.aoyama.ac.jp> Subject: Re: [Ltru] IANA XML registries In-Reply-To: <B075B981-DD81-4C58-AE81-90A55A08DFE9 at icann.org> References: <4AA29C10-63B3-465D-9A6E-D7C02C72C07C at icann.org> <7.0.1.0.2.20060920140342.036d4e48 at afrac.org> <0E361BCA-5B26-4937-B760-68CD002C2EA6 at icann.org> <20060920164622.GF15905 at ccil.org> <B075B981-DD81-4C58-AE81-90A55A08DFE9 at icann.org> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit X-Spam-Score: 0.0 (/) X-Scan-Signature: 9182cfff02fae4f1b6e9349e01d62f32 Cc: ltru at ietf.org X-BeenThere: ltru at ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Language Tag Registry Update working group discussion list <ltru.ietf.org> List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ltru>, <mailto:ltru-request at ietf.org?subject=unsubscribe> List-Archive: <http://www1.ietf.org/pipermail/ltru> List-Post: <mailto:ltru at ietf.org> List-Help: <mailto:ltru-request at ietf.org?subject=help> List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ltru>, <mailto:ltru-request at ietf.org?subject=subscribe> Errors-To: ltru-bounces at ietf.org Hello David, At 02:52 06/09/21, David Conrad wrote: >Internally, we use subversion for version control. It would be >relatively straight forward for us to provide an opt-in mailing list >that broadcasts the contextual diffs of any registry update. We can, >of course, also look at other alternatives people might suggest. If you use subversion internally already, the best way to allow differential updates would be to make subversion available publicly. I understand that it would have to be considered carefully, but it's really the protocol designed for the job. Also, as an alternative to mail broadcasts, I'd suggest using Atom (RFC 4287). Regards, Martin. #-#-# Martin J. Du"rst, Assoc. Professor, Aoyama Gakuin University #-#-# http://www.sw.it.aoyama.ac.jp mailto:duerst at it.aoyama.ac.jp _______________________________________________ Ltru mailing list Ltru at ietf.org https://www1.ietf.org/mailman/listinfo/ltru t) with SMTP id k8L9tF35023420 for <ltru at ietf.org>; Thu, 21 Sep 2006 18:55:15 +0900 (JST) Received: from (133.2.206.133) by scmse1.scbb.aoyama.ac.jp via smtp id 2a9c_48004e78_4957_11db_92f9_0014221fa3c9; Thu, 21 Sep 2006 18:55:15 +0900 X-AuthUser: duerst at it.aoyama.ac.jp Received: from Tanzawa.it.aoyama.ac.jp ([133.2.210.1]:54217) by itmail.it.aoyama.ac.jp with [XMail 1.22 ESMTP Server] id <S25761> for <ltru at ietf.org> from <duerst at it.aoyama.ac.jp>; Thu, 21 Sep 2006 18:55:17 +0900 Message-Id: <6.0.0.20.2.20060921182425.09d3a8b0 at localhost> X-Sender: duerst at localhost X-Mailer: QUALCOMM Windows Eudora Version 6J Date: Thu, 21 Sep 2006 18:28:23 +0900 To: David Conrad <david.conrad at icann.org>, John Cowan <cowan at ccil.org> From: Martin Duerst <duerst at it.aoyama.ac.jp> Subject: Re: [Ltru] IANA XML registries In-Reply-To: <B075B981-DD81-4C58-AE81-90A55A08DFE9 at icann.org> References: <4AA29C10-63B3-465D-9A6E-D7C02C72C07C at icann.org> <7.0.1.0.2.20060920140342.036d4e48 at afrac.org> <0E361BCA-5B26-4937-B760-68CD002C2EA6 at icann.org> <20060920164622.GF15905 at ccil.org> <B075B981-DD81-4C58-AE81-90A55A08DFE9 at icann.org> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit X-Spam-Score: 0.0 (/) X-Scan-Signature: 9182cfff02fae4f1b6e9349e01d62f32 Cc: ltru at ietf.org X-BeenThere: ltru at ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Language Tag Registry Update working group discussion list <ltru.ietf.org> List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ltru>, <mailto:ltru-request at ietf.org?subject=unsubscribe> List-Archive: <http://www1.ietf.org/pipermail/ltru> List-Post: <mailto:ltru at ietf.org> List-Help: <mailto:ltru-request at ietf.org?subject=help> List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ltru>, <mailto:ltru-request at ietf.org?subject=subscribe> Errors-To: ltru-bounces at ietf.org Hello David, At 02:52 06/09/21, David Conrad wrote: >Internally, we use subversion for version control. It would be >relatively straight forward for us to provide an opt-in mailing list >that broadcasts the contextual diffs of any registry update. We can, >of course, also look at other alternatives people might suggest. If you use subversion internally already, the best way to allow differential updates would be to make subversion available publicly. I understand that it would have to be considered carefully, but it's really the protocol designed for the job. Also, as an alternative to mail broadcasts, I'd suggest using Atom (RFC 4287). Regards, Martin. #-#-# Martin J. Du"rst, Assoc. Professor, Aoyama Gakuin University #-#-# http://www.sw.it.aoyama.ac.jp mailto:duerst at it.aoyama.ac.jp _______________________________________________ Ltru mailing list Ltru at ietf.org https://www1.ietf.org/mailman/listinfo/ltru
Note Well: Messages sent to this mailing list are the opinions of the senders and do not imply endorsement by the IETF.