Lists Home |
Date Index |
Something that addresses the issue of application/data model interaction,
perhaps? Like, how to best insulate your application from nonpertinent/minor
tweaks to the underlying data model (as relates to XML Schema)? In other
words, maintain flexibility in the data model, but avoid having changes
constantly disrupt your development process?
I think that ties in versioning, data model extensibility, and patterns for
insulating the internal application object model from that of the
hierarchical data model represented by the schema. Is that more or less it?
Might be a tad too meaty for the XML Schema-specific Best Practices site.
I've got a call in to find out, however...
> -----Original Message-----
> From: Dare Obasanjo [mailto:firstname.lastname@example.org]
> Sent: Thursday, March 07, 2002 11:08 AM
> To: Jeff Lowery; email@example.com
> Subject: RE: [xml-dev] Stupid Question (was RE: [xml-dev] XML doesn't
> dese rve its "X".)
> Something like that but perhaps with more complex or relevant
> I read it and [at first glance] it seemed to be further explanation of
> the information in the W3C XML Schema Primer with
> different examples.
> I'd like something a little more. I'll search around for more like it
> and if nothing really tickles my fancy I may just end up writing about
> it myself.
>  http://www.w3.org/TR/xmlschema-0/
> THINGS TO DO IF I BECOME AN EVIL OVERLORD #230
> I will not procrastinate regarding any ritual granting immortality.
> > -----Original Message-----
> > From: Jeff Lowery [mailto:firstname.lastname@example.org]
> > Sent: Thursday, March 07, 2002 10:50 AM
> > To: Jeff Lowery; Dare Obasanjo; email@example.com
> > Subject: RE: [xml-dev] Stupid Question (was RE: [xml-dev] XML
> > doesn't dese rve its "X".)
> > Spoke too soon. Looks like a lot is already covered on 
> > under the title "Extensible Content Models"; is that of the
> > flavor you crave, Dare?
> > >
> > > > ... What I'd like to see are examples and design
> > > > patterns that show how subtitution groups and abstract types
> > > > can be used to build polymorphic apps that adapt well to
> > > > schema evolution.
> > >
> > > I think that's an excellent suggestion for an addition to the
> > > Best Practices
> > > web site. There's already some coverage there on Schema
> > versioning
> > > (thanks, Priscilla); Schema robusting(?) would go
> > > hand-in-hand with that. I
> > > offer some thoughts on that subject in soon-to-be published book
> > > <?whoTooted?>, but an open discussion of tried and true
> > > approaches would
> > > certainly educate us all.
> > >
> > >  http://www.xfront.com/BestPracticesHomepage.html
> > >  http://www.manning.com/lowery/index.html
> > >
> > > -----------------------------------------------------------------
> > > The xml-dev list is sponsored by XML.org <http://www.xml.org>, an
> > > initiative of OASIS <http://www.oasis-open.org>
> > >
> > > The list archives are at http://lists.xml.org/archives/xml-dev/
> > >
> > > To subscribe or unsubscribe from this list use the subscription
> > > manager: <http://lists.xml.org/ob/adm.pl>
> > >