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

Re: How can I constrain publicly available schemas?

• To: xml-dev@l...
• Subject: Re: How can I constrain publicly available schemas?
• From: Charles Woerner <cwoerner@e...>
• Date: Mon, 04 Apr 2005 14:50:28 -0700
• In-reply-to: <4251ABE0.1030504@s...>
• Organization: Ensenda, Inc.
• References: <74B14CBC0FEB9D4EB16969F09FA51F4540180E@M...> <4250820A.60406@s...> <1112641754.7722.283.camel@borgia> <4251ABE0.1030504@s...>

> >The key is that we have a formal means of
> >annotating the relationship between the master and the derived.  In this
> >way we can design our processing pipeline to deal with whatever
> >constraints are appropriate at any stage.  As long as people follow the
> >business rule that the universe of valid documents for any derived
> >schema is a subset of the universe of valid documents for the
> >corresponding master schema, it all works very well indeed.  The problem
> >is that code review is the only way we have to enforce this rule.

Is the "formal means of annotating the relationship" through peer code
review?  Or am I missing something...

-- 
Thanks,

Charles Woerner
Integration Engineer
Ensenda, Inc.

• Follow-Ups:
  • Re: How can I constrain publicly available schemas?
    • From: Uche Ogbuji <Uche.Ogbuji@f...>

• References:
  • RE: How can I constrain publicly available schemas?
    • From: "Chiusano Joseph" <chiusano_joseph@b...>
  • Re: How can I constrain publicly available schemas?
    • From: Fraser Crichton <fraser.crichton@s...>
  • Re: How can I constrain publicly available schemas?
    • From: Uche Ogbuji <Uche.Ogbuji@f...>
  • Re: How can I constrain publicly available schemas?
    • From: Fraser Crichton <fraser.crichton@s...>

• Prev by Date: Re: How can I constrain publicly available schemas?
• Next by Date: Re: Ausdehnungslehre
• Previous by thread: Re: How can I constrain publicly available schemas?
• Next by thread: Re: How can I constrain publicly available schemas?
• Index(es):
  • Date
  • Thread