Mailing-List: contact deltacloud-dev-help@incubator.apache.org; run by ezmlm
Precedence: bulk
Reply-To: deltacloud-dev@incubator.apache.org
Received-SPF: pass (nike.apache.org: domain of lutter@redhat.com designates
 209.132.183.28 as permitted sender)
Subject: Re: Model layer for CIMI
From: David Lutterkort <lutter@redhat.com>
To: deltacloud-dev@incubator.apache.org
Date: Thu, 10 Nov 2011 10:55:13 -0800
In-Reply-To: 
 <OF581BEB27.272867A0-ON85257944.0049FF17-85257944.004ABC4A@us.ibm.com>
References: <1320873504-27543-1-git-send-email-lutter@redhat.com>
	 <OF581BEB27.272867A0-ON85257944.0049FF17-85257944.004ABC4A@us.ibm.com>
Organization: Red Hat Inc
Content-Type: text/plain; charset="ISO-8859-15"
Content-Transfer-Encoding: 7bit
Message-ID: <1320951314.29766.3.camel@melon.watzmann.net>
Mime-Version: 1.0

On Thu, 2011-11-10 at 08:36 -0500, Tong Li wrote:
> I do not think DMTF cimi spec strongly suggested the sequence of the
> elements. At least it did not say in the spec. although most of the samples
> do show a patten of the elements.

That's one of the implicit rules of XML: order matters, DOM's are
ordered trees etc.

>  When I used XmlSimple (), it actually
> keeps the right order with the xml it reads in. The difficulty is when you
> have a hash (produced by XmlSimple from an XML doc), you most likely will
> add or remove things off of the hash, that is where it sequence really get
> messed up, I do not consider it has anything to do with the XmlSimple, it
> is just when hash get serialized to xml or json, probably the serializer
> does not know how to deal with the sequence since the hash certainly does
> not have the sequence information of its members.

Either way, we'll have to write our own XML serialization to make sure
element order is correct; the schema that is declared with the DSL has
the element order (the order in which attributes are declared)

David