[XML-DEV Mailing List Archive Home] [By Thread] [By Date] [Recent Entries] [Reply To This Message]

Re: Rick Jelliffe on designing XML Schemas in a way thatsuppor

• From: Fraser Goffin <goffinf@gmail.com>
• To: "xml-dev@lists.xml.org" <xml-dev@lists.xml.org>
• Date: Sun, 19 Aug 2012 23:14:50 +0100

The most obvious example of which is used by UBL which promotes this
approach for 'value based' validation (which isn't restricted simpy to
enums and can be quite successfully used for any information item).
UBL actually takes things a little further and caters not only for
dealing with multi-version validation but also context based
validation too (i.e. different subsets that apply to different
locations within the instance).

Ken Holman may be along shortly to correct my clumsy description.

That said, if Rick was using enums as just one possible use case for
schema volatility where schematron could play a role, and there are
others, then as Roger suggests, it is a topic that many are interested
in and probably deserves another outing.

Fraser.


On 19/08/2012, Frank Manola <fmanola@acm.org> wrote:
> Roger--
>
> The statement from Rick that you cite seems to be in the context of a
> discussion of schemas containing *enumerated lists*, rather than other kinds
> of XML Schema declarations (as in your example).  As Rick said, an
> enumerated list of US states (in the schema, for validation purposes) is
> likely to be static (and you could compile with it) but an enumerated list
> of publication types (in the schema, for validation purposes) is more likely
> to be dynamic.
>
> --Frank
>
> On Aug 19, 2012, at 8:01 AM, Costello, Roger L. wrote:
>
>> Hi Folks,
>>
>> Earlier this week Rick Jelliffe casually inserted into his message a
>> profound statement regarding how to create applications and XML Schemas in
>> a way that support parts which frequently change.
>>
>> I am trying to understand Rick's statement.
>>
>> I have many questions.
>>
>> Here is my summary of Rick's statement along with my questions:
>>
>> http://www.xfront.com/Rick-Jelliffe-on-Designing-XML-Schemas-in-a-way-that-Support-Parts-which-Frequently-Change.pdf
>>
>> Would you take a look at my summary and questions please?
>>
>> I suspect this issue is relevant for many people on this list.
>>
>> /Roger
>>
>> _______________________________________________________________________
>>
>> XML-DEV is a publicly archived, unmoderated list hosted by OASIS
>> to support XML implementation and development. To minimize
>> spam in the archives, you must subscribe before posting.
>>
>> [Un]Subscribe/change address: http://www.oasis-open.org/mlmanage/
>> Or unsubscribe: xml-dev-unsubscribe@lists.xml.org
>> subscribe: xml-dev-subscribe@lists.xml.org
>> List archive: http://lists.xml.org/archives/xml-dev/
>> List Guidelines: http://www.oasis-open.org/maillists/guidelines.php
>>
>
>
> _______________________________________________________________________
>
> XML-DEV is a publicly archived, unmoderated list hosted by OASIS
> to support XML implementation and development. To minimize
> spam in the archives, you must subscribe before posting.
>
> [Un]Subscribe/change address: http://www.oasis-open.org/mlmanage/
> Or unsubscribe: xml-dev-unsubscribe@lists.xml.org
> subscribe: xml-dev-subscribe@lists.xml.org
> List archive: http://lists.xml.org/archives/xml-dev/
> List Guidelines: http://www.oasis-open.org/maillists/guidelines.php
>
>

• Follow-Ups:
  • Re: Rick Jelliffe on designing XML Schemas in a way that support parts which frequently change
    • From: "G. Ken Holman" <gkholman@CraneSoftwrights.com>

• References:
  • Rick Jelliffe on designing XML Schemas in a way that support partswhich frequently change
    • From: "Costello, Roger L." <costello@mitre.org>
  • Re: Rick Jelliffe on designing XML Schemas in a way thatsupport parts which frequently change
    • From: Frank Manola <fmanola@acm.org>