[clr-dev] Genericode / CVA validation

["Linda van den Brink" <linda@dynasol.nl>]

Great work!

I am working with a customer in The Netherlands who are now starting
to use Genericode in some of their XSDs.

Because some of their code lists can change pretty regularly, they
don't want to use the example validation implementation provided by
CraneSoft. Their objection is that the values from the code list are
hard coded in the generated Schematron and XSLT. They don't want to
have to regenerate the Schematron and XSLT each time a code list
changes.

I'm wondering if it is easy to change the implementation so that the
Schematron reads the code lists dynamically using the document()
function, or if maybe the latest version already does that?

Regards, Linda van den Brink

On Wed, Nov 12, 2008 at 3:46 PM, G. Ken Holman
<gkholman@cranesoftwrights.com> wrote:
> Fellow CLR-dev subscribers,
>
> While the Code List Representation Technical Committee list has been quiet,
> there have been a growing number of users of OASIS genericode and the
> proposed Context/Value Association document model.  I've been working with
> people in New Zealand, England and Belgium on new implementations, as well
> as assisting the UBL committee with their 2.0 update release with updated
> files.  I also had the opportunity to teach a full day on genericode and CVA
> in Rome in April.
>
> Further to Maarten's formal request:
>
>  http://lists.oasis-open.org/archives/codelist-comment/200811/msg00000.html
>
> ... I have addressed a couple of small issues that have been piling up:
>
>  - augmented the Identification section to be more in line with genericode
>  - rearranged and augmented the Annotation section to be more in line with
>   genericode
>  - added the mark="" attribute to characterize a context with a name token
>
> Maarten's request was framed using Schematron, yet CVA is specified to be
> implementation independent.  The new CVA mark="" attribute can be
> implemented with flag="" when using Schematron as the implementation.  Using
> "mark" reflects that the user is marking the particular context with some
> abstract characteristic that may be useful in downstream distinctions of the
> constraint violations.
>
> Still not addressed are valuable comments from Tony regarding the prose used
> in the draft specification.  I'm waiting until we stop getting technical
> comments before reworking the prose.
>
>  The specification of CVA:
>
>  http://www.oasis-open.org/committees/document.php?document_id=29990
>
>  An example Schematron implementation of CVA for validation:
>
>  http://www.cranesoftwrights.com/resources/ubl/index.htm#cva2sch
>
>  XSLT 1.0 stylesheets for rendering CVA and genericode files in HTML:
>
>  http://www.cranesoftwrights.com/resources/ubl/index.htm#codess
>
> As always, any feedback is very much appreciated.
>
> . . . . . . . . . . . . . Ken
>
> --
> Upcoming XSLT/XSL-FO hands-on courses:      Wellington, NZ 2009-01
> Training tools: Comprehensive interactive XSLT/XPath 1.0/2.0 video
> Video sample lesson:    http://www.youtube.com/watch?v=PrNjJCh7Ppg
> Video course overview:  http://www.youtube.com/watch?v=VTiodiij6gE
> G. Ken Holman                 mailto:gkholman@CraneSoftwrights.com
> Crane Softwrights Ltd.          http://www.CraneSoftwrights.com/c/
> Male Cancer Awareness Nov'07  http://www.CraneSoftwrights.com/c/bc
> Legal business disclaimers:  http://www.CraneSoftwrights.com/legal
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: clr-dev-unsubscribe@lists.oasis-open.org
> For additional commands, e-mail: clr-dev-help@lists.oasis-open.org
>
>