# Presentation: 201906

## MANAGING 

- INFORMATIONRESOURCES
- USING XML
- AND CONTENT
- WORKSPACES

- A presentation to the
- CIO’s Council
- XML Working Group
*14 February 2001*

## THE CHALLENGE

- To put OMB A-0130 in XML, and to
- show how the XML can be used to
- improve the effectiveness of information
- resource management, as required by
- the policies set out in OMB A-130.

## STEPS TOWARDS A SOLUTION

- 1. Identify the target environment.
- 2. Develop the DTD.
- 3. Create and deploy the content.
- 4. Provide a framework for managing
-     the content life cycle and re-use.

## DOCUMENT-ORIENTATED XML APPLICATIONS

-   Transactional XML is more than
-    HTML Forms.
-   Document -orientated XML is more
-    than ‘super’ HTML. It could provide
-    a whole new way to manage content.

***Step 1. Target Environment***

## A DOCUMENT IS PART OF A NETWORK OF REFERENCES

_*A DOCUMENT IS PART OF A NETWORK OF REFERENCES*_

- OMB A-130

- USC

- CFR

- OMB

- OMB

- REFERENCE LINK

***Step 1. Target Environment***

## A DOCUMENT IS AN AGGREGATE OF INFORMATION COMPONENTS

- OMB A-130

*Authorities*

*Definitions*

*Policy *

***Step 1. Target Environment***

## THE COMPONENTS ARE THE DOCUMENT

- OMB A-130

*Authorities*

*Definitions*

*Policy *

- 1. The host document could
- be a shell with links to its
- components.

- 4. And some of these
- components themselves
- might be shells, with links ...

- CONTAINMENT LINK

***Step 1. Target Environment***

## A NEW VIEW OF CONTENT MANGEMENT

-  The unit of information content is
-    now the component.
-   A component may be text, graphics,
-    a spreadsheet, data from an RDBMS, or ...
-   A document is just another component
-    in a web of content.
-   How can component creation and re-use
-    be managed in this environment?

***Step 1. Target Environment***

## CONTENT SEMANTICS

-   XML provides the means to embed
-    content semantics using meaningful
-    tags and attributes.
-   XML can be used to ‘wrap’ non-text
-    information components.
-   The purpose of XML is to enable
-    computer programs to manipulate
-    both structure and content reliably.

***Step 1. Target Environment***

## THE USE OF CONTENT SEMANTICS

-   Dynamic, user-sensitive rendering.
-   Improved indexing and searching.
-   Reference links to create a
-    ‘*semantic web’* of content.
-   Containment links for component
-    re-use through ‘*virtual documents.’*

***Step 1. Target Environment***

## THE ROLE OF THE DTD

-  The DTD defines a ‘grammar’ for
-      a family of documents.
-   Valid XML requires a DTD.
-   Only valid XML ensures reliable machine
-       processing of the structure and content.

***Step 2. DTD Development***

- The DTD we have created for OMB A-130
- is only for the purpose of illustrating the
- major principles involved.  It is not intended
- to be a production-strength example.

## A DTD FOR OMB A-130

- <!ELEMENT omb (Header, Body)>
- <!ELEMENT Header (OMBCirc.Index, OMBCirc.Title?, OMBCirc.Date?,
-                                    OMBCirc.Subject, OMBCirc.Author?, Content.List)>
- <!ELEMENT Body (Section1*)>
- <!ELEMENT OMBCirc.Index (#PCDATA)>
- <!ELEMENT OMBCirc.Title (#PCDATA)>
- <!ELEMENT OMBCirc.Date (#PCDATA)>
- <!ELEMENT OMBCirc.Subject (para)*>
- <!ELEMENT OMBCirc.Author (#PCDATA)>
- <!ELEMENT Content.List (Content.List.Item+)>
- <!ELEMENT Content.List.Item (#PCDATA)>
- <!ATTLIST Content.List.Item
- 	PointTo CDATA #IMPLIED
- >
- <!ELEMENT bold (#PCDATA)*>
- <!ELEMENT italic (#PCDATA)*>
- <!ELEMENT underline (#PCDATA)*>
- <!ELEMENT title (#PCDATA)>
- <!ELEMENT para (#PCDATA | bold | italic | underline | ExtDoc)*>

_*A DTD FOR OMB A-130*_

***Step 2. DTD Development***

## A DTD FOR OMB A-130: use of attributes

- <!ATTLIST Section1
- 	Type CDATA #IMPLIED
- 	xflag CDATA #IMPLIED
- > <!ELEMENT Section2 (title?, (para | Section3)*)>
- <!ATTLIST Section2
- 	xflag CDATA #IMPLIED
- >
- <!ELEMENT Section3 (title?, (para | Section4)*)>
- <!ATTLIST Section3
- 	xflag CDATA #IMPLIED
- >
- <!ELEMENT Section4 (title?, (para | Section5)*)>
- <!ATTLIST Section4
- 	xflag CDATA #IMPLIED
- >
- <!ELEMENT Section5 (title?, (para)*)>
- <!ATTLIST Section5
- 	xflag CDATA #IMPLIED
- >

_*A DTD FOR OMB A-130: use of attributes*_

***Step 2. DTD Development***

## A DTD FOR OMB A-130: use of named elements

- <!ELEMENT Act (#PCDATA | Act.Section | Act.Name | Act.Alias | Act.Year |
-                                USCNumber | PublicLaw)*>
- <!ELEMENT ExecOrder (#PCDATA | ExecOrder.Section | ExecOrder.Num |
-                                           ExecOrder.Date)*>
- <!ELEMENT OMBMemo (#PCDATA | OMBMemo.Index | OMBMemo.Description)*>
- <!ELEMENT OtherOMBCirc (#PCDATA | OtherOMBCirc.Index | OtherOMBCirc.Subject)*>
- <!ELEMENT Act.Section (#PCDATA)>
- <!ELEMENT Act.Name (#PCDATA)>
- <!ELEMENT Act.Alias (#PCDATA)>
- <!ELEMENT Act.Year (#PCDATA)>
- <!ELEMENT USCNumber (#PCDATA)>
- <!ELEMENT PublicLaw (#PCDATA | PublicLaw.Title | PublicLaw.Range)*>
- <!ELEMENT ExecOrder.Num (#PCDATA)>
- <!ELEMENT ExecOrder.Section (#PCDATA)>
- <!ELEMENT ExecOrder.Date (#PCDATA)>
- <!ELEMENT OMBMemo.Index (#PCDATA)>
- <!ELEMENT OMBMemo.Description (#PCDATA)>
- <!ELEMENT OtherOMBCirc.Index (#PCDATA)>
- <!ELEMENT OtherOMBCirc.Subject (#PCDATA)>
- <!ELEMENT PublicLaw.Title (#PCDATA)>
- <!ELEMENT PublicLaw.Range (#PCDATA)>

_*A DTD FOR OMB A-130: use of named elements*_

***Step 2. DTD Development***

**BARRIERS:**
-   User resistance to change.
-   Training costs/learning curve.

***Step 3. Content  Creation***

_*CREATING & EDITING XML*_

**ONE APROACH:**
-   Train information creators in XML

**BARRIERS:**
-   On-going correction costs.

**ANOTHER APROACH:**
-   Apply XML after content creation

## AND ANOTHER APPROACH:TAGLESS EDITING

*i4i’s assault on the barriers to enterprise-wide*
*deployment of XML creation and editing tools...*
-   give the user a familiar interface:
- 	  Microsoft ® Word
-   hide the tags
-   play to the user's understanding
-       of the logic of the document

- FAMILIAR INTERFACE, SIMPLE PARADIGM

***Step 3. Content  Creation***

## Step 3. Content  Creation

***Step 3. Content  Creation***

## Step 3. Content  Creation

***Step 3. Content  Creation***

## Step 3. Content  Creation

***Step 3. Content  Creation***

## Step 3. Content  Creation

***Step 3. Content  Creation***

## S4/TEXT- TAGLESS EDITOR ARCHITECTURE

_*S4/TEXT- TAGLESS EDITOR ARCHITECTURE*_

**DTD**

**e-mail**

**XML **
**Instance**

**Microsoft® **
**Word **

**DataPipe Layer:**
***S4/TEXT***

**Application Layer:**
***Tagless Editor***

**Data Services Layer:**
***S4 and SP***

- Format
- Template

- Behavioral
- Instance

**Collaboration**
**Services**

***Step 3. Content  Creation***

## MANAGING CONTENT LIFE-CYCLE AND RE-USE

-   The web of content raises new problems:
- How can information creators understand the content web and manage their work?
- How are legacy resources included?

***Step 4. Managing Life Cycle & Re-use***

## CONTENT WORKSPACES

- A content workspace is a visual metaphor
-     representing the components for a task --
-     a browser is not enough.
- A content workspace is a product of the
-     metadata -- the tags, attributes and other properties, plus links, derived from the XML.
-  A content workspace is itself a virtual
-      document, supported by a metadata
-      server, while the actual content resides
-      elsewhere.

***Step 4. Managing Life Cycle & Re-use***

## Step 4. Managing Life Cycle & Re-use

***Step 4. Managing Life Cycle & Re-use***

## S4/ENTERPRISE ARCHITECTURE

_*S4/ENTERPRISE ARCHITECTURE*_

- File
- Server

- Content
- Mgt. Sys.

- Web
- Server

- RDBMS
- Server

- S4/ENTERPRISE
- Server(s)

**SOAP/HTTP/TCP/IP**

**S4/ENTERPRISE**
** ****CLIENT**

- S4/TEXT

- OTHER
- TOOLS

- P
- C

***Step 4. Managing Life Cycle & Re-use***

## SUMMARY

- XML can deliver a ‘semantic web’ of content.
- XML can be deployed enterprise-wide
-     without an army of markup technicians.
- XML can be deployed incrementally to
-     protect your current investment.
- As an open standard, your investment in
-     XML is protected.

## CONTACT US 

**By e-mail:****	****	****	****By  phone:**
- 	kthomas@i4i.com          (416) 504-1041 x202
- 	hjohnson@i4i.com	(416) 504-0141 x216
- 	jpoisson@i4i.com		(416) 504-0141 x294
**Visit our Web site:**
- 	www.i4i.com

## Tagless Editing Demousing OMB A-130