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

RE: U.S. Federal Goverment's Data Reference Model (DRM) XML Sc

.xml .sc
I'm interested in how you tackle the problem of translating from business object definitions into message definitions. I'm working with an organization that has designed schemas to represent its (many hundreds of) business objects, and is now struggling with the question of how to design messages for application data interchange that are based on these object definitions. The problem is that messages exchange information about a business object, and different messages exchange different subsets of the information. Making all the information mandatory and thereby forcing the sending application to populate the message with data that the recipient doesn't want to know seems unproductive; equally, making all the data optional seems to defeat the purpose of validation. So it seems that one needs a message definition (=type) for each message that is somehow related to the schema for the business object, but isn't related to it by one of the recognized mechanisms of restriction and extension. It needs some kind of concept of being "derived by projection". 
Any thoughts or advice?
Michael Kay

From: Chiusano Joseph [mailto:chiusano_joseph@b...]
Sent: 21 June 2005 19:30
To: xml-dev@l...
Subject: U.S. Federal Goverment's Data Reference Model (DRM) XML Schema

The XML Cover pages just announced[1] the availability of a draft XML schema[2] for the U.S. Federal Goverment's Data Reference Model (DRM) initiative. I am posting this here to invite comments from the broad XML community as to our approaches for this initiative. A specification for the DRM XML Schema is at [4] (includes all elements/attributes, their definition, and hyperlinks for efficient navigation).
I presented[3] on this schema at last week's First Quarterly DRM Public Forum along with Mike Daconta (U.S. Department of Homeland Security Metadata Program Manager), who is leading this vast interagency effort. We discussed the design factors that we took into account regarding the schema, use of existing open standards, and other aspects.
If you have comments or questions, please feel free to (a) submit them per the instructions in [1], (b) express them directly to me, or (c) express them here on the XML-DEV listserv.
[1] http://xml.coverpages.org/ni2005-06-20-a.html
[2] http://xml.coverpages.org/ni2005-06-20-a.html#schema20050611
(DRM XML Schema)
[3] http://xml.coverpages.org/DRM-SchemaPresentation20050613.pdf
(Presentation on DRM XML Schema)
[4] http://colab.cim3.net/file/work/drm/schema/Draft_FEA_DRM_Schema.htm
(DRM XML Schema Specification]
Joseph Chiusano
Booz Allen Hamilton
Visit us online@ http://www.boozallen.com/


Purchasing Stylus Studio from our online shop is Easy, Secure and Value Priced!

Buy Stylus Studio Now

Download The World's Best XML IDE!

Accelerate XML development with our award-winning XML IDE - Download a free trial today!

Don't miss another message! Subscribe to this list today.
First Name
Last Name
Subscribe in XML format
RSS 2.0
Atom 0.3

Stylus Studio has published XML-DEV in RSS and ATOM formats, enabling users to easily subcribe to the list from their preferred news reader application.

Stylus Studio Sponsored Links are added links designed to provide related and additional information to the visitors of this website. they were not included by the author in the initial post. To view the content without the Sponsor Links please click here.

Site Map | Privacy Policy | Terms of Use | Trademarks
Free Stylus Studio XML Training:
W3C Member
Stylus Studio® and DataDirect XQuery ™are products from DataDirect Technologies, is a registered trademark of Progress Software Corporation, in the U.S. and other countries. © 2004-2013 All Rights Reserved.