[Home] [By Thread] [By Date] [Recent Entries]

  • To: "Jirka Kosek" <jirka@k...>
  • Subject: Re: Java NVDL implementation
  • From: "bryan rasmussen" <rasmussen.bryan@g...>
  • Date: Sun, 7 May 2006 08:56:47 +0200
  • Cc: "XML Dev" <xml-dev@l...>
  • Domainkey-signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=TRlM3aBBmMUhnCqBGkGRIDqVLm89lm+rPIsaFN3zH47iVhTgUyl6sTZz7BmtK+MFP6Yt3pEyK2F6t/MErZAoBCIMs3MhTdYYKs8rHwn9PwQXvEbR82ksSSnr+7dqJ8umAtHNBg5Y4oJGCx6Fd/uAM90xb8rurvAtko6A8gq+UhY=
  • In-reply-to: <445CC1CC.9000709@k...>
  • References: <74B14CBC0FEB9D4EB16969F09FA51F45F473BF@M...> <445CC1CC.9000709@k...>

The other version NVDL implementation in its current version does
support XML Schema, at any rate I have compiled a version of it that
does, there were some problems getting it to work but Atsushi Eno the
implementer was very helpful.

One question I have about this implementation is: what returns at the
end of an NVDL validation?

Since the .Net NVDL implementation is a validatingReader what returns
is XML, however that XML is the original input XML if valid, meaning
that namespaces are not seperated, I don't find it problematic to
handle myself but it does decrease the attractiveness of NVDL and I
think others might find it a real problem.

Thus I'm really interested to hear if your implementation returns
something other than the original xml.

Couldn't find anything in the spec saying what should be returned by a
validation, but I may have overlooked things.

Cheers,
Bryan Rasmussen
On 5/6/06, Jirka Kosek <jirka@k...> wrote:
> Chiusano Joseph wrote:
>
> > I understand that there were some issues in the past regarding some
> > NVDL implementation supporting W3C Schema (I don't recall which one,
> > assuming that there are more than one). Can you please confirm that
> > your implementation fully supports W3C Schema, in addition to RNG?
>
> JNVDL just creates fragments from validated document and these fragments
> are then passed to respective validators for validation against specific
> schema (be it WXS, RNG, or whatever else). JNVDL uses standard JAXP 1.3
> validation API, so any validator which supports this API can be used for
> WXS validation.
>
> By default JNVDL uses MSV library for validation, but distribution also
> contains sample batch file (jnvdl-xerces.bat) which changes WXS
> validator from MSV to Xerces just by changing one Java property. So if
> Xerces is enough for you, or you have even better WXS validator then
> Xerces, you can use it very easily with JNVDL.
>
>                         Jirka
>
> --
> ------------------------------------------------------------------
>    Jirka Kosek     e-mail: jirka@k...     http://www.kosek.cz
> ------------------------------------------------------------------
>    Profesionální školení a poradenství v oblasti technologií XML.
>       Podívejte se na náš nově spuštěný web http://DocBook.cz
>         Podrobný přehled školení http://xmlguru.cz/skoleni/
> ------------------------------------------------------------------
>                     Nejbližší termíny školení:
>         ** DocBook 15.-17.5.2006 ** XSL-FO 12.-13.6.2006 **
>      ** XSLT 23.-26.10.2006 ** XML schémata 13.-15.11.2006 **
> ------------------------------------------------------------------
>    http://xmlguru.cz    Blog mostly about XML for English readers
> ------------------------------------------------------------------
>
>
>
>

Site Map | Privacy Policy | Terms of Use | Trademarks
Free Stylus Studio XML Training:
W3C Member