Lists Home |
Date Index |
It probably is. There are those who think
declaring an xsd:list saves them from the
fact that it is just whitespace delimited
CDATA. In a sense, some don't quite get it
that Schemas and DTDs are instructions to
application processors, not parsers, and
even then, don't declare the delimiters
inside the attributes. One might want to
but at the end of the day, a list inside an
attribute where the content of a list member
includes whitespace is back to ugly syntax
hacking in the instance.
From: Jason Diamond [mailto:firstname.lastname@example.org]
On Friday, June 13, 2003, at 06:26 AM, Bullard, Claude L (Len) wrote:
> But considering that filenames can have
> spaces in them in both MS and Unix operating
> systems, other than stuffing %20 in the strings,
> that is a likely solution.
If you have to stick them in attributes, URL-escaping seems like the
best solution to me. It's easily describable with WXS and you have
precedence: xsi:schemaLocation. Think of your attribute as containing a
list of URIs, relative in this case.
> Other than
> what are better solutions?
That is the better solution, isn't it?