XML.Gov Registry Business Case Suggestions

1
XML.Gov Registry Business Case Suggestions

• Brand Niemann
• XML Web Services Solution Architect
• US EPA Office of Environmental Information
• July 17, 2002

2
Overview

• 1. Interview with BAH
• 2. Additional Comments
• 3. XML Schemas and Relational Databases
• XMLSpy 4.4 and Oracle 9i Support
• Oracle XML DB
• 4. Access XP (2002)
• Access Database Linked to Excel
• Export Access Database to XML Files
• Web Services Toolkit
• 5. Pilot XML Registry and Repository
• 6. Contact Information

3
1. Interview with BAH

• 1. I have done and am doing an XML Registry and
  Repository.
• See paper for UNEP Conference in August 2000 and
  PowerPoint presentation for our EPA-State Network
  meeting in June 2002.
• At this meeting, the states expressed
  dissatisfaction with the progress and quality of
  the EPA-NIST Registry Pilot and suggested looking
  at my approach which we will be doing in our
  revised work plan for this effort.
•  2.  I advocate that XML Registries and
  Repositories be distributed XML Web Services and
  be an integral part of XML-based content networks
  of which they are a logical and essential part.
• In other words, every piece of content in a
  distributed content network can and should have
  metadata (RDF, XSD, etc.) depending on the nature
  of the content and its functions.
•  3. XML Registries and Repositories need to be
  populated by XML experts using professional XML
  tools like XML Spy, Canon Developer Portal, etc.
  which is not a trivial task.
• The process of populating an XML R/R teaches more
  about what the XML R/R needs to do so it is an
  iterative process. One doesn't just "build" an
  XML R/R and say okay now we are ready to populate
  it with what everyone has - the content of the
  XML R/R dictates the evolving design.
• Terry Bjornsen, Booz-Allen Hamilton, July 12,
  2002.

4
1. Interview with BAH

• 4. My experience with working with our regional
  and state partners in building a national
  environmental information exchange network has
  strongly influenced my views on this subject.
• For example, this past week I spent three days
  providing XML Web Services training and advice to
  the West Virginia Department of Environmental
  Protection on how to XML-ize their content from
  RDBMS-to-XML and from XML data collection back to
  RDBMS and we had what I would call a
  "breakthrough experience". We connected XML Spy
  4.4 to their large Oracle database and generated
  on the fly the XML Schema for over 600 tables in
  that databases in less that 30 seconds!
  We then demonstrated how XML Spy can generate XML
  instance documents of any and all of those data
  tables based on the Schema. These XML Schema and
  instance documents are what they need to exchange
  with EPA and other states and organizations. Knowi
  ng that these XML documents can now be readily
  exchanged publicly of course prompted some
  discussion of the need to reformat some of the
  Oracle tables and standardize the XML tag names,
  etc., but those are the details. The Oracle 91 R2
  just released claims to have a built-in XML R/R
  which I suggested that the WVDEP and we
  investigate and http//otn.oracle.com/tech/xml/xml
  db/
• Terry Bjornsen, Booz-Allen Hamilton, July 12,
  2002.

5
2. Additional Comments

• Registries describing and pointing to business
  services (i.e., web services) offer higher value
  than registries that provide only XML definitions
  and classifications (i.e., XML Schemas). (BAH at
  XML.Gov on June 16th)
• The content of XML Registries and Repositories is
  both document-oriented and database-oriented
  (Designing XML Databases, Mark Graves, Prentice
  Hall PTR, 2002).
• The fact that the content of RDBMS will change,
  and the so will their related XML Schemas, etc.,
  suggests the need for distributed Registries and
  Repositories to simplify the updating process.
• XML Registries and Repositories built upon
  interoperable XML Web Services will facilitate
  the integration and harmonization of Registries
  and Repositories built on multiple standards (ISO
  11179, ebXML, etc.).

6
3. XML Schemas and Relational Databases XMLSpy
4.4 and Oracle 9i Support

• Altova has teamed up with Oracle to integrate
  support for Oracle XML Schema Extensions -
  introduced in Project XDB, the native XML
  database in the Oracle 9i version - into the
  graphical XML Schema editor, which is part of the
  XML Spy Suite.
• XML Spy already includes full support for Oracle
  9i data access in the current 4.4 version of XML
  Spy Suite through the extensive Database
  Import/Export interface. This includes import and
  export of data between XML documents and
  relational tables, as well as converting a
  relational database schema into an XML Schema
  document on the fly.

7
3. XML Schemas and Relational Databases XMLSpy
4.4 and Oracle 9i Support
8
3. XML Schemas and Relational Databases XMLSpy
4.4 and Oracle 9i Support

• You can either choose a database table to be
  imported from a list, or enter any arbitrary
  SELECT statement to create the record-set you
  intend to import.
• You can again preview the data and choose
  different attribute or element assignments for
  each column before you start the actual import
  process.
• XML Spy allows you to choose different
  representations for date and number formats -
  depending on whether you intend to use the
  resultant XML file in conjunction with the new
  unified datatypes proposed by the most recent XML
  Schema draft or if you want to keep those formats
  corresponding to the locale in use in your
  country.
• Combine this with the Schema Generation function
  and you immediately get all the datatype
  information you need from your database into your
  XML documents.

9
3. XML Schemas and Relational Databases XMLSpy
4.4 and Oracle 9i Support

• Enable Oracle Schema extensions
• XML Spy provides preliminary support for Oracle
  schema extensions for use with "Project XDB".
  Using these extensions will allow you to
  configure and customize how the Project XDB
  version of Oracle 9i, will store XML documents
  internally. These XML documents are then
  accessible from an XML perspective as well as
  through SQL queries and legacy tools. Please see
  the Oracle.com website for more information
  (http//otn.oracle.com/tech/xml/xmldb).
• Selecting this menu option inserts an
  Oracle.com/xdb namespace into the schema file and
  makes an Oracle tab available in the Details
  entry helper. Oracle extensions can be defined
  for elements, attributes and complex types. Use
  the entry helpers to define the schema settings
  in the same was as you normally would with XML
  Spy.
• Please note
• Disabling this menu option deletes all the Oracle
  schema extension information from your schema
  file. A warning message appears, allowing you to
  reconsider. Confirming this action with OK,
  deletes all the info. This action cannot be
  undone!
• Oracle Schema settings This command allows you to
  define the global settings for Oracle schema
  extensions. You have to have previously enabled
  the Oracle schema extensions, using the menu
  option "Enable Oracle schema extensions", to be
  able to access this menu option.

10
3. XML Schemas and Relational Databases Oracle
XML DB

• Introduction
• Oracle XML DB is a feature of Oracle9i Database
  Release 2. It provides a high-performance, native
  XML storage and retrieval technology available
  with Oracle9i Release 2. It fully absorbs the W3C
  XML data model into the Oracle9i Database, and
  provides new standard access methods for
  navigating and querying XML. With Oracle XML DB,
  you get all the advantages of relational database
  technology plus the advantages of XML.
• Recent Papers and Articles
• Oracle XML DB Uniting XML Content and Data
  (Seybold Consulting Group, March 2002)
• Oracle XML DB Frequently Asked Questions
• Oracle XML DB Technical White paper
• Oracle XML DB Key Features in Oracle9i Database
  Release 2
• http//otn.oracle.com/tech/xml/xmldb

11
3. XML Schemas and Relational Databases Oracle
XML DB

• Oracle XML DB is a high-performance, native XML
  storage and retrieval technology available with
  Oracle9i Database Release 2. It fully absorbs the
  W3C XML data model into the Oracle9i Database,
  and provides new standard access methods for
  navigating and querying XML. With Oracle XML DB,
  you get all the advantages of relational database
  technology plus the advantages of XML
  technology. 
• Oracle XML DB is a set of  features in the
  Oracle9i database server that encompass both SQL
  and XML in a highly interoperable manner. It is
  not a separate server. Oracle XML DB adds a
  native XML repository to the database.
• The XML data-model encompasses both unstructured
  content and structured data. Oracle XML DB
  provides new capabilities for both
  content-oriented and data-oriented access. For
  developers who see XML as documents (news
  stories, articles, etc.), Oracle XML DB provides
  an XML repository accessible from standard
  protocols and queryable from SQL. see Figure 1
  in next slide
• For others, the structured-data aspect of XML
  (invoices, addresses, etc.) is more important.
  For these users, Oracle XML DB provides a native
  XMLType, support for XML Schema, XPath, XSL-T,
  DOM, etc. The data-oriented access see Figure 2
  in second next slide is typically more
  query-intensive.

12
3. XML Schemas and Relational Databases Oracle
XML DB
Figure 1 Content-Oriented Access
13
3. XML Schemas and Relational Databases Oracle
XML DB
Figure 2 Data-Oriented Access
14
3. XML Schemas and Relational Databases Oracle
XML DB

• As the amount of XML information grows,
  enterprises are looking at efficient ways to
  manage XML. Oracle XML DB introduces native XML
  storage in the Oracle9i Database, with support
  for the XML Schema data model, as well as other
  popular XML standards such as XPath for
  traversal, XSL-T for transformation, DOM SAX
  for programmatic access, and so on. XML data
  stored in the server naturally raises the
  question of queries. Two of the most popular
  standards that are emerging for querying XML are
• SQL/XML defined by specifications prepared by
  the SQLX group and submitted to the US standards
  body, INCITS H2
• XQuery defined by the W3C XML Query Working
  Group
• Oracle is an active participant in both working
  groups.
• Oracle XML DB supports SQL-style queries, in
  which users can use XPath notation to 'step into'
  XML documents. This style of querying, known as
  SQL/XML, is being standardized by the SQLX group.
  SQL/XML is an extension to SQL -- using functions
  and operators -- to include processing of XML
  data in relational stores. Oracle XML DB is the
  first implementation of SQL/XML.

15
3. XML Schemas and Relational Databases Oracle
XML DB

• The W3C is deliberating on an XML-only query
  language, called XQuery (also known, in
  conjunction with XPath, as "XML Query"). This
  standard addresses XML queryability from a
  pure-XML standpoint. XQuery queries XML wherever
  it may be - in databases, files, messages and so
  on. XQuery is not yet a standard (W3C calls it a
  "recommendation") - it is still in the Working
  Draft stage. Though there is no published
  schedule, the complete recommendation can be
  expected in late 2002 or early 2003. Oracle is
  also implementing XQuery. An early prototype is
  provided below to give you some feel for XQuery
  syntax. 
• We expect SQL/XML will be immediately important
  for enterprises with structured and
  semi-structured data, which needs to interoperate
  with various enterprise (SQL) reporting tools,
  relational data stores, transactional middleware,
  and so on. If your organization uses SQL today,
  Oracle XML DB will give you native XML
  capability, and SQL/XML implemented in Oracle XML
  DB will be the standard way to query your XML
  data. 
• XQuery is an emerging standard for a 'pure XML
  world'. It is most relevant when all your data is
  XML, and you are able to consume (for display or
  other processing) XML elements and attributes
  returned from queries. While XQuery is still
  evolving, for the XML developer the prospect of
  such a query language is very exciting! In this
  new world, Oracle will continue to provide the
  most robust, secure, scalable way to store and
  manage all your data, including XML. 
• Oracle prides itself on being the premier
  implementor of popular standards, and Oracle's
  implementation of XML standards are already
  helping developers build rich, loosely-coupled,
  content- and data-oriented applications.

16
4. Access XP (2002)Access Database Linked to
Excel

• Source Chapter 3. Getting Information Into and
  Out of a Database, Step by Step Microsoft Access
  2002
• Best practices
• Link to other databases rather than import so can
  view and edit in both systems.
• Share databases by exporting to XML (universal
  format).
• http//office.microsoft.com/assistance/2002/articl
  es/acExOfScenariosUsingXML.aspx
• Import
• Open Access 2002 database.
• File, Get External Data, Import, Files of type,
  XML Documents, Import both XML and XSD, select
  file to be imported, Import, Import XML, Options,
  Structure and Data, Okay.
• Open and view database tables to confirm data was
  imported.

17
4. Access XP (2002) Access Database Linked to
Excel
18
4. Access XP (2002)Export Access Database to XML
Files
19
4. Access XP (2002)Web Services Toolkit

• The Microsoft Office XP Web Services Toolkit
  brings the power of Web services to Office XP
  solutions by enabling developers to discover and
  integrate Web services into Office XP solutions.
  From directly within the Microsoft Visual Basic
  for Applications (VBA) editor, developers can use
  the UDDI registry, an open, standard-based .NET
  Web Service, for discovery of available Web
  services, searching by keywords or businesses.
• The toolkit contains comprehensive documentation
  on discovering and integrating XML Web
  servicesincluding technical white papers on
  using XML Web services within your custom Office
  XP solutions, as well as samples that illustrate
  XML Web services integration and provide real
  examples on how XML Web services can be
  integrated into custom Office XP solutions using
  Microsoft Excel and Microsoft Word.
• Contents
• Calling XML Web Services from Office VBA Using
  the Web Service References Tool
• Calling XML Web Services over the Web Using the
  Web Service References Tool and Microsoft Access
• Checking Book Prices over the Web Using the Web
  Service References Tool and Microsoft Outlook
• Checking Stock Quotes over the Web Using the Web
  Service References Tool and Microsoft Excel
• Handling Complex SOAP Data Types in XML Web
  Services
• Unlocking Office XML Data Through the XML
  Document Object Model
• For an introduction to the Office XP Web Services
  Toolkit, take the Web Services Toolkit Tour.
• http//msdn.microsoft.com/library/default.asp?url
  /library/en-us/dnxpwst/html/odc_wstoolkitoverview.
  asp

20
5. Pilot Registry and Repository

• Concepts for pilot
• XML registry and repository should be an integral
  part of a distributed XML-based content network.
• Tools like XML Spy and Canon Developer Portal are
  needed to support content of an the XML registry
  and repository.
• Data dictionaries and data element harmonization
  results should also be included in the XML
  registry and repository
• Scope of the pilot
• XML Spy documentation (461 pages) and 97 files of
  general documentation (3), Schemas (47), and
  Schema documentation (47) totaling 12.6 MB.
• Used XML Spy to create documentation (Word) and
  used NXT 3 to create a registry and repository
  node on the Environmental Node of the FedGov
  Content Network.

21
4. XML Registry and Repository
22
4. XML Registry and Repository
23
6. Contact Information

• Brand Niemann, Ph.D.
• USEPA Headquarters, EPA West, Room 6143D
• Office of Environmental Information, MC 2822T
• 1200 Pennsylvania Avenue, NW, Washington, DC
  20460
• 202-566-1657
• niemann.brand_at_epa.gov
• EPA http//161.80.70.167
• Outside EPA http//130.11.44.140