> How do you create a single XML vocabulary, and validate that XML
> vocabulary, for a community that has sub-groups that have overlapping
> but different data needs?
>
>
> EXAMPLE
>
> Consider the book community. It is comprised of:
>
> - book sellers
> - book distributors
> - book printers
>
> They have overlapping, but different data needs.
>
> For example, the data needed by a book seller is:
>
> - the title of the book
> - the author of the book
> - the date of publication
> - the ISBN
> - the publisher
>
> The book distributor has many of the same data needs, but also some
> differences:
>
> - the title of the book
> - the author of the book
> - the size of the book
> - the weight of the book
> - the mailing cost
>
> And the book printer has overlapping but different needs:
>
> - the size of the book
> - the number of pages
>
> How does the book community deal with such differing needs?
Couldn't you just have three schema's each containing their own
definition of <book>, which import a common schema where everything
else is defined?
The book sellers will use book-seller.xsd, the distributor will use
book-distributor.xsd etc... seems simple enough?
--
Andrew Welch
http://andrewjwelch.com
Kernow: http://kernowforsaxon.sf.net/
