iECM Briefing: XML Community of Practice

1
iECM Briefing XML Community of Practice

• Betsy Fanning
• AIIM

2
About AIIM Standards

• ANSI Accredited
• ISO TC 171, Document Management Applications
  Secretariat
• ISO TC 171, Document Management Applications,
  SC2, Application Issues Secretariat
• U. S. TAG (Technical Advisory Group) to ISO TC
  171 Administrator
• Industry Standards Developer AIIM Recommended
  Practices (ARP)
• Open Source Standards for Document Management
• Liaison Relationships

3
AIIM Standardization Work

• Micrographics
• Digital Imaging
• Document Management
• Workflow
• Legality Issues
• Metadata
• XML
• Integrated EDM/ERM Functional Requirements
• PDF
• iECM

4
PDF/Archive Success Story

• October 2002 Initial meeting of AIIM/NPES PDF/A
  committee
• April 2003 Initial Working Draft (WD)
• August 2003 New Work Item (NWI) approved and
  Joint Working Group (JWG) formed
• December 2003 First Committee Draft (CD) approved
• September 2004 Second CD approved
• June 2005 Draft International Standard
  (DIS) unanimously approved
• September 2005 Published

5

• There is a need to find, access (read/write),
  aggregate, and report on information that is
  stored in data stores implemented on a variety of
  platforms, making data available through a
  variety of means, and controlled by a variety of
  applications. Notification of new information
  relevant to a particular topic of interest is
  also a common theme.

6
The Pain Points

• Knowledge of data stores.
• Access through individual applications and/or
  proprietary mechanisms.
• Varying data formats (files and metadata) and
  taxonomies.
• A variety of different security protocols are
  used for authentication, authenticity, directory
  services, etc.
• Creation of an aggregated set of information is
  difficult due to many of the items noted above.
• There is often a need to alert the user (or
  consuming system) that previously retrieved
  content objects (documents, files, etc.) have
  been changed since they were retrieved. The
  content object's metadata may also have been
  changed relevant to a prior search (e.g. in such
  a way as to make the retrieved document no longer
  a member of the same search results.)
• Moving content from one repository to another.
• Repository synchronization (even if one-way only)

7
iECM Simple Idea
and we have applications
And the applications dont want to talk
differently to each store!!
We have content stores
8
Mission/Vision Statement

• Interoperable Enterprise Content Management
• iECM will create an interoperability framework
  that enables information sharing across
  organizational and system boundaries.

9
iECM Charter

• The iECM Consortium will
• Inform and assist stakeholder communities in
  challenges of content management
• Responsible for developing and maintaining an
  architecture
• Endorse existing standards
• Collaborate with standards organizations to
  enhance applicable existing standards
• Develop standard where no standards exist

10
Reference Model

• iECM Services Model
• Set of common content management functions
  (document transfer, check-in/out, etc.)
• iECM Domain and Metadata Model
• Normalization of information that flows through
  the services model (files, folders, metadata,
  etc.)
• iECM Component Model
• Schema describing the entities of a content
  management ecosystem (Services model, Domain and
  Metadata model, access mechanisms, protocols, and
  repositories)

11
iECM Communities of Interests

• Enterprise Consumers
• Fortune 1000 Reduce Complexity, Cost. Increase
  control and access to corporate information
  assets
• Government Agencies 85 of budget only manages
  15 of data.
• System Integrators Risk mitigation in deploying
  enterprise ECM systems
• Manufacturers and VARs
• SDOs and Industry Groups (FSTC, Domea, Open
  Group, and others)

12
Organizational Structure
13
Timeline

• May 2005 Initial Meeting
• September 2005 Washington, DC Organizational
  Meeting
• October 2005 Initiated weekly conference calls
• November 2005 New York City Scope and
  Outreach
• December 2005 Draft Scope Internal approval
• January 2006 Redmond, WA
• March 2006 Boulder, CO
• May 2006 Philadelphia AIIM 2006
• October 2006 Reference model
• January 2007 Architecture

14
How to Join

• Following AIIM Standards Development Process
• Email intent to participate
• Listserv
• Wiki
• Membership Agreement
• Agencies 2,500
• Departments 7,000
• Individual 250
• Weekly Conference Calls
• 1-888-742-8686 or 1-303-928-2600
• Conference ID 5291291
• Technical Committee Fridays at 11 a.m. Eastern
• Outreach Committee Fridays at 245 p.m. Eastern

15
Where to get more information

• AIIM Web Site www.aiim.org
• AIIM Standards Page www.aiim.org/standards
• iECM Wiki http//iecm.editme.com
• DOC.1 weekly email service
• AIIM E-DOC Magazine bi-monthly periodical
• Contact bfanning_at_aiim.org
  301-755-2682