eXtensible Mark-Up Language (XML)

1. eXtensible Mark-Up Language (XML) Enabling the exchange and integration of business information Virginia, April 2002

2. The CCRA XML Experience • CCRA Context • Current status • Proposed strategy • Strategic and tactical streams • Examples • Internal initiatives • Cross government initiatives • Partnering opportunities • What we have learned to date • Our next steps

3. XML - the CCRA context • XML offers CCRA: • Improved sharing of information and standardized information • Reduced costs and faster development • Improved security • What are some of our challenges? • External pressures from: • Other departments and international partners • Banks and large corporations • Evolving standards • Internal pressures • Expertise • Application of knowledge • Uncoordinated and inconsistent approach to XML projects in the past

4. Current status • Externally: • Participating in initiatives across Government of Canada • Engaging other governments (provincial and international) and partners • Monitoring XML standards activity • Influencing standards • Developing strategies for incorporating XML within CCRA • Internally • Developing an enterprise approach • Approaching from information, technology and integration perspectives • Defining strategic and tactical initiatives • Undertaking pilots and proof of concept within the enterprise approach • Examples of current projects and short pressures • Using a task force to flesh out this approach

5. CCRA proposed XML strategy • Two streams • Strategic • Long term growth opportunities • Tactical • Immediate needs and pressures (tools, projects, etc.) • Defining our approach • Information (content) • Business and corporate • Infrastructure (packaging or containers) • Technology • Integration and application

6. Strategic • Information (content) • Define processes and procedures surrounding naming • Define how the registry and repository will be managed • Declare standards and establish center of expertise • Validate business infrastructure and needs • Common data model • Information Life Cycle principles • Technology (container) • Establish development processes and practices • Establish technical infrastructure and needs • Establish technical centers of expertise • Integration • Discover needs and processes • Establish standards

7. Tactical • Support current and immediate projects • Learn and evolve • Prove the concepts • Information (content) • Consolidating existing tag names and identifying attribute needs from business drivers • Defining semantics; descriptors, creating tags (using existing EDI as a basis) • Technology (container) • Evaluating existing tools in use • Determining tool categories and candidate tools • Selecting and implementing tools • Integration • Ensuring content and container standards work together (process) • Example: Do we use an XML native database or relational database for registry/repository?

8. Internal initiatives • Integrated Product Index (IPI) • Corporate Financial Systems (EISO) • Mag Media • Benefits Program Electronic Reports • Child Credit Program • Provincial partners and other government departments • Future Projects • Enterprise document management • Decision support / performance measurement

9. Cross government initiatives • Streamlining Service Delivery Using E-forms (SSDUE) • Proof of concept with RCMP, Health, Police, and Customs using XML to replace paper forms for drug seizures • Electronic Supply Chain • With Public Works and Government Services Canada • Integrated Justice Initiative (RCMP) • With the RCMP working on defining modeling and tagging • Other provinces • Business Number (BN) links

10. Partnering opportunities • Canadian Institute of Chartered Accountants • Discussions surrounding XBRL • House of Commons Prism project • Tagging standards • Sharing experiences with International Customs and Tax Organizations

11. What we have learned to date • It’s all about the business… • XML is 80% business and information management and 20% technical. • We need clear long term and short term plans • We need to partner with others and leverage their learning • Different standards require different approaches / leads • Business languages • Partners/International • Defining our information / requirements • Enterprise focus is required (strategic and tactical) • Knowing when we should use XML (and when we shouldn’t).

12. Next steps • Continue to seek out opportunities for collaboration • Internationally • Domestically • Action our proposed XML strategy • Position our organization appropriately • Pilot projects and proof of concepts • Continue to monitor and influence standards

13. Questions? www.ccra-adrc.gc.ca