Re: [ubl-dev] Customizing UBL: first steps

2009/1/23 G. Ken Holman <gkholman@cranesoftwrights.com>

At 2009-01-22 15:46 +0100, Martin Kempe wrote:

I hope I'm not spamming this mailing list with "beginner's questions".

Beginners' questions are always welcome!

I am pretty sure I know what I want to do with my UBL extension project, but I am lacking a first step to take. I want to create an additional schema-definition that extends some BIEs with advanced, respectively specific, content.

You have to decide if you want a compatible customization or a conformant customization.

A compatible customization allows you to model the extensions at the point in the UBL document hierarchy where the business objects are used, but the end result is an XML vocabulary that interoperates at the model level but not the instance level.

A conformant customization requires you to model the extensions under the extension point, and the end result is an XML vocabulary that interoperates at the instance level.

What I wonder about is how to begin. I read the draft of the Guidelines for Customization

For the archive, I assume you are reading from:

http://docs.oasis-open.org/ubl/guidelines/UBL-Customization1.0prd01.pdf

and what i wish to have is the underlaying schema-definitions of the example in "figure 17" on page 27.

Then you are looking for a conformant customization where you are defining the constructs under the UBL extension point.

The example comprises, what I want to achieve, but not how to get there.

It isn't in the committee purview to recommend specific tools, but only the artefacts that are needed in order to achieve the desired result.

Reviewing the specification document:

http://docs.oasis-open.org/ubl/os-UBL-2.0/UBL-2.0.html

I note section 5.2.5:

http://docs.oasis-open.org/ubl/os-UBL-2.0/UBL-2.0.html#d0e3540

... the use of the Extension Content Datatype schema fragment. That references the description text here:

http://docs.oasis-open.org/ubl/os-UBL-2.0/UBL-2.0.html#d0e3968

Can you give me any hints?

Can you share which step is stymieing you?

You will need to create your own schema fragments for the namespaces associated with the "eac:" and "ebc:" prefixes (note those prefixes are arbitrary and you could equally use "harry:" and "sally:").

The schema fragment common/UBL-ExtensionContentDatatype-2.0.xsd needs to be replaced with your own schema fragment (of the *same* name, you physically need to replace this file) that replaces:

<xsd:complexType name="ExtensionContentType">

... with whatever complex type you define in your own schema fragments as the apex of your extensions.

The UBL schemas will then pull in your definitions as part of the validation process.

I hope this helps.

. . . . . . . . . . . . Ken

--
Upcoming XSLT/XSL-FO, UBL and code list hands-on training classes:
: Sydney, AU 2009-01/02; Brussels, BE 2009-03; Prague, CZ 2009-03
Training tools: Comprehensive interactive XSLT/XPath 1.0/2.0 video
Video lesson: http://www.youtube.com/watch?v=PrNjJCh7Ppg&fmt=18
Video overview: http://www.youtube.com/watch?v=VTiodiij6gE&fmt=18
G. Ken Holman mailto:gkholman@CraneSoftwrights.com
Crane Softwrights Ltd. http://www.CraneSoftwrights.com/u/
Male Cancer Awareness Nov'07 http://www.CraneSoftwrights.com/u/bc
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