[mmox] xxSD XML serialization

Catherine Pfeffer <cathypfeffer@gmail.com> Tue, 24 February 2009 15:10 UTC

DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:date:message-id:subject:from:to:content-type; b=Ye+P2qRTWa78cc8GIz6xdCx/YCjfYI9haRK2pKP+3PDubE8EOjPfTsCjw4p3oDMvzx umyY+q4FWgVZ9hUE9kHxtOS22RRKMl1coyUNfGHG2El7Zemx3iHHrhk0X+8PgeLaPtud nr1qBbWC7jut+xKx5AW0EOky4lQm5R7fhfUZU=
MIME-Version: 1.0
Date: Tue, 24 Feb 2009 16:10:47 +0100
Message-ID: <ebe4d1860902240710m59f0cc86oed80e575e110bc2e@mail.gmail.com>
From: Catherine Pfeffer <cathypfeffer@gmail.com>
To: mmox@ietf.org
Content-Type: multipart/alternative; boundary="0015174be6ea1a9ea90463ab869d"
Subject: [mmox] xxSD XML serialization
Precedence: list

Zero wrote:
> Jon Watte wrote:
> > <map>
> > <value type="boolean" key="success>true</value>
> > <value type="string"
> > key="something_i_like_to_eat_on_sundays">bananas</value>
> > </map>
>
> This format is notably more difficult for schemas (from XMLSchema to
> RelaxNG) to support, since value now has a key attribute that is only
> valid if it is tested in a map element.

Yes. Jon should have named it "entry" and not "value", so it would have been
clear that it can appear only in a map.

Moving the data type to a "type" attribute could be generalized outside of a
map for all values. That's a separate problem that raises its own concerns,
and also has advantages, which I have discussed in my previous mail.

(Side note: both XML schema and Relax NG have provisions for
context-dependant validation, expressed in "Russian doll" style. So it would
not be that difficult. It would only be ugly from a conceptual point of
view...)

>  Second, you have left out
> the top element, which needs to be something fixed, rather than being
> map or array or value depending on the structure of the data.

Omitting <llsd> was probably just a way for Jon to get quickly to the point.

-- 
Cathy

[mmox] xxSD XML serialization Catherine Pfeffer