[
Lists Home |
Date Index |
Thread Index
]
bryan rasmussen wrote:
> So if I tell them, well you can seperate your namespaces out very
> easily this way, and send them to different processes, then the
> natural response of the guy in charge on their side is, okay, once
> I've seperated stuff out why don't I just send namespace a to schemas
> for a and namespace b to schemas for b? What value do I get from NVDL.
Simple separation of namespaces is not sufficient of validation. NVDL
allows you to specify how different namespaces can be combined depending
on context. In your scenario context (which I see as one of the most
important feature of NVDL) is not taken into account.
>> Do you have any idea how API that returns outcome of NVDL validation as
>> validated streams your are talking about should look like? I still don't
>> get it.
>>
> It does not actually have to be streams, I just got into talking
> streams cause it seemed someone else was thinking specifically of
> streams, perhaps this made things more difficult to communicate. But I
> would suppose an api would expose something like the following:
>
> Nvdl.Instance.Namespaces - an array of namespaces
> Nvdl.Instance.isValid(namespace) - boolean
> Nvdl.Instance.validatedXml(namespace)
>
> no doubt there would be other things but with this then one could do,
> as per following pseudocode
> variable x;
> for each namespace in Nvdl.Instance.Namespaces
> if(Nvdl.Instance.isValid(namespace)==True){
> x=Nvdl.Instance.validatedXml(namespace);
> DoSomethingWithXml(x)
> }
Again, such model doesn't take context of XML fragments into account.
After sectioning you can have multiple fragments from the same namespace
(for example all SVG images extracted from XHTML page). I think that
without context you can not reliably and meaningfully process such
content. Anyway NVDL model with separated sections is built during
validation in JNVDL, so you can access it if you need it. If there will
be more interest in such API, we can polish it little bit and made it
public in future.
Still I think that NVDL alone is not suitable for your task, but I can
imagine that NVDL + XProc will handle it better.
Jirka
--
------------------------------------------------------------------
Jirka Kosek e-mail: jirka@kosek.cz 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
------------------------------------------------------------------
S/MIME Cryptographic Signature
|
