Mark Lambert wrote:
> Another strange thing I noticed with XML Schema validation: if you
> define an archetype with content="mixed", then in the absence of any
> archetype ordeing attribute, the elements can appear in any order in
> instances of that archetype. But if you define the archetype with
Another strange thing I noticed with XML Schema validation: if
you define an archetype with content="mixed", then in the absence of any
archetype ordeing attribute, the elements can appear in any order in instances
of that archetype. But if you define the archetype with
content="elemOnly",
Obligatory disclaimer: I'm new to this list and was routed
here for feedback by the Xerces documentation. If this is the wrong list
or these bugs have already been reported, my apologies...
I'm using XML4J 3.0 EA with JDK 1.2.2, and I've hit a few
problems with XML Schema validation, to wi
You can pretty much do that now with V3. There is a 'reuse validator' flag
on the parse() call. If you get the validator loaded up once, you can just
force the use of that validator on subsequent parses. The files being
parsed cannot have any internal subset if you do this, they can only have a
>[JBDP] I don't know how many people have compilers and libraries
(including
>legacy libraries, whether home-grown or thirds party) that support
>character-style and string-style operations on unsigned shorts so I don't
>know how "few" the people are who will be inconvenienced.
It is our belie
Tim Bray wrote:
> I'm with Mr. Roddey. At this point in history, doing extra work or adding
>
> extra complexity in order to empower people to dodge internationalization
> is just not defensible on business, engineering, or ethical grounds. -Tim
[JBDP] Well I kind of agree on the moral front: I
[JBDP] In reply to Dean Roddy:
> I would like to go on the record as saying that I'm very much against
> this
> proposal, nothing personal.
[JBDP] Fair enough.
> I believe that the simplicity and maintainability of the current
> architecture is more important. The work to make the parser core
>
I have just joined this discussion group so pardon me if I am suggesting
something that has previously been discussed...
I am going to use the term "DTD" but it should be interchangeable with
"schema" in my following discussion.
I would like to be able to validate a document against one or more D
you can ignore this, I'm debugging something on the mail server. Thanks.
Brian
Well, I'm not going to argue with you about whether DOMString is a good
implementation or not, perhaps its not. I didn't write it and I don't know.
The fact that you don't get null terminated strings out of DOMString is an
implementation issue with DOMString, not a good argument necessarily for
I am confirming that I was successfully able to compile the samples
after installing the binary drop of Xerces 1.0.0 for Linux.
all the settings that I did were:
export XERCESCROOT=~/xerces-c_1_0_0-linux
export LD_LIBRARY_PATH=~/xerces-c_1_0_0-linux/lib
if this still does not work
11 matches
Mail list logo
