On Apr 7, 12:17=A0am, "P. Lepin" <p.le...@ctncorp.com> wrote:

>
> XML is case-sensitive. 'CustomerID' is not the same thing as
> 'customerID'.
>
P. Lepin,
Thank you very much for pointing out that error.

I ask the XML community out there, can anyone point out a resource
where
I can find some example XML Schema code that does not contain errors.
Specifically code showing the use of identity constraint features,
such
as unique, key, and keyref.

The code in question, where P. Lepin found the error was supplied by
a
small, and perhaps underfunded and understaffed U.S. software company
called
microsloft.  It is in their example code for how to use xsd:unique

Here is the link: http://msdn.microsoft.com/en-us/library/ms256146(VS.85).a=
spx

I looked around for a source a little more careful that microsloth,
I thought perhaps xml.com would be a reputable source.
Yet it also supplies erroneous examples (I think, I can't tell because
I can't find
a validator that I trust).  These errors seem even more obvious.
For instance: http://www.xml.com/2002/11/13/examples/Housing2.xsd.txt
Here the selector xpath attribute refers to an element that does not
exist.
I have copied the offending code here (I think they meant for the
selector to be HousingUnit)

    <key name=3D"UnitIDKey">
      <selector xpath=3D"Unit" />
      <field xpath=3D"@unitID" />
    </key>

I downloaded an evaluation version of Altova XMLSpy, because I came to
the conclusion one
has to pay money for a properly functioning XML validation tool.

Yet I can put anything in the xpath attribute for selector, hit the F8
key, and and Altova
gives me the green check mark saying everything is OK.
well I can't type in anything
  <selector xpath=3D"!@!@!"/>
causes a validation error, but
  <selector xpath=3D"obviouslyNonExistentXpathExpressionSubset"/>
is perfectly OK.

Maybe I don't understand what validation means.
It seems reasonable to me that a software tool could tell when an
xpath doesn't validly refer
to anything (it seems like it should have caught the error P. Lepin
caught, where
the selector field was "@customerID" instead of "@CustomerID").

I'm having a hard time learning XML, because I learn by example.
I can't seem to find any examples that I trust.
If anyone can point me to examples that I can trust, that would be
very helpful.

Is there a software tool that does the kind of validation I am looking
for?
If you are a vendor of such a tool please contact me.
AltovaSpy is $129, perhaps one needs to pay $1290 for the tool I
want??

-Thanks,
Chip Grandits
ATA


> --
> Waterfall: One Process To Rule Them All