1. IRS XML Content Meta-Data Management

2. Key Enterprise ContentMeta-Data Components • Content Meta-Data Model • Meta-Data Tagging Tool • Collaborative Templates

3. 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.)

4. 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

5. Content Management Meta-Data Model Demonstration

6. 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

7. 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

8. Metasoft Demonstration

9. 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

10. 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

11. 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

12. 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

13. Issues • Developing Enterprise vocabularies and taxonomies – major socialization process • Need a quick and efficient Enterprise process to extract taxonomies when and wherever they occur