Slide 1Copyright 2003 Inera Incorporated. All Rights Reserved Using XML Presented by Bruce D....

Copyright 2003 Inera Incorporated. All Rights Reserved

Using XML

Presented by

Bruce D. Rosenblum

CEO

Inera Incorporated

InfoToday – May 7, 2003


DOI Stands For...


DOI Stands For... Digital Object Identifier


DOI Stands For... Digital Object Identifier Dusty Old Issue


DOI Stands For... Digital Object Identifier Dusty Old Issue Death Of Ink


500 Years of Ink on Paper

Gutenberg Oldenburg Linotype Photon PostScript


Enter XML SGML (1985)

Application-independent electronic documents

HTML (1991) Computer-independent screen rendering

XML (1998) Application-independent electronic documents Application-independent data Computer-independent communication


What XML Is and Does XML is a meta language XML drives workflow XML drives the business processes XML drives new products XML drives new knowledge


XML Is Not Easy XML requires

New workflow New tools New training


Key considerations Management support Financial investment

Team Tools Testing


Using XML Design Develop Implement

Pilot Broader rollout

Refine Version 1.1 Version 2.0


Design: Business Business requirements

Define business objectives Build the ROI case Management support

Personnel requirements In-house or outsource production Training


Elsevier DTD: Pure Content Print Version

Neutra, R., Shusterman, D. (1991) Hypotheses to explain the higher symptom rates observed around hazardous waste sites. Environmental Health Perspectives 94, 31–38.

Elsevier DTD <bib id="bbib7"><no>Neutra and Shusterman 1999</no><bb><contribution><authors> <author><snm>Neutra</snm><fnm>R.</fnm><author><snm>Shusterman</snm><fnm>D.</fnm> <title>Hypotheses to explain the higher symptom rates observed around hazardous waste sites.</title> <host><issue><series><title>Environmental Health Perspectives<volume-nr>94<date>1991 <pages><first-page>31<last-page>38</bibl>


Blackwell DTD: Society Style Print Version


Blackwell DTD<bb id="b7"><jnlref>

<au><snm>Neutra</snm><x>, </x><fnms>R.</fnms></au><x>, </x>

<au><snm>Shusterman</snm><x>, </x><fnms>D.</fnms></au><x> (</x>

<cd year="1991">1991</cd><x>) </x><tl>Hypotheses to explain the higher

symptom rates observed around hazardous waste sites.</tl><x> </x>

<pubtl>Environmental Health Perspectives</pubtl><x> </x><vid>94</vid><x>, </x>

<ppf>31</ppf><x>–</x><ppl>38</ppl><x>.</x></jnlref></bb>


Highwire DTD: Just The Links Print Version


Highwire DTD<bib id="b7"><other-ref>Neutra, R., Shusterman, D. (<date>1991</date>)

Hypotheses to explain the higher symptom rates observed around hazardous waste sites.

<title>Environmental Health Perspectives</title> <volume-nr>94</volume-nr>,

<first-page>31</first-page>–38.</other-ref></bib>


UCP DTD: Easier Editing Print Version


UCP DTD<CITATION ID="rf7" URI="9683608" URI-STATUS="RESOLVES" BIBCODE="9683608" BIB-STATUS="LINKS">

Neutra, R., Shusterman, D. (1991) Hypotheses to explain the higher symptom rates observed

around hazardous waste sites. <ITAL>Environmental Health Perspectives</ITAL>

<BF>94</BF>, 31–38.</CITATION>


Design: DTD Selection Industry-specific DTDs

Less restrictive Subject to multiple interpretations Adaptable to business requirements of multiple organizations E.g., Docbook, NLM/Mellon

Organization-specific DTDs More restrictive Designed to optimize publisher production activities Reflect unique business requirements of owning-organization E.g. Elsevier Science, Blackwell


Design: DTD Modification To meet

Technical requirements

Which are driven by Business requirements Document Analysis

The quick and dirty analysis problem

Don’t forget samples and documentation “It’s not done until it’s documented”


Implement: Software Out-of-the-box solutions are snake-oil Select software based on

Workflow requirements Customization capabilities

Customize wisely The amateur programmer problem


Implement: Rollout Pilot implementation

Small team Evangelists Identify and fix problems

Gradual rollout The “shock therapy” problem


Implement: Quality Assurance Good XML requires

Constant quality assurance Integrated quality checks Multi-stage quality checks

The Elsevier quality solution


Refine Version 1.0 is never perfect Version 1.1 is better Don’t be afraid of version 2.0

Remember: Business requirements change The copy edit accuracy problem The electronic manuscript problem


Resources XML information

http://www.oasis-open.org http://www.xml.com

Publishing DTDs NLM Mellon (http://dtd.nlm.nih.gov) Docbook (http://www.oasis-open.org)

Publishing metadata CrossRef (http://www.crossref.org) Onix (http://www.bisg.org/)


Conclusions XML is not just about tags XML is about

Business requirements Careful design and implementation Built-in quality assurance Ongoing re-evaluation and improvement


Questions?

Bruce RosenblumInera Incorporated+1 (617) 969 - 3053

[email protected]

Slide 1Copyright 2003 Inera Incorporated. All Rights Reserved Using XML Presented by Bruce D....

Documents

Transcript of Slide 1Copyright 2003 Inera Incorporated. All Rights Reserved Using XML Presented by Bruce D....