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


Help: OASIS Mailing Lists Help | MarkMail Help

ubl-dev message

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

Subject: Re: [ubl-dev] looking for practical examples

Hi Ken

I'm not entirely OK with the diagram. I had envisiaged something
more along the lines of augmenting rather than replacing the
common schemas. I had thought, to meet the cust guidlines we
requirements, we would suggest people keeping all of the UBL
OASIS standard schemas intact and adding the custom types in
additional schema(s). Then the choice would be whether to put all
the new elements and types into just one custom schema (which
imports the UBL common schemas) - with the document element
as root - or whether, like with the UBL standard schema modules,
to split the schema into either two or three - either {document plus
custom basic schema plus custom aggregate schema} or
{custom document schema plus custom common schema}. Also
there would need to be a guideline on how to do the imports -
whether, say, the custom document schema imports everything
or whether the custom common schema(s) import their respective
standard schemas and are imported by the custom document
schema. Thinking of the possibility of using SET (OASIS SET TC)
tools for interoperability between custom and standard documents,
I'd suggest the guidelines might consider how to ensure the design
provides a consistent data dictionary within the schemas with a
use case that SET schema to OWL tools can create their OWL
ontology from the custom schema set (including the standard
UBL schema set). The aim would be to ensure a set of tools can
ascertain what impact the customisation might have on any existing
implementation based on the standard UBL schemas.

Best regards

- Steve

2009/2/12 G. Ken Holman <gkholman@cranesoftwrights.com>:
> At 2009-02-10 19:13 +0000, Stephen Green wrote:
>> 1. Create a new document called, say, Inventory - with your own
>> namespace for the document but import the common schemas so
>> you can make it almost the same as the UBL Catalogue - just with
>> a new InventoryLine, like Ken says, which adds StockQuantity or
>> something like that (and maybe a few more things like that). There
>> are a few things to make the writing of the schema (like Ken, I too
>> strongly recommend keeping to a schema - testing the messages
>> that they are valid by the schema - at design stage at least). You
>> will want the extra InventoryLine and somewhere to put it in the set
>> of schemas. Maybe Ken has an opinion on whether to put this
>> aggregate in the document schema (I guess that breaks the NDR,
>> Ken) or whether to create not just a custom document schema but
>> a 'common' schema too: If the latter then maybe both a basic and
>> an aggregates common schema?
> Precisely!  The following is a diagram from our training material that we
> delivered in Australia in January, and is now available as part of the
> latest edition of our "Practical Universal Business Language Deployment"
> book (published today!):
>  http://www.CraneSoftwrights.com/sales/Crane-UBLProfile/#schemasy
> I'm proposing to the UBL TC that these diagrams be included in the
> customization guidelines.
>> Those technical issues might seem overly detailed.
> But I think the approach is sound, which is why it is included in our book
> and training material.
>> > And if you can join the TC, bring in your new documents, and find others
>> > to
>> > collaborate with in order to come up with flexible and useful
>> > configurations
>> > of those new documents, they might end up becoming UBL documents!
> Which was the reasoning behind creating aggregate and basic schema fragments
> analogous to those of UBL so that the business objects can migrate into the
> common library if the UBL technical committee chooses to effect.
> I hope this helps.
> . . . . . . . . . . . Ken
> --
> Upcoming hands-on XSLT, UBL & code list hands-on training classes:
> Brussels, BE 2009-03;  Prague, CZ 2009-03, http://www.xmlprague.cz
> 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

Stephen D. Green

Document Engineering Services Ltd

http://www.biblegateway.com/passage/?search=matthew+22:37 .. and voice

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