# Presentation: 655414

## IRS XML

- Content Meta-Data
- Management

**Notes:**
Welcome!  This is an overview of the implementation of XML as a tool to manage content within the IRS.  Progress and implementation issues are covered.

## Key Enterprise ContentMeta-Data Components

- Content Meta-Data Model
- Meta-Data Tagging Tool
- Collaborative Templates

**Notes:**
There are three key components to our effort.  The first is an extensible and flexible content meta-data model that can be used to universally tag business process content within the IRS.  The second is the development of a tool that will allow anyone to tag content in such a way that it can be discovered and located by anyone else in the Service and, where applicable, discovered and located by private citizens.  To extend this tool even further the plan also includes using Microsoft’s InfoPath application to extend the tool, making it easier for people to accomplish these goals.

## EDMO’s Enterprise Content Data Model - SCOPE

- Business Data
- Tax Returns/Submissions and Forms
- Planning Analysis and Decision Support Data
- Content or Procedures Management (How do I complete this task?  Does not include records or correspondence.)

**Notes:**
Currently, there are roughly four parts to the Enterprise Content Data Model.  There are Business Data, Tax Returns/Submissions and Forms, Planning Analysis and Decision Support Data and what we are calling Content Management.  The first three systems deal primarily with what is traditionally understood to be pure data.  This automated data processing approach has been around since the sixties and there is a great deal of stability around these processes.  Within the content management area, however, new processes like XML are motivating people to begin looking at processing document-based information in an automated fashion.  The focus of our efforts (and this presentation) then, is on the management of document-based content.  Correspondence is not included in this model, due to the complexity of tracking unique instances of this type of communication.  We are mostly focused on keeping track of trusted sources of knowledge and research information, usually of an e-learning, performance support or procedural perspective.

## Proposed ECDM Content Management Meta-Data

- Meta-data is based on SCORM, which is an extension of LOM and Dublin Core
- SCORM originally used to tag e-learning
- Highly extensible and flexible, adapting easily to IRS content

**Notes:**
The proposed method for meta-data tagging IRS content is based on SCORM, which stands for Sharable Content Object Reference Model.  SCORM is the reference model used to create e-learning and has been adopted as the standard for IRS e-learning.  The meta-data tagging portion of SCORM is taken from the IEEE Learning Object Metadata standard.  Both models are based on from the highly flexible Dublin Core meta-data tagging model.  The proposed process, therefore, should meet most of the needs of the Enterprise when it comes to discovering and locating knowledge and research information. 

## Content Management

- _[Meta-Data Model Demonstration](http://152.223.202.185/xmlspydoc/irsschema.html)_

**Notes:**
This model is essentially a deconstruction of the SCORM model and re-constructed to meets the needs of the Enterprise.  The key features of the model are:

Relating all content to it’s location in the IRM

Using the IRM and taxonomies to discover content

Using the container, object and asset computer model to aggregate content

Establishing the concept of a “trusted source and location” in the Enterprise culture

Combining the user profiles and marketing information to assist in designing targeted information

Most of the elements within the meta-data model are global elements.  Other information required by the BODs can be acquired through the extension of the model.

## Metasoft - Enterprise Meta Data Tool

- Used to successfully implement meta-data tagging in e-learning and now in performance support
- Evolving into a key resource to create meta-data Enterprise-wide
- Easily extensible to Enterprise level

**Notes:**
How do we implement the model?  We use a tool called Metasoft.  Metasoft is a utility that gathers all the meta-data information and wraps it in XML binding.  Wrapping this content in XML makes the information portable and non-proprietary.  Web services can be used to port the information in and out of Metasoft as required.  Global updates of information have already been demonstrated in the use of Metasoft.  The tool was originally designed and used to track SCORM data for e-learning purposes.  Version 2 of Metasoft has been generalized to accept all types of knowledge and research information.  The tool is a distributed information system which resides outside the firewall.  No OUO information is kept on the system, only identification and inside-the-firewall location information.  The tool is easily extensible to the Enterprise.  

## Aggregation Model

- Also based on SCORM
- Incorporates the universal “tree” structure – aggregation, content object, asset
- Permanent intranet location
- Tagging in this manner exponentially increases ability to locate and re-use content

**Notes:**
The potential of aggregating content within the Enterprise is exciting.  Designing content in a object-oriented fashion permits the Enterprise to take the individual objects and re-organize them into other versions of the content.  If the object itself is expressed in XML, the content can also be “reshaped” to fit different displays.  The movement of the IRM into an object-oriented XML format should be an Enterprise priority.  If the IRM were done in this manner, the Enterprise would be able to easily assemble all references to a particular IRM subject with a keystroke.  

## Metasoft

- _[Demonstration](http://www.digitalconcepts.com/metasoft_irs/)_

**Notes:**
Show:

IRM Taxonomic Structure

Pointers created by IRM location

Show keywords and tax map

Show objects by BOD

Search for content

Add content to package

Re-organize content

## Enterprise Collaborative Templates 

- InfoPath’s templates will facilitate the tagging of content
- Metasoft is the trusted source
- Create easily modified InfoPath templates
- Transmit the meta-data collected with InfoPath to Metasoft via web services

**Notes:**
The next step is to take the global aspects of the Metasoft tool and filter them so customers only deal with the information that’s relevant to them.  This is where Microsoft’s new application called “InfoPath” comes in.  InfoPath will be rolled out to the Enterprise when Office 2003 is delivered.  InfoPath will be able to take the IRS Content Management XML Schema (which currently resides on Metasoft) and customize it to the particular situation.  For instance, in some situations it may only be necessary to identify a content container with a title, description and URL.  In those cases, a simple InfoPath form with three elements might suffice.  The information is then uploaded to an Enterprise SharePoint Server which then sends it to the Metasoft trusted source repository.  This tailored approach will greatly simplify the process.

## Issues

- IRM structure should drive organization of all content in the IRS
- May require adoption of a new XML structure (OASIS LegalXML?)
- Namespaces will consolidate many stove-piped areas – major socialization process

## Issues

- Now – Content is process driven by BODs and process owners – leads to duplication of effort and updating nightmare
- Future – Content driven by content data model (MITS via BSMO/EDMO) – easily updatable trusted sources
- A “collision” is imminent

## Issues

- Office 2003 implementation will include InfoPath – Form OMB 300 is currently implemented
- Delays in Office 2003 and SharePoint delay Enterprise XML roll-out
- Need collaborative SharePoint server to implement Enterprise model

## Issues

- Developing Enterprise vocabularies and taxonomies – major socialization process
- Need a quick and efficient Enterprise process to extract taxonomies when and wherever they occur