<feed xml:lang="EN-us" xmlns="http://www.w3.org/2005/Atom" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:dcterms="http://purl.org/dc/terms/"><title>Norman.Walsh.name</title><subtitle>Norm's musings. Make of them what you will.</subtitle><link rel="alternate" type="text/html" href="http://norman.walsh.name/"/><link rel="self" href="http://norman.walsh.name/atom/whatsnew.xml"/><id>http://norman.walsh.name/atom/whatsnew.xml</id><updated>2012-02-09T12:15:14.823228Z</updated><author><name>Norman Walsh</name></author><entry><title>Playing with transclusion</title><link rel="alternate" type="text/html" href="http://norman.walsh.name/2011/10/03/transclusion"/><id>http://norman.walsh.name/2011/10/03/transclusion</id><published>2011-10-04T16:12:42Z</published><updated>2011-10-04T16:14:26.104676Z</updated><dc:subject>DocBook</dc:subject><dc:subject>W3C</dc:subject><dc:subject>XML</dc:subject><summary type="xhtml"><div xmlns="http://www.w3.org/1999/xhtml"><p>
  In my continuing efforts to explore transclusion, some running code.
</p></div></summary></entry><entry><title>HTML+XML at XML Prague</title><link rel="alternate" type="text/html" href="http://norman.walsh.name/2011/03/26/HTML-XML-Prague"/><id>http://norman.walsh.name/2011/03/26/HTML-XML-Prague</id><published>2011-03-26T15:24:56Z</published><updated>2011-03-26T15:25:20.803573Z</updated><dc:subject>XMLPrague2011</dc:subject><dc:subject>W3C</dc:subject><dc:subject>TAG</dc:subject><dc:subject>HTML</dc:subject><summary type="xhtml"><div xmlns="http://www.w3.org/1999/xhtml"><p>
      Here are the slides that I presented at XML Prague 2011.
    </p></div></summary></entry><entry><title>Thinking about the HTML and XML</title><link rel="alternate" type="text/html" href="http://norman.walsh.name/2011/02/08/html-xml"/><id>http://norman.walsh.name/2011/02/08/html-xml</id><published>2011-02-10T14:32:02Z</published><updated>2011-02-10T14:33:15.50534Z</updated><dc:subject>TAG</dc:subject><dc:subject>W3C</dc:subject><dc:subject>HTML</dc:subject><dc:subject>XML</dc:subject><summary type="xhtml"><div xmlns="http://www.w3.org/1999/xhtml"><p>
      After considering a set of use cases, the HTML/XML Task Force has decided
to issue a report of its findings. This is not that report. These are some notes, musings, and
experimental prose.
    </p></div></summary></entry><entry><title>Introducing the W3C HTML/XML Task Force</title><link rel="alternate" type="text/html" href="http://norman.walsh.name/2010/12/21/html-xml"/><id>http://norman.walsh.name/2010/12/21/html-xml</id><published>2010-12-21T21:47:34Z</published><updated>2010-12-21T21:52:00.957587Z</updated><dc:subject>TAG</dc:subject><dc:subject>W3C</dc:subject><dc:subject>XML</dc:subject><dc:subject>HTML</dc:subject><summary type="xhtml"><div xmlns="http://www.w3.org/1999/xhtml"><p>
      At the W3C Technical Plenary in November, the creation of an
      HTML/XML Task Force was announced. Today, that task force took
      its first steps down what I hope will be a fruitful
      path.
    </p></div></summary></entry><entry><title>ePUB, second attempt</title><link rel="alternate" type="text/html" href="http://norman.walsh.name/2010/06/10/epubredux"/><id>http://norman.walsh.name/2010/06/10/epubredux</id><published>2010-06-10T22:02:54Z</published><updated>2010-10-08T18:43:51.775293Z</updated><dc:subject>OASIS</dc:subject><dc:subject>W3C</dc:subject><dc:subject>XML</dc:subject><summary type="xhtml"><div xmlns="http://www.w3.org/1999/xhtml"><p>
Playing with ePUB. Validated ePUB this time.
</p></div></summary></entry><entry><title>ePUB tools</title><link rel="alternate" type="text/html" href="http://norman.walsh.name/2010/06/09/epubxpl"/><id>http://norman.walsh.name/2010/06/09/epubxpl</id><published>2010-06-09T10:24:09Z</published><updated>2010-10-08T18:43:48.293621Z</updated><dc:subject>W3C</dc:subject><dc:subject>XML</dc:subject><dc:subject>XProc</dc:subject><summary type="xhtml"><div xmlns="http://www.w3.org/1999/xhtml"><p>
Want to convert your favorite specification to ePUB? Here are the tools
that I've been using. [Update: 10 June 2010] Much revised.
</p></div></summary></entry><entry><title>ePUB specifications</title><link rel="alternate" type="text/html" href="http://norman.walsh.name/2010/06/07/epub"/><id>http://norman.walsh.name/2010/06/07/epub</id><published>2010-06-07T23:19:41Z</published><updated>2010-10-08T18:43:44.5579Z</updated><dc:subject>OASIS</dc:subject><dc:subject>W3C</dc:subject><dc:subject>XML</dc:subject><summary type="xhtml"><div xmlns="http://www.w3.org/1999/xhtml"><p>
Playing with ePUB. In this episode, ePUB versions of W3C specifications.
[Update 10 June 2010] Regenerated with stricter compliance to the ePUB
rules; added a few more. Plus pretty covers!
</p></div></summary></entry><entry><title>XProc is a W3C Recommendation!</title><link rel="alternate" type="text/html" href="http://norman.walsh.name/2010/05/11/xproc"/><id>http://norman.walsh.name/2010/05/11/xproc</id><published>2010-05-11T13:16:09Z</published><updated>2010-10-08T18:43:29.042312Z</updated><dc:subject>W3C</dc:subject><dc:subject>XML</dc:subject><dc:subject>XProc</dc:subject><summary type="xhtml"><div xmlns="http://www.w3.org/1999/xhtml"><p>
I'm delighted to say that we're finally finished. We've been
finished for a while, really, but today's announcement of the
Director's decision to advance XProc: An XML Pipeline Language to
Recommendation status dots the final “i” and crosses the final
“t”.
</p></div></summary></entry><entry><title>XProc Proposed Recommendation!</title><link rel="alternate" type="text/html" href="http://norman.walsh.name/2010/03/10/XProcProposedRecommendation"/><id>http://norman.walsh.name/2010/03/10/XProcProposedRecommendation</id><published>2010-03-10T11:01:16Z</published><updated>2010-10-08T18:42:57.210668Z</updated><dc:subject>W3C</dc:subject><dc:subject>XML</dc:subject><dc:subject>XProc</dc:subject><summary type="xhtml"><div xmlns="http://www.w3.org/1999/xhtml"><p>
I'm pleased to report that XProc: An XML Pipeline
Language is now a W3C Proposed Recommendation.
</p></div></summary></entry><entry><title>XProc: Back to Last Call</title><link rel="alternate" type="text/html" href="http://norman.walsh.name/2009/12/28/xproc-lc"/><id>http://norman.walsh.name/2009/12/28/xproc-lc</id><published>2009-12-28T14:20:52Z</published><updated>2010-10-08T18:41:40.365898Z</updated><dc:subject>W3C</dc:subject><dc:subject>XProc</dc:subject><summary type="xhtml"><div xmlns="http://www.w3.org/1999/xhtml"><p>
Early in January, a new XProc draft will appear. It will be a
Last Call Working Draft, a step backwards in the process, or maybe just
a half-step. The reason is important though: versioning.
</p></div></summary></entry><entry><title>Not exactly XProc</title><link rel="alternate" type="text/html" href="http://norman.walsh.name/2009/06/23/notXProc"/><id>http://norman.walsh.name/2009/06/23/notXProc</id><published>2009-06-23T22:27:55Z</published><updated>2010-10-08T18:40:29.706353Z</updated><dc:subject>Calabash</dc:subject><dc:subject>W3C</dc:subject><dc:subject>XProc</dc:subject><summary type="xhtml"><div xmlns="http://www.w3.org/1999/xhtml"><p>
One advantage of being an implementor is that I can play with
languages that the Working Group didn't approve.
</p></div></summary></entry><entry><title>Perhaps the penultimate XProc draft</title><link rel="alternate" type="text/html" href="http://norman.walsh.name/2009/05/28/xproc"/><id>http://norman.walsh.name/2009/05/28/xproc</id><published>2009-05-28T16:44:39Z</published><updated>2010-10-08T18:40:13.395409Z</updated><dc:subject>W3C</dc:subject><dc:subject>XML</dc:subject><dc:subject>XProc</dc:subject><summary type="xhtml"><div xmlns="http://www.w3.org/1999/xhtml"><p>
Today, the XML Processing Model Working Group published a new
working draft. Not the very last working draft, but possibly very close.
</p></div></summary></entry><entry><title>126 issues: resolved!</title><link rel="alternate" type="text/html" href="http://norman.walsh.name/2009/04/30/126issues"/><id>http://norman.walsh.name/2009/04/30/126issues</id><published>2009-04-30T22:11:46Z</published><updated>2010-10-08T18:39:54.670611Z</updated><dc:subject>W3C</dc:subject><dc:subject>XML</dc:subject><dc:subject>XProc</dc:subject><summary type="xhtml"><div xmlns="http://www.w3.org/1999/xhtml"><p>
Today, the XProc WG reached consensus on the last of the 126 issues
submitted during our Candidate Recommendation period.
</p></div></summary></entry><entry><title>Building a bigger pipeline</title><link rel="alternate" type="text/html" href="http://norman.walsh.name/2009/03/26/xprocWithXProc"/><id>http://norman.walsh.name/2009/03/26/xprocWithXProc</id><published>2009-03-27T00:00:40Z</published><updated>2011-08-31T20:13:50.046812Z</updated><dc:subject>Calabash</dc:subject><dc:subject>W3C</dc:subject><dc:subject>XML</dc:subject><dc:subject>XProc</dc:subject><summary type="xhtml"><div xmlns="http://www.w3.org/1999/xhtml"><p>
Constructing a “real world” XProc pipeline:
building the XProc specification with XProc.
</p></div></summary></entry><entry><title>&lt;/TAG&gt;</title><link rel="alternate" type="text/html" href="http://norman.walsh.name/2008/12/09/endTAG"/><id>http://norman.walsh.name/2008/12/09/endTAG</id><published>2008-12-10T02:52:44Z</published><updated>2010-10-08T18:38:06.511444Z</updated><dc:subject>SelfReference</dc:subject><dc:subject>TAG</dc:subject><dc:subject>W3C</dc:subject><summary type="xhtml"><div xmlns="http://www.w3.org/1999/xhtml"><p>
I've been an elected member of the W3C Technical Architecture Group
for eight years. I've had a wonderful time and I hope that I've contributed
in useful ways, but I feel like it's time to step aside, at least for a
little while.
</p></div></summary></entry><entry><title>XProc Candidate Recommendation!</title><link rel="alternate" type="text/html" href="http://norman.walsh.name/2008/11/26/XProcCandidateRecommendation"/><id>http://norman.walsh.name/2008/11/26/XProcCandidateRecommendation</id><published>2008-11-27T03:28:20Z</published><updated>2010-10-08T18:37:49.899861Z</updated><dc:subject>W3C</dc:subject><dc:subject>XML</dc:subject><dc:subject>XProc</dc:subject><summary type="xhtml"><div xmlns="http://www.w3.org/1999/xhtml"><p>
I'm pleased to report that XProc: An XML Pipeline
Language is now a W3C Candidate Recommendation.
</p></div></summary></entry><entry><title>XProc and Calabash progress</title><link rel="alternate" type="text/html" href="http://norman.walsh.name/2008/09/28/calabash"/><id>http://norman.walsh.name/2008/09/28/calabash</id><published>2008-09-28T20:16:46Z</published><updated>2010-10-08T18:37:40.565775Z</updated><dc:subject>Calabash</dc:subject><dc:subject>W3C</dc:subject><dc:subject>XML</dc:subject><dc:subject>XProc</dc:subject><summary type="xhtml"><div xmlns="http://www.w3.org/1999/xhtml"><p>
The second “Last Call” for XProc ended on Friday. Things are
looking good for progress to Candidate Recommendation. That means we
need implementations!
</p></div></summary></entry><entry><title>Announcing xproc-dev@lists.w3.org</title><link rel="alternate" type="text/html" href="http://norman.walsh.name/2008/08/24/xproc-dev"/><id>http://norman.walsh.name/2008/08/24/xproc-dev</id><published>2008-08-24T20:48:14Z</published><updated>2010-10-08T18:37:24.221767Z</updated><dc:subject>Calabash</dc:subject><dc:subject>W3C</dc:subject><dc:subject>XProc</dc:subject><summary type="xhtml"><div xmlns="http://www.w3.org/1999/xhtml"><p>
You're invited to join the xproc-dev mailing list,
a public discussion forum for implementors and users of XProc:
An XML Pipeline Language.
</p></div></summary></entry><entry><title>XProc goes back to Last Call</title><link rel="alternate" type="text/html" href="http://norman.walsh.name/2008/08/20/xproc"/><id>http://norman.walsh.name/2008/08/20/xproc</id><published>2008-08-20T11:17:56Z</published><updated>2010-10-08T18:37:20.038539Z</updated><dc:subject>W3C</dc:subject><dc:subject>XML</dc:subject><dc:subject>XProc</dc:subject><summary type="xhtml"><div xmlns="http://www.w3.org/1999/xhtml"><p>
I sincerely expect this to be the Last Call.
</p></div></summary></entry><entry><title>Thinking differently about XML</title><link rel="alternate" type="text/html" href="http://norman.walsh.name/2008/08/04/aboutXML"/><id>http://norman.walsh.name/2008/08/04/aboutXML</id><published>2008-08-04T20:32:29Z</published><updated>2010-10-08T18:37:13.048402Z</updated><dc:subject>MarkLogic</dc:subject><dc:subject>W3C</dc:subject><dc:subject>XML</dc:subject><summary type="xhtml"><div xmlns="http://www.w3.org/1999/xhtml"><p>
Having an XML server at my disposal is making me think about XML
applications differently.
</p></div></summary></entry><entry><title>Agenda bookmarklet</title><link rel="alternate" type="text/html" href="http://norman.walsh.name/2008/05/09/bookmarklet"/><id>http://norman.walsh.name/2008/05/09/bookmarklet</id><published>2008-05-09T11:15:54Z</published><updated>2010-10-08T18:36:37.644192Z</updated><dc:subject>TheWeb</dc:subject><dc:subject>W3C</dc:subject><summary type="xhtml"><div xmlns="http://www.w3.org/1999/xhtml"><p>
A ten minute hack to fix a ten second problem, linking to working
group agendas and minutes.
</p></div></summary></entry><entry><title>New XProc Working Draft</title><link rel="alternate" type="text/html" href="http://norman.walsh.name/2008/05/01/xproc"/><id>http://norman.walsh.name/2008/05/01/xproc</id><published>2008-05-01T12:32:24Z</published><updated>2010-10-08T18:36:30.666893Z</updated><dc:subject>W3C</dc:subject><dc:subject>XML</dc:subject><dc:subject>XProc</dc:subject><summary type="xhtml"><div xmlns="http://www.w3.org/1999/xhtml"><p>
The XML Processing Model Working Group has published a new Working
Draft of XProc: An XML Pipeline Language.
</p></div></summary></entry><entry><title>XML 2.0? No, seriously.</title><link rel="alternate" type="text/html" href="http://norman.walsh.name/2008/02/20/xml20"/><id>http://norman.walsh.name/2008/02/20/xml20</id><published>2008-02-20T15:17:24Z</published><updated>2010-10-08T18:35:25.166901Z</updated><dc:subject>W3C</dc:subject><dc:subject>XML</dc:subject><summary type="xhtml"><div xmlns="http://www.w3.org/1999/xhtml"><p>
Maybe its madness to consider XML 2.0 seriously.
The cost of deployment would be significant.
Simultaneously convincing a critical mass of users to switch without
turning the design process into a farce would be very difficult.
And yet, the alternatives look a little like madness too.
</p></div></summary></entry><entry><title>XML at 10</title><link rel="alternate" type="text/html" href="http://norman.walsh.name/2008/02/10/xml10"/><id>http://norman.walsh.name/2008/02/10/xml10</id><published>2008-02-10T18:51:54Z</published><updated>2010-10-08T18:35:21.927693Z</updated><dc:subject>W3C</dc:subject><dc:subject>XML</dc:subject><summary type="xhtml"><div xmlns="http://www.w3.org/1999/xhtml"><p>
Today is the tenth anniversary of the publication of Extensible
Markup Language (XML) 1.0 as a W3C Recommendation.
</p></div></summary></entry><entry><title>XML 1.0 (Fifth Edition)</title><link rel="alternate" type="text/html" href="http://norman.walsh.name/2008/02/07/xml105e"/><id>http://norman.walsh.name/2008/02/07/xml105e</id><published>2008-02-07T17:23:19Z</published><updated>2010-10-08T18:35:15.668247Z</updated><dc:subject>W3C</dc:subject><dc:subject>XML</dc:subject><summary type="xhtml"><div xmlns="http://www.w3.org/1999/xhtml"><p>
The fifth edition of XML 1.0 is now a “proposed edited recommendation”.
New editions do little more than incorporate errata, hardly
newsworthy. This one is different.
</p></div></summary></entry><entry><title>New XProc Working Draft</title><link rel="alternate" type="text/html" href="http://norman.walsh.name/2007/11/29/xproc"/><id>http://norman.walsh.name/2007/11/29/xproc</id><published>2007-11-29T18:30:47Z</published><updated>2010-10-08T18:32:42.26628Z</updated><dc:subject>W3C</dc:subject><dc:subject>XML</dc:subject><dc:subject>XProc</dc:subject><summary type="xhtml"><div xmlns="http://www.w3.org/1999/xhtml"><p>
The XML Processing Model Working Group has published a new Working
Draft of XProc: An XML Pipeline Language.
</p></div></summary></entry><entry><title>XProc and XPath</title><link rel="alternate" type="text/html" href="http://norman.walsh.name/2007/11/15/xprocXPath"/><id>http://norman.walsh.name/2007/11/15/xprocXPath</id><published>2007-11-15T20:29:00Z</published><updated>2010-10-08T18:31:51.411105Z</updated><dc:subject>W3C</dc:subject><dc:subject>XProc</dc:subject><summary type="xhtml"><div xmlns="http://www.w3.org/1999/xhtml"><p>
When are two versions better than one? Maybe never, but
apparently sometimes two versions are an inevitable
compromise.
</p></div></summary></entry><entry><title>End of an era</title><link rel="alternate" type="text/html" href="http://norman.walsh.name/2007/10/10/eoxsl"/><id>http://norman.walsh.name/2007/10/10/eoxsl</id><published>2007-10-10T13:10:41Z</published><updated>2010-10-08T18:31:05.722551Z</updated><dc:subject>W3C</dc:subject><dc:subject>XSLT</dc:subject><summary type="xhtml"><div xmlns="http://www.w3.org/1999/xhtml"><p>
After almost a decade, I'm going to have to put aside my XSL Working
Group Member hat.
</p></div></summary></entry><entry><title>XProc Implementations?</title><link rel="alternate" type="text/html" href="http://norman.walsh.name/2007/10/09/xprocImplementations"/><id>http://norman.walsh.name/2007/10/09/xprocImplementations</id><published>2007-10-09T19:41:04Z</published><updated>2010-10-08T18:31:01.55629Z</updated><dc:subject>W3C</dc:subject><dc:subject>XProc</dc:subject><summary type="xhtml"><div xmlns="http://www.w3.org/1999/xhtml"><p>
Are you implementing XProc or thinking about implementing XProc?
Are you willing to say so in public? Please do tell me!

</p></div></summary></entry><entry><title>XProc Last Call!</title><link rel="alternate" type="text/html" href="http://norman.walsh.name/2007/09/21/lastCall"/><id>http://norman.walsh.name/2007/09/21/lastCall</id><published>2007-09-21T11:43:35Z</published><updated>2010-10-08T18:30:24.525753Z</updated><dc:subject>W3C</dc:subject><dc:subject>XML</dc:subject><dc:subject>XProc</dc:subject><summary type="xhtml"><div xmlns="http://www.w3.org/1999/xhtml"><p>
The XML Processing Model Working Group has published
XProc: An XML Pipeline Language as a Last
Call Working Draft!
</p></div></summary></entry></feed>

