Emad, I don't know if this directly answers your question, but the following URL points to an article that provides an update on The Metadata Coalition published in the The Data Administration Newsletter. As highlighted in the article, XML is used as the interchange format for the metadata in the Open Information Model (OIM) standard that is being revised by the Coalition. http://www.tdan.com/mdcupdate.htm Ron Schuldt Senior Staff Systems Engineer Lockheed Martin Enterprise Information Systems 11757 W. Ken Caryl Ave. #F521 MP DC5694 Littleton, CO 80127 Phone: 303-977-1414 FAX: 303-971-4274 email: [EMAIL PROTECTED] > ---------- > From: Emad N. Georgy[SMTP:[EMAIL PROTECTED]] > Reply To: Emad N. Georgy > Sent: Wednesday, March 01, 2000 1:18 AM > To: The XML/EDI Group > Subject: DB, Data Modeling and XML > > I would like more information on how XML can help enterprise-wide data > modeling and database administrators. Is there a Metadata standard out > there? If so, can anyone point me to some resources and examples? Would > love > to hear both the business case for it and the technical case (specifically > for modeling databases). > > Thanks. > -Emad > > ----- Original Message ----- > From: David RR Webber <[EMAIL PROTECTED]> > To: The XML/EDI Group <[EMAIL PROTECTED]> > Sent: Monday, February 28, 2000 8:24 PM > Subject: eDTD BUSINESS SCHEMAS > > > > http://www.bizcodes.org/eDTD/xml-eDTDWP.htm > > > > Please review the above content. You can download the XML > > and review the example in any XML capable tool. > > > > I'm intrigued by how this compares to Martin's approach at: > > > > http://www.sgml.u-net.com/neutral.htm > > > > Basically I would characterize that the difference is between > > 'explicit definitions' as opposed to 'implied definitions'. > > > > There's a lot to like about both approaches, and clearly > > blending the two has significant merit and possiblities. > > > > Martin's approach is clearly designed to be 'schema neutral'. > > While this has a lot of attractions - foremost is HIDING the worst > > aspects of Schema - the unreadablity - the devil is in the detail > > and the heavy reliance on a Repository to allow you to figure out > > what a : > > > > <InformationMessage ID="DespatchNote"> > > <GlobalID>LGMS12345</GlobalID> > > <Name>Despatch Note</Name> > > . . . . . . > > > > really is. > > > > Anyway - one thing is abundantly clear to me - the current > > W3C Schema proposal is coming up way short and way too light > > compared to these business focused approaches. > > > > I'm particularly disturbed by the use of MAXOCCURS / MINOCCURS. > > This I believe is a recipe for disaster on a global scale - that can > > cost implementers hundreds of millions $$$ annual resolving data > > conflicts that this mechanism will foster and encourage. > > > > Fortunately we have the ebXML initiative - and the ability to make > > the business requirements drive the technical syntax. > > > > I look forward to people's comments - refinements - and ideas to > > help create the right technology tools here. Of particular importance > > is to take these ideas and IMPLEMENT one of your own transactions. > > > > This will teach and instruct on what is really needed. I'm particularly > > focused on creating a Schema system that you can manually type in, > > and read, understand, and above all keep elegantly simple. > > > > That path leads to success in a global context. > > > > So we have the two levels - the top level, and the bottom level. > > The top level allows modelling of the business process, the > > bottom level provides succinct machine syntax to implement, > > support and effectively manage those top level processes > > using computer systems and XML syntax. > > > > This synergy I believe is at the heart of the ebXML effort and > > what we need to achieve over the coming months. > > > > Thanks, DW. > > > > ========================================== > > XML/EDI Group members-only discussion list > > Homepage = http://www.xmledi.com > > > > Brought to you by: Online Technologies Corporation > > Home of BizServe - www.bizserve.com > > > > TO UNSUBSCRIBE: Send email to <[EMAIL PROTECTED]> > > Leave the subject blank, and > > In the body of the message, enter ONLY: unsubscribe > > > > Questions/requests should be sent to: [EMAIL PROTECTED] > > To join the XML/EDI Group complete the form located at: > > http://www.geocities.com/WallStreet/Floor/5815/mail1.htm > > > > > > > > > ========================================== > XML/EDI Group members-only discussion list > Homepage = http://www.xmledi.com > > Brought to you by: Online Technologies Corporation > Home of BizServe - www.bizserve.com > > TO UNSUBSCRIBE: Send email to <[EMAIL PROTECTED]> > Leave the subject blank, and > In the body of the message, enter ONLY: unsubscribe > > Questions/requests should be sent to: [EMAIL PROTECTED] > To join the XML/EDI Group complete the form located at: > http://www.geocities.com/WallStreet/Floor/5815/mail1.htm > > ========================================== XML/EDI Group members-only discussion list Homepage = http://www.xmledi.com Brought to you by: Online Technologies Corporation Home of BizServe - www.bizserve.com TO UNSUBSCRIBE: Send email to <[EMAIL PROTECTED]> Leave the subject blank, and In the body of the message, enter ONLY: unsubscribe Questions/requests should be sent to: [EMAIL PROTECTED] To join the XML/EDI Group complete the form located at: http://www.geocities.com/WallStreet/Floor/5815/mail1.htm
