Looks good!  (And slightly better spelling in v2...😃)
On May 2, 2015 1:48 PM, "Shivani Mall" <[email protected]> wrote:

> First off, I am really happy that we are improving the documentation for
> VXQuery. This will help future developers understand VXQuery much better.
>
> I had the documentation ready for a different xml doc. But it won't take
> much to incorporate this one. This documentation will be available in my
> next patch, hopefully in a week or two from now.
>
> Thanks,
> Shivani
> ᐧ
>
> On Sat, May 2, 2015 at 12:54 PM, Till Westmann <[email protected]> wrote:
>
> > Looks pretty good to me.
> > We’re got a document node, 3 element nodes, an attribute node, a comment
> > node, a processing instruction, and a text node.
> > The only thing that seems to be missing (didn’t realize that before) are
> > namespaces!
> > So maybe we can change it to be this:
> >
> > <?xml version="1.0"?>
> > <catalog xmlns:ex="http://example.org/"; >
> >   <ex:book isbn="0812416139">
> >     <!--top secret-->
> >     <title>Macbeth</title>
> >     <?hide?>
> >   </ex:book>
> > </catalog>
> >
> > Cheers,
> > Till
> >
> >
> > > On May 1, 2015, at 5:10 PM, Eldon Carman <[email protected]> wrote:
> > >
> > > In an effort to improve our documentation, Shivani suggested adding a
> > > commented XDM representation for a sample XML document on our website.
> > Till
> > > suggested the document include all the different types of elements that
> > can
> > > be in a XML document (attribute, comments, etc.). Here is a suggested
> XML
> > > document:
> > >
> > > <?xml version="1.0"?>
> > > <catelog>
> > >  <book "title"="007">
> > >    <!--top secret-->
> > >    <foo>bar</foo>
> > >    <?hide?>
> > >  </book>
> > > </catelog>
> > >
> > > Does this provide enough variety to make a complete example?
> >
> >
>

Reply via email to