Re: Whitespace

I'll agree with Brian too and add, to Christian's comment, that to control
whitespace treatment in the content an app could do the following, for
example, with an enveloping child element.

Perhaps this may be the best solution regardless of our time constraints.
(Note
that whitespace outside the envelope is not controllable the xml:space
attribute
but this may be OK.)

<ds:Object>
<custom:Envelope  xml:space="preserve>
<custom:Elem1> ... </custom:Elem1>
<custom:Elem2 xml:space="default"> ... </custom:Elem2>
</custom:Envelope>
</ds:Object>

Ed

----- Original Message -----
From: "Christian Geuer-Pollmann" <geuer-pollmann@nue.et-inf.uni-siegen.de>
To: "Brian LaMacchia" <bal@microsoft.com>; <reagle@w3.org>
Cc: <w3c-ietf-xmldsig@w3.org>
Sent: Saturday, January 12, 2002 6:54 AM
Subject: RE: Whitespace


> --On Freitag, 11. Januar 2002 17:30 -0800 Brian LaMacchia
> <bal@microsoft.com> wrote:
>
> > 3) If we were going to put the attribute anywhere, then I believe
> > Joseph's comment is correct that it would be more appropriate for the
> > attribute to go on ext:Foo.  (Notice that since dsig:Object does not
> > itself have any significant semantic beyond a mere container, it is the
> > case that in fact doing it this way (on ext:foo) is fully equivalently
> > expressive.)
>
> I agree with Brian about that this is a good solution if the schema is
> _not_ tweaked.
>
> I am no schema crack, but if the dsig schema cannot be overwritten in a
way
> that an application re-defined a ds:Object to contain only Elements (so
> that xml:space would be important for direct ds:Object/text() children,
> then the application developer can put the xml:space='preserve' into every
> element child of the ds:Object:
>
> <ds:Object>
> <custom:Elem1 xml:space="preserve"> ... </custom:Elem1>
>
>      <custom:Elem2 xml:space="preserve"> ... </custom:Elem2>
> </ds:Object>
>
>
>
>
>