Title: RE: [ubl-ndrsc] Draft Partial Document Use Case - Justification f or Document at the Top Level Tag Name Mark and NDRSC Team, Correct me if I'm wrong, it was my understanding that the UBL Naming Design Rules Sub-Committee is trying to establish rules that eventually will be adopted by the larger ebXML community. I quote the NDRSC purpose from the Web site -- The purpose of the NDR SC is to recommend to the TC rules and guidelines for normative-form schema design, instance design, and markup naming, and write and maintain documentation of these rules and guidelines. It has been my assumption (perhaps wrong) that the once the rules are adopted by the TC, they will be promoted within the larger ebXML community. In my opinion, the scope of tag naming must go beyond the naming of tags for traditional business transactions. Within the illustration that I provided, the tagging of engineering data is only the tip of a much larger iceberg for back-office application to application integration.The tag naming rules that I am proposing are the rules one would use when assigning tag names to data within all structured databases used within an enterprise. The fact that engineering data needs to be shared in real B2B types of scenarios is simply an example of standardizing tag names for exchanging data between two or more systems within a B2B context. I simply believe that this is such an important topic that if included within the scope of the NDRSC, it would enhance the potential adoption of the naming rules by the larger ebXML community. Ronald L. Schuldt Senior Staff Systems Architect Lockheed Martin Enterprise Information Systems 11757 W. Ken Caryl Ave. #F521 MP DC5694 Littleton, CO 80127 303-977-1414
ron.l.schuldt@lmco.com