[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: RE: [ubl-lcsc] [code lists] drafct of section to put in document ation- for comment
I second that.
____________________
Alan Stitzer
AVP
Marsh USA Inc.
1166 Avenue of the Americas
New York, NY 10036-2774
Phone: (561) 743-1938
Fax: (561) 743-1993
Internet: Alan.Stitzer@marsh.com
____________________
<<< Memo from STK@Finansraadet.dk@Internet on 27 October, 2003, 08:31:29 AM
Monday >>>
STK@Finansraadet.dk@Internet on 27 Oct 2003, 08:31 Monday
To: MCRAWFORD; ubl-lcsc
cc: (bcc: Alan Stitzer)
Subject: RE: [ubl-lcsc] [code lists] drafct of section to put in
document ation - for comment
And that statement Mark, I strongly agree with!
Best Regards
Stig Korsgaard
M.Sc.E Standardisation Manager
Tel: +45 3370 1083
Cell: +45 2121 8234
Mail: stk@finansraadet.dk
Danish Bankers Association
Amaliegade 7
DK-1256 Copenhagen K
Tel: 3370 1000
Fax: 3393 0260
mail@finansraadet.dk
www.finansraadet.dk
-----Original Message-----
From: CRAWFORD, Mark [mailto:MCRAWFORD@lmi.org]
Sent: 27. oktober 2003 14:05
To: ubl-lcsc@lists.oasis-open.org
Cc: UBL Design Rules (E-mail)
Subject: RE: [ubl-lcsc] [code lists] drafct of section to put in
documentation - for comment
Ken,
Are you stating that we would never switch from UBL code lists to
externally
generated code lists? NDR was pretty specific in stating that external
code
lists would be used wherever available, and that any UBL generated code
lists would only be used as an interim measure.
Mark
> -----Original Message-----
> From: G. Ken Holman [mailto:gkholman@CraneSoftwrights.com]
> Sent: Sunday, October 26, 2003 9:37 AM
> To: ubl-lcsc@lists.oasis-open.org
> Subject: Re: [ubl-lcsc] [code lists] drafct of section to put in
> documentation - for comment
>
>
> At 2003-10-25 09:16 -0400, CRAWFORD, Mark wrote:
> >An excellent first cut. I think you need to clarify hat all
> codes will be
> >handled by scheMa modules, regardless of their source so that the
> >necessary enumerations and their subsequent maintenance will
> not impact
> >the root schema.
>
> Not sure what you mean by "impact", unless the important
> point you raise
> here is that end users mustn't ever touch the UBL schema fragments as
> delivered ... that they are really inviolate and can be treated as
> read-only documents. I don't think that is mentioned anywhere and is
> something I agree should be brought out explicitly about the
> W3C schema
> expressions that are shipped.
>
> >I think you should also add that as external code ist owners
> do make their
> >code lists available in the form of importable schema modules, the
> >corresponding import statements for those code list modules will be
> >changed accordingly.
>
> Actually, the design I put forward precludes any changes to import
> statements and configuration is done at the file system level
> through the
> wholesale replacement of files. My supposition was that
> asking any user to
> edit a document was an invitation to typographical errors or
> incorrectly
> modified files that would be rendered useless and difficult
> to diagnose or
> repair ... and an easy source of complaints to the (future) UBL-dev
> regarding "what did I do wrong?".
>
> In place of editing import statements, the UBL design is
> hard-wired to
> utilize the code list definitions found in the "in-use" directory as
> documented by Tim:
>
> >From: Tim McGrath <tmcgrath@portcomm.com.au>
> >To: ubl-lcsc@lists.oasis-open.org <ubl-lcsc@lists.oasis-open.org>
> >Sent: Sat Oct 25 01:59:26 2003
> >Subject: [ubl-lcsc] [code lists] drafct of section to put in
> documentation
> >- for comment
> >...
> >Within the UBL schemas, an "in-use" directory is used to
> define each code
> >list to be used during the validation process. Only values
> for standard
> >definitions of code lists are validated for their content
> when UBL is run
> >out-of-the-box. All other code lists are validated using the placebo
> >definition merely as having a tokenized value, and this value is not
> >checked against any further constraints. Customised
> implementations can
> >chose to adopt either stock or private-use code list
> definitions, and
> >after any such engagement can revert to the out-of-the-box
> configuration
> >by engaging the original standard or placebo code list definition.
>
> Using this design, the sole responsibility is the wholesale
> replacement of
> the in-use definition file with the desired definition file,
> be it one that
> we've supplied or however that desired definition file may be
> created. And
> we are supplying my XSLT stylesheet that helps in the synthesis of
> qualified private-use definition files.
>
> This wholesale replacement can be done with any
> file-system-level "copy"
> command and without editing any UBL files whatsoever that
> might jeopardize
> the integrity of the W3C schema fragments.
>
> I hope this addresses the concerns that you had.
>
> ................... Ken
>
> --
> Next public European delivery: 3-day XSLT/2-day XSL-FO 2004-01-??
> Instructor-led on-site corporate, government & user group training
> for XSLT and XSL-FO world-wide: please contact us for the details
>
> G. Ken Holman mailto:gkholman@CraneSoftwrights.com
> Crane Softwrights Ltd. http://www.CraneSoftwrights.com/o/
> Box 266, Kars, Ontario CANADA K0A-2E0 +1(613)489-0999 (F:-0995)
> ISBN 0-13-065196-6 Definitive XSLT and XPath
> ISBN 0-13-140374-5 Definitive XSL-FO
> ISBN 1-894049-08-X Practical Transformation Using XSLT and XPath
> ISBN 1-894049-11-X Practical Formatting Using XSL-FO
> Member of the XML Guild of Practitioners: http://XMLGuild.info
> Male Breast Cancer Awareness http://www.CraneSoftwrights.com/o/bc
>
>
> To unsubscribe from this mailing list (and be removed from
> the roster of the OASIS TC), go to
> http://www.oasis-open.org/apps/org/workgroup/ubl-lcsc/members/
leave_workgroup.php.
To unsubscribe from this mailing list (and be removed from the roster of
the
OASIS TC), go to
http://www.oasis-open.org/apps/org/workgroup/ubl-lcsc/members/leave_workgrou
p.php.
To unsubscribe from this mailing list (and be removed from the roster of
the OASIS TC), go to
http://www.oasis-open.org/apps/org/workgroup/ubl-lcsc/members/leave_workgroup.php
.
To: MCRAWFORD@lmi.org@Internet, ubl-lcsc@lists.oasis-open.org@Internet
cc: (bcc: CN=Alan Stitzer/OU=NYC-NY/OU=US/OU=Marsh/O=MMC)
From: STK@Finansraadet.dk@Internet
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]