Re: [ubl-dev] Free UBL NDR 2.1 schema generator

On 25 October 2011 14:02, Stephen D Green <stephen.green@documentengineeringservices.com> wrote:

That all sounds wonderful, Ken.

I can't think of any more that would be needed (maybe others can).

I would think there might be a need to stick to just the extension

of the tutorial to keep it simple but maybe something at the end

about any extra steps which might be needed to create a new

document using the common library.

Very good.

Cheers Ken

Steve
---
Stephen D Green

On 25 October 2011 11:56, G. Ken Holman <gkholman@cranesoftwrights.com> wrote:

At 2011-10-24 14:15 +0100, Stephen D Green wrote:

such as the
use case where they need to create a small extension schema for
a UBL invoice.

This is an excellent idea, Stephen!

It shouldn't be too hard to find a specific example (but
I might be out-of-date with my knowledge of what isn't already covered
by the 2.1 UBL invoice).

There *is* a specific example: the UBL 2.1 standardized signature extension! I will adapt this environment to accept a standalone genericode _expression_ of the BIEs of the signature extension and I should then be able to synthesize the fragment that will be included in the UBL 2.1 delivery.

Then anyone will be able to follow what I did for the signature extension to create their own custom extension for UBL documents.

In the past a utility invoice extension or one
for billing hours worked (by consultant or contractor, say) would have
been good ones and maybe one or other would still be appropriate.

And ..... what about someone wanting to create their own non-UBL document that uses the UBL common library? Two use cases: an independent who needs something that isn't already in UBL, and a group who wants to propose new documents to go into a future UBL.

I will adapt this environment to accept a standalone genericode _expression_ of the BIEs in a suite of non-UBL documents using the UBL common library. A group can then model their set of documents, express the contents in genericode, run it through this environment and get a set of schemas that work in unison with the UBL common library. Having done so, their non-UBL ABIEs and BBIEs will be suitably structured for the UBL TC to consider simply plugging in to the common library in a future version.

I already have pencilled in the necessary changes to the configuration file and invocations in order to effect both of the above features. I should be able to get a new version of this environment out by late next week (possibly earlier if I can juggle priorities) that will support them.

Then the environment is useful not only to any project following UBL NDR 2.1, but also any project group with constituents wanting to create custom extensions and additional documents for use with that project's artefacts.

If you (or anyone else) can think of any other features that would help in this schema-generating environment, please let me know ASAP so I can consider them for this next revision.

Thanks, again, Stephen!

. . . . . . . . . . Ken

--
Contact us for world-wide XML consulting and instructor-led training
Crane Softwrights Ltd. http://www.CraneSoftwrights.com/u/
G. Ken Holman mailto:gkholman@CraneSoftwrights.com
Google+ profile: https://plus.google.com/116832879756988317389/about
Legal business disclaimers: http://www.CraneSoftwrights.com/legal

---------------------------------------------------------------------
To unsubscribe, e-mail: ubl-dev-unsubscribe@lists.oasis-open.org
For additional commands, e-mail: ubl-dev-help@lists.oasis-open.org

ubl-dev message