To:
"Hollenbeck, Scott" <shollenbeck@verisign.com>
Cc:
EPP Provreg <ietf-provreg@cafax.se>
From:
Andrew Sullivan <ajs@shinkuro.com>
Date:
Fri, 30 Oct 2009 11:57:44 -0400
Content-Disposition:
inline
In-Reply-To:
<046F43A8D79C794FA4733814869CDF0702ECDE6B@dul1wnexmb01.vcorp.ad.vrsn.com>
Mail-Followup-To:
Andrew Sullivan <ajs@shinkuro.com>,"Hollenbeck, Scott" <shollenbeck@verisign.com>,EPP Provreg <ietf-provreg@cafax.se>
Sender:
owner-ietf-provreg@cafax.se
User-Agent:
Mutt/1.5.18 (2008-05-17)
Subject:
Re: [ietf-provreg] Anyone working on 4310-bis?
On Fri, Oct 30, 2009 at 11:37:38AM -0400, Hollenbeck, Scott wrote: > The answer to this question is implicit in the understanding of how XML > Schema works. Aha, well, this is obviously where I fell down. > If the <choice> is changed to a <sequence>, the order will be specified > in the schema. If you don't want the order to matter, use <all>. I > would like to suggest that a sequence makes more sense if you want to > avoid issues related to processing order. Ok, cool. This is terribly helpful. Expect the next iteration to include this strategy, then. Thanks! A -- Andrew Sullivan ajs@shinkuro.com Shinkuro, Inc. -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- List run by majordomo software. For (Un-)subscription and similar details send "help" to ietf-provreg-request@cafax.se