Re: [ubl] docbook of NDR, etc

[harvey <harvey@eccnet.com>]

Hi Stephen:

I don't know if you are familiar with the work that is being done at
NIST on a tool for validating schema's against NDR rules.  The tools
is called "Quality of Design" or QOD (http://sourceforge.net/projects/qod/).

You might want to take a look at the tool - I think you might find it
very useful.

I have been working with NIST in developing user requirements and
schema design.  We have developed a schema we are calling (NDRProfile).
The profile schema provides the ability to author a subset of the
NDR for importing and exporting rules in an out of QOD.  QOD provides
the ability to encode the rules in both Schematron or JESS.

The conversion of the UBL NDR Word document went pretty smoothly because
Mike and Mavis did an excellent job of maintaining Word styles.  They
also had uniform styles that allowed me to convert the Docbook UBL into
an NDRProfile.

If you are interested in any of these files I have them available at:

http://ecc02.eccnet.com/ndr/UBLNDR/UBLNDR/

The file "UBL-NDR-Docbook-20070207.xml" is the full NDR.  The file
"UBL-NDR-Profile.xml" file is the file that is used to import the UBL
profile to QOD.  The NDRProfile schema is in the process of being
modified because of modifications that is being made to QOD to support
import/export of NDRProfile.

The PDF file in this directory was created using Ken Holman's Docbook
to OASIS PDF stylesheet for XSL-FO.

If you have any questions or ideas, please let me know.  There may
possibly be some synergy with what you are doing and what NIST is
doing with QOD.

Betty


> An aside regarding the docbook of NDR: I'm working a bit with TAG TC
> which involves looking at best practices and examples of specification
> approaches (as precursors to documenting 'test assertions' - precursors
> in turn to test cases which software producers would develop) and
> it is very interesting a) how UBL have developed the NDR and its
> checklist and b) how this has been represented in docbook.
> Would UBL TC object at all to my using the NDR format, checklist and
> docbook representations, perhaps, as examples for some of the TAG TC
> work? It might be that this will help with considerations of how test
> assertion guidelines/lists as well as specifications such as the NDR.
> Maybe this will in turn inspire some ideas about how to represent an
> NDR such as UBL's as a list of test assertions such as those in a format
> the TAG TC hope to specify and describe.
>
> Best regards
>
> --
> Stephen Green
>
> Partner
> SystML, http://www.systml.co.uk
> Tel: +44 (0) 117 9541606
>
> http://www.biblegateway.com/passage/?search=matthew+22:37 .. and voice
>
>
>
> Quoting harvey <harvey@eccnet.com>:
>
>> Your right Mike - my mistake.  I actually converted 2 versions of
>> the NDR and I was looking at the 7/19/2007 versaion and the last
>> version was 2/7/2007.
>>
>> Thanks for keeping me straight!
>>
>> Betty
>>
>>>
>>>
>>> [CDL4] was removed some time ago (prior to your docbook conversion of
>>> the
>>> NDR).
>>>
>>>
>>> -----Original Message-----
>>> From: harvey [mailto:harvey@eccnet.com]
>>> Sent: Monday, 17 September 2007 1202
>>> To: ubl@lists.oasis-open.org
>>> Subject: [ubl] Codelist Question
>>>
>>> Are we (meaning UBL) officially using Genericode?  The NDR hasn't been
>>> modified to reflect the ability to use it:
>>>
>>> [CDL4]	All UBL maintained or used Code Lists MUST be enumerated using
>>> the
>>> UBL Code List Schema Module.
>>>
>>>
>>> Thanks!
>>>
>>> Betty
>>>
>>>
>>> /\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/
>>> Betty Harvey                         | Phone: 410-787-9200 FAX: 9830
>>> Electronic Commerce Connection, Inc. |
>>> harvey@eccnet.com                    | Washington,DC XML Users Grp
>>> URL:  http://www.eccnet.com          | http://www.eccnet.com/xmlug
>>> /\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/
>>> Pray for Mac (http://www.macsteam.org)
>>>
>>
>>
>>
>
>
>
>