[
Lists Home |
Date Index |
Thread Index
]
Ken,
some 'at first glance' questions. If these seem a bit dumb, please take them
as an oppotunity to promote the strengths of this approach :-
1. How does this approach specifically assist in dealing with versioning
issues ?
2. I see mention of auditability and impact analysis but didn't understand
how these would be acheived. ?
3. How is this approach 'better' than creating a vocabulary schema for each
third party contract using the 'chameleon' schema +
xs:redefines/union/restrition etc. I mentioned earlier (I take the point
about being able to specify particular contexts in which an enumeration can
apply - but is there more ?)
4. Large lists are still a problem right ?. It is not unusual in the
financial services sector for many lists to be > 200 entries, a reasonable
number to be > 1000 and a few that are >10,000. Using schematon XSLT would
be a bit impractical wouldn't it ?
4. You mentioned in your earlier response to Glen, that you had hoped in UBL
to remove ALL embedded enumerations from schema. Did you decide then that no
enumeration could be considered 'stable' or did you want this just to keep
the approach consistent regardless ? (you also mention 'type 1' code lists
which suggest in schema definition ?)
Cheers
Fraser.
>From: "G. Ken Holman" <gkholman@CraneSoftwrights.com>
>To: "Fraser Goffin" <goffinf@hotmail.com>
>Subject: Re: [xml-dev] Versioning of Enums
>Date: Sun, 12 Feb 2006 19:22:36 -0500
>
>[off-list]
>
>At 2006-02-12 23:30 +0000, you wrote:
>>Thanks Ken. I will certainly give this material a thorough read. Tony
>>Coates was I believe one of the original proponents of the method I was
>>suggesting below, so evolution of this thinking sounds promising (plus you
>>know I am a big fan of schematron already :-).
>
>Aren't we all? :{)}
>
>>I am certainly interested in your final revision and who knows I may come
>>along to one of the conferences you mention to hear it first hand.
>
>That would be nice.
>
>>I will send you any feedback that comes to mind after a read and possibly
>>a bit of experimentation with my own specific use cases.
>
>Thanks, Fraser!
>
>And thanks for the on-list discussion as I'm anxious to bring this
>methodology to the attention of as many projects as possible.
>
>. . . . . . . . . . . . Ken
>
>
>--
>Upcoming XSLT/XSL-FO hands-on courses: Washington,DC 2006-03-13/17
>World-wide on-site corporate, govt. & user group XML/XSL training.
>G. Ken Holman mailto:gkholman@CraneSoftwrights.com
>Crane Softwrights Ltd. http://www.CraneSoftwrights.com/m/
>Box 266, Kars, Ontario CANADA K0A-2E0 +1(613)489-0999 (F:-0995)
>Male Cancer Awareness Aug'05 http://www.CraneSoftwrights.com/m/bc
>Legal business disclaimers: http://www.CraneSoftwrights.com/legal
>
|
