XMLIntroduction

Slide 1: 

Washington DC February 26, 2003 E-Grants Stakeholder Briefing XML as a Basis For Government Collaboration

The integration of business processes within and across enterprises is a key driver in IT strategy and investments : 

The integration of business processes within and across enterprises is a key driver in IT strategy and investments Strategic efforts are calling for an integrated approach to business execution Federal Enterprise Architecture Business Reference Model Homeland Security E-Government Projects Intra-Agency Process Automation New IT investments must address the imperative of business process integration Provide an integrated approach to critical applications and data repositories Provide end to end visibility for business process execution, regardless of organizational boundaries Leverage current IT investments and architect for future integration Reduce infrastructure complexity

Slide 3: 

What is XML? XML, eXtensible Markup Language, is a markup language based upon Standard Generalized Markup Language (SGML) and a product of the World Wide Web Consortium (W3C) As a markup language, it makes use of tags and attributes just like HTML HTML defines what the tags and attributes mean, XML uses tags only to delimit pieces of data and leaves the interpretation of data to the application XML is not a programming language XML doesn’t define actions, perform calculations, or make decisions XML DOES describe information (text or data) and defines how it should be processed

Slide 4: 

Why is XML a Powerful Tool? Value Proposition It’s platform or vendor independent. It doesn’t have to be unique for each different type of program which will be using it (e.g. there’s not XML for Java, XML for C++, etc.) Allows web-based applications to share information regardless of the language in which the applications are programmed Forms a basis for individuals to agree upon and manage shared data within and across communities of interest It’s the foundation for Web Services

Slide 5: 

XML Basics XML is a building block for data and, potentially, process standardization Standard schemas are being defined around communities of interest and within enterprises An XML Registry is a service that manages the storage and validation of “standard” XML schemas, components and or DTD’s. The registry service interacts with the Repository XML is a key driver of Web Services Web services focus on shared application processes across the internet XML is leveraged to describe the data that these processes “publish” and “consume”

Slide 6: 

Components of XML Schema Essentially a contract between multiple parties that describes the data and document structure. A schema can be used to perform content validation, as well as guide data management and collaboration efforts for structured and unstructured data Metadata Data that defines or describes other data is known as metadata. There is a proliferation of metadata usage today with the advent of content management systems and XML artifacts <?xml version="1.0" encoding="UTF-8"?> <OurDataExchange> <HeaderInformation> <SubmissionDate>2003-02-26</SubmissionDate> <TransactionIdentifier>526XYZ</TransactionIdentifier><SubmitterIdentifier>13579</SubmitterIdentifier></HeaderInformation> <DetailInformation><ReportingPeriod>4Q 2001</ReportingPeriod><ReportingFrequency>Daily</ReportingFrequency><!--...more elements here...--></DetailInformation><!--...more elements here...--></OurDataExchange> XML Example

Slide 7: 

DTD’s (Document Type Definitions) Defines what you’re presenting. It’s a formal description of a particular type of document (for example, the description for the PO document) Defines elements, attributes, and entities to be used and how they fit together. Using the PO example, this is where you would define ‘Ship To’, ‘Bill To’, and all the components parts of that element. For example, the ‘Ship To’ is composed of the name, street, city, state, zip, and country Stylesheets Define how you’ll render (or display) the information you’re presenting. The 2 primary forms of Stylesheets are CSS (Cascading Stylesheets) and XSL (eXtensible Style Language) Components of XML (Continued)

Slide 8: 

Commercial Evolution XML is the basis for most eBusiness COTS packages 1998 TODAY Commercially, XML has matured into a formally and widely adopted eBusiness development standard. COTS vendors have now begun to expand on the interoperability that XML facilitates which is automatic Web services discovery

Slide 9: 

Current Efforts Across the “Federal” Landscape XML.gov Mitre/DoD DLA EPA State Network Global Justice Network (DOJ) OMB Activities E-Government initiatives

Slide 10: 

Current Efforts Across the “Federal” Landscape XML.gov Activities: The members of XML.gov are composed of Federal, private-sector, and vendor communities who are interested in fostering the use of XML in the Federal environment. Under the auspices of this group, a government-wide XML registry/repository was created. They also sponsor the XML Working Group and the XML Registry/Repository Working Group Value Contribution: Performs education and marketing of XML in the Federal space. Provides a cost-free and relatively risk-free environment for government agencies to begin use of an XML registry EPA State Network Activities: Registering XML objects in the prototype Federal XML registry. Beginning to look at registering web services Value Contribution: Using the registered common XML elements will allow state agencies to provide required reporting information to the Federal level electronically and in a consistent and proper format. It will also allow the EPA to share transactional information within the agency

Slide 11: 

Current Efforts Across the “Federal” Landscape… cont’d DLA Activities: Created an ebXML registry to manage XML Schemas related to logistics and supplier management Value Contribution: Will facilitate a standard data exchange format through which suppliers and DLA can transact business. Mitre/DoD Activities: Creating a registry of XML meta-data elements, DTDs, and schema definitions Value Contribution: Defining these XML objects will allow for visibility and reuse of DOD-specific elements. This data definition will also allow for appropriate identification and sharing of information across a large and complex agency network. Will reduce cost, risk, and implementation schedules for the DOD

Slide 12: 

Current Efforts Across the “Federal” Landscape… cont’d Global Justice Network (DOJ) Activities: (1) US Courts: Creating an object-oriented XML data dictionary for the Court system and (2) Office of Justice and Programs (grant making arm): legal meta-data description Value Contribution: (1) Will allow the US Courts to file cases electronically although each of the regional Justice offices uses different web-based filing systems. Will also provide a data standard as none currently exists. Will provide a framework for intelligence and state and local law enforcement agencies to share electronic information with the DOJ. (2) Will allow grant data interchange and system interoperation. It will marry XML meta-data and legal documents OMB Activities Activities: (1) Developing the Federal Enterprise Architecture that will include the Data and Information Reference Model. (2) Expressing the OMB 300 as an XML Schema. Value Contribution: (1) Will begin to standardize the use of XML Objects across Government. (2) Will lead to increased usage of XML and increased efficiencies in processing budget requests.

Slide 13: 

Key Components of an XML based coordination strategy Data Coordination requires a set of building blocks to be in place, including: Interoperability Standards (e.g., ebXML, web services and component based standards) Well Defined Communities of Interest Subject Matter Experts Working Groups (e.g., Electronic Standards Work Group) Common Vocabularies A registry/repository capability to facilitate re-use A federated governance and management model to ensure interoperability Policy and committed participation

Conclusion : 

Conclusion The internet has challenged government (and business) to become collaborative organizations that reach across boundaries. Success will be measured by who integrates best. XML and Web Services are well positioned to handle complex integration challenges Loosely-coupled and asynchronous to preserve investments and enable new work flows Coarse grained to ensure a business services based approach XML and Web services offer a compelling value proposition Standards are maturing and well supported Products and standards groups are converging, rather than diverging Adoption is increasing New services are emerging today that will extend the web services stack and enable more widespread adoption outside of the enterprise Global XML Web Services Architecture provides much needed application services for robust application design