xml without tears (j gollner at intelligent content 2012)
DESCRIPTION
This was a featured presentation at the Intelligent Content Conference in 2012.TRANSCRIPT
![Page 1: XML without Tears (J Gollner at Intelligent Content 2012)](https://reader033.vdocument.in/reader033/viewer/2022052618/554ba196b4c905b8618b4af1/html5/thumbnails/1.jpg)
Copyright © Joe Gollner 2012
XML
without
Tears
Joe Gollner, M.Phil.
Gnostyx Research Inc.
www.gnostyx.com
www.gollner.ca
@joegollner
Intelligent
Content
2012
![Page 2: XML without Tears (J Gollner at Intelligent Content 2012)](https://reader033.vdocument.in/reader033/viewer/2022052618/554ba196b4c905b8618b4af1/html5/thumbnails/2.jpg)
Background
Regulatory Agency for the Energy Sector managing:
• Regulations
• Process Documentation
• Submissions
• Public Consultation Outcomes
• Judgments
Pressures:
• Growing volume & complexity of regulations & submissions
• Growing complexity of the consultation process
• To bring costs under control or even reduce them
• Maintain or even shorten the process cycle times
Case Study: Regulatory Structured Content
![Page 3: XML without Tears (J Gollner at Intelligent Content 2012)](https://reader033.vdocument.in/reader033/viewer/2022052618/554ba196b4c905b8618b4af1/html5/thumbnails/3.jpg)
Three Key Ingredients
Top Tier Management Consulting Firm
• Conducted a comprehensive process review
• Collaborated with stakeholders to re-envision the future
Content Management Consulting Firm
• Facilitated a wide-ranging analysis & modeling activity
• Developed target content models with rich semantics
Content Management & Publishing Technology Vendors
• Engaged to tailor their tools to support
• The re-envisioned business process
• Fully customized authoring environments
• Sophisticated management & publishing services
Case Study: Regulatory Structured Content
![Page 4: XML without Tears (J Gollner at Intelligent Content 2012)](https://reader033.vdocument.in/reader033/viewer/2022052618/554ba196b4c905b8618b4af1/html5/thumbnails/4.jpg)
Case Study: Outcome
How do you think
this turned out?
![Page 5: XML without Tears (J Gollner at Intelligent Content 2012)](https://reader033.vdocument.in/reader033/viewer/2022052618/554ba196b4c905b8618b4af1/html5/thumbnails/5.jpg)
Case Study: Outcome
Disaster
![Page 6: XML without Tears (J Gollner at Intelligent Content 2012)](https://reader033.vdocument.in/reader033/viewer/2022052618/554ba196b4c905b8618b4af1/html5/thumbnails/6.jpg)
Over-indulgence in meaningful [semantic] markup
Insanely complex authoring experience
Insanely complex authoring tool customizations
Insanely complex authoring support tools
• Auto-complete
• Validation
• Packaging
Insanely complex processing scenarios [publishing]
Target vision disconnected from reality in key ways
Naively transgressed obvious legal boundaries
• Attempted to automate formatting submission after receipt
Generated unsustainable maintenance costs
What Went Wrong?
![Page 7: XML without Tears (J Gollner at Intelligent Content 2012)](https://reader033.vdocument.in/reader033/viewer/2022052618/554ba196b4c905b8618b4af1/html5/thumbnails/7.jpg)
Lessons Learned
<$ Element element-name >
Semantics come at a price and
must be associated with a concrete use
Standard Generalized Markup Language (SGML)
defined a Document Type Definition (DTD) as
[organizing] “rules defined by an application”
![Page 8: XML without Tears (J Gollner at Intelligent Content 2012)](https://reader033.vdocument.in/reader033/viewer/2022052618/554ba196b4c905b8618b4af1/html5/thumbnails/8.jpg)
Markup Considered Harmful
Theodor (Ted) Holm Nelson
Is there any value in using meaningful [semantic] markup?
Infrastructures for Information, Inc. and
![Page 9: XML without Tears (J Gollner at Intelligent Content 2012)](https://reader033.vdocument.in/reader033/viewer/2022052618/554ba196b4c905b8618b4af1/html5/thumbnails/9.jpg)
But You Said XML without Tears
![Page 10: XML without Tears (J Gollner at Intelligent Content 2012)](https://reader033.vdocument.in/reader033/viewer/2022052618/554ba196b4c905b8618b4af1/html5/thumbnails/10.jpg)
Copyright © Joe Gollner 2012
XML
without
Tears
Take Two
Intelligent
Content
2012
![Page 11: XML without Tears (J Gollner at Intelligent Content 2012)](https://reader033.vdocument.in/reader033/viewer/2022052618/554ba196b4c905b8618b4af1/html5/thumbnails/11.jpg)
+$
-$Formatting
Content Models Processing & Results
XHTML Web Pages
Formatting
Markup
Expedites
online delivery
Shouldn’t
have cost
much but did
Minimum
investment
Didn’t get in
the way…
Basic Markup: HTML
![Page 12: XML without Tears (J Gollner at Intelligent Content 2012)](https://reader033.vdocument.in/reader033/viewer/2022052618/554ba196b4c905b8618b4af1/html5/thumbnails/12.jpg)
Different story
Cost of
processing
semantic
markup is real
Benefits
mainly seen in
more filtered
formatting
The outcome
is debateable
Inline Semantic Markup
+$
-$Formatting
Content Models Processing & Results
+$
-$Semantics
XML / DITA Multiple Products
![Page 13: XML without Tears (J Gollner at Intelligent Content 2012)](https://reader033.vdocument.in/reader033/viewer/2022052618/554ba196b4c905b8618b4af1/html5/thumbnails/13.jpg)
-$Formatting
Semantic Models Content Models Processing & Results
+$
-$Semantics
+$
Balanced Markup: Just Enough Semantics
Semantic models provide semantic markup with the rigor needed to become really useful
![Page 14: XML without Tears (J Gollner at Intelligent Content 2012)](https://reader033.vdocument.in/reader033/viewer/2022052618/554ba196b4c905b8618b4af1/html5/thumbnails/14.jpg)
Advanced Markup: Progression from Balanced
+$
-$Formatting
Semantic Models Content Models Processing & Results
+$
-$Semantics
More comprehensive semantic models co-evolve with inline semantic markup
![Page 15: XML without Tears (J Gollner at Intelligent Content 2012)](https://reader033.vdocument.in/reader033/viewer/2022052618/554ba196b4c905b8618b4af1/html5/thumbnails/15.jpg)
Can we have Intelligent Content sans XML?
![Page 16: XML without Tears (J Gollner at Intelligent Content 2012)](https://reader033.vdocument.in/reader033/viewer/2022052618/554ba196b4c905b8618b4af1/html5/thumbnails/16.jpg)
Two Answers
Even when you are trying to
not use XML, you are
probably using XML
• MS Office / SharePoint
Any application larger than
an eggcup will need to
interoperate with other
applications
• Exchanging information
• Permitting extensibility to
support interoperability
Intelligent Content in a Normal Office
Frankenstein goes mobile
![Page 17: XML without Tears (J Gollner at Intelligent Content 2012)](https://reader033.vdocument.in/reader033/viewer/2022052618/554ba196b4c905b8618b4af1/html5/thumbnails/17.jpg)
So Explain to Me Again Why We Need XML?
![Page 18: XML without Tears (J Gollner at Intelligent Content 2012)](https://reader033.vdocument.in/reader033/viewer/2022052618/554ba196b4c905b8618b4af1/html5/thumbnails/18.jpg)
Real Content Resists Definitive Categorization
Real Content Demands Special
attention
![Page 19: XML without Tears (J Gollner at Intelligent Content 2012)](https://reader033.vdocument.in/reader033/viewer/2022052618/554ba196b4c905b8618b4af1/html5/thumbnails/19.jpg)
The Web & XML united
Browser-based collaborative authoring
Strong object metadata
supporting discovery & selection
Container elements providing
semantic guidance
Content input as XHTML
using common widgets
Minimal inline semantic markup
Attractive benefits profile
Easily extensible over time
The Human Face of Intelligent Content
![Page 20: XML without Tears (J Gollner at Intelligent Content 2012)](https://reader033.vdocument.in/reader033/viewer/2022052618/554ba196b4c905b8618b4af1/html5/thumbnails/20.jpg)
Asking Questions & Raising Objections
or just making connections…
Joe Gollner
Gnostyx Research Inc.
www.gnostyx.com
The Content Philosopher Blog
www.gollner.ca