[
Lists Home |
Date Index |
Thread Index
]
- From: "KenNorth" <KenNorth@email.msn.com>
- To: <xml-dev@xml.org>
- Date: Sun, 9 Jul 2000 15:32:48 -0700
Walter,
<< the salient rules are those most exactly specific, perhaps unique, to
the particular occasion and environment
<< That, precisely, is why the schema actually implemented in a processing
instance is, as I described it, effectively a schema of the relationships of
the input data,
Not every application view of data is unique, nor are schemas simply for
processing inputs. Consider a scenario such as a consumer electronics
manufacturer with global distribution:
- Shipping address rules fit your uniqueness criteria. Orders require
locale-specific rules.
- There are, however, documents whose content is not unique to a locale. For
example, consider a worldwide list of authorized repair centers. An
application might generate the list twice per year using an SQL query, and
then use an XML schema to validate the output document. The data is fairly
static, and a server in Canada delivers the same document as a server in
Hong Kong.
***************************************************************************
This is xml-dev, the mailing list for XML developers.
To unsubscribe, mailto:majordomo@xml.org&BODY=unsubscribe%20xml-dev
List archives are available at http://xml.org/archives/xml-dev/
***************************************************************************
|