[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]


To: "Klaus Malorny" <Klaus.Malorny@knipp.de>
Cc: "EPP Provreg" <ietf-provreg@cafax.se>
From: "Hollenbeck, Scott" <shollenbeck@verisign.com>
Date: Thu, 5 Nov 2009 07:16:55 -0500
Content-class: urn:content-classes:message
In-Reply-To: <4AF1E51A.90703@knipp.de>
Sender: owner-ietf-provreg@cafax.se
thread-index: AcpdjhdWpdLsvXpuSYyri+490u0OwgAgfavA
Thread-Topic: [ietf-provreg] Anyone working on 4310-bis?
Subject: RE: [ietf-provreg] Anyone working on 4310-bis?

> -----Original Message-----
> From: Klaus Malorny [mailto:Klaus.Malorny@knipp.de] 
> Sent: Wednesday, November 04, 2009 3:34 PM
> To: Hollenbeck, Scott
> Cc: Andrew Sullivan; EPP Provreg
> Subject: Re: [ietf-provreg] Anyone working on 4310-bis?
> 
> On 04/11/09 21:05, Hollenbeck, Scott wrote:
> 
> > Section 2 of 5730 very clearly states that "Commands are 
> processed by 
> > a server in the order they are received from a client."  If 
> an<add>  
> > is received before a<rem>  it should be processed first.
> >
> > Scott
> >
> 
> Hi Scott,
> 
> up to now I interpreted the term "command" in this sentence 
> in respect to the "epp:commandType" in the 
> "urn:ietf:params:xml:ns:epp-1.0" name space as an atomic 
> piece of work. The definition as low level sequences of 
> characters forming text contents, attributes, elements, 
> comments, processing instructions and so on, representing 
> individual tiny commands within the big one, is a fairly new 
> and dubious concept to me, especially as the XML infoset[1] 
> does not regard the order of attributes in the document as 
> relevant and parsers and generators are free to change it.
> 
> But thanks for clarification.
> 
> Regards,
> 
> Klaus
> 
> 
> [1] http://www.w3.org/TR/xml-infoset Appendix D, 10.

I'm referring to XML command structures for which an order can be
explicitly specified, such as elements within a sequence.  It's
certainly not a new concept because the specifications have been this
way since the very beginning (the same quote can be found in RFC 3730
from 2004). If the order wasn't intended to be significant I wouldn't
have used sequences.

Scott

-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
List run by majordomo software.  For (Un-)subscription and similar details
send "help" to ietf-provreg-request@cafax.se


Home | Date list | Subject list