OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.


Help: OASIS Mailing Lists Help | MarkMail Help

ubl message

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]

Subject: Re: [ubl] Suggestions for an UBL ExtensibleContent area

At 2006-02-27 09:00 +0100, Bryan  Rasmussen wrote:
>I updated some parts of the earlier document on our discussion point on a
>possible ExtensibleContent area for Wednesday, it was decided not to do a lot
>of additions to the document because the additions I was working on after a
>bit seemed to cloud the issue; these were such things as example extensions,
>possible varying validation mechanisms (Schematron, Namespace Routing
>Language http://www.thaiopensource.com/relaxng/nrl.html

In my role as Secretariat Manager for SC34 I've helped the authors 
marshal the evolution of the above into the standardized 
Namespace-based Validation Dispatching Language (NVDL) ISO/IEC 
19757-4 - part 4 of Document Schema Definition Languages (DSDL):


I have shared with others that I think NVDL would be the best basis 
for the customization of UBL using namespaces so have pointed them in 
this direction.

My gut feel is that using NVDL we would probably not need an explicit 
area for extensible content as the entire instance would be 
extensible ... different industries could add line-level detail, or 
document-level detail, however best fit with their needs, all without 
changing the read-only schemas published by UBL.  Explicitly creating 
such a section might lead to the impression that extensions could 
only be added in that section.

But I just haven't had the time to experiment with it yet as my focus 
has been on HISC and Code Lists.  I'm not sure if my ideas would work 
or not, but if we are going to start modifying the models (which I 
don't think we have to do) then hopefully someone will be able to 
find the time to experiment with NVDL first.

>), and application usage (transformation). This is more the kind of 
>thing that should be moved to HISC if ExtensibleContent was accepted.

I'm not confident that validation issues belong in HISC.  The code 
list value validation work I'm doing is in a task group of UBL, not of HISC.

. . . . . . . . Ken

Upcoming XSLT/XSL-FO hands-on courses: Washington,DC 2006-03-13/17
World-wide on-site corporate, govt. & user group XML/XSL training.
G. Ken Holman                 mailto:gkholman@CraneSoftwrights.com
Crane Softwrights Ltd.          http://www.CraneSoftwrights.com/o/
Box 266, Kars, Ontario CANADA K0A-2E0    +1(613)489-0999 (F:-0995)
Male Cancer Awareness Aug'05  http://www.CraneSoftwrights.com/o/bc
Legal business disclaimers:  http://www.CraneSoftwrights.com/legal

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]