<?xml version="1.0" encoding="UTF-8"?>
<?xml-stylesheet type="text/xsl" media="screen" href="/~d/styles/atom10full.xsl"?><?xml-stylesheet type="text/css" media="screen" href="http://feeds.feedburner.com/~d/styles/itemcontent.css"?><feed xmlns="http://www.w3.org/2005/Atom" xmlns:feedburner="http://rssnamespace.org/feedburner/ext/1.0">
    <title>O'Reilly News: XML</title>
    <link rel="alternate" type="text/html" href="http://oreilly.com/xml/" />
    <id>tag:news.oreilly.com,2008-08-01://44</id>
    <updated>

2011-10-03T13:00:00Z</updated>
    <subtitle>XML news and articles from O'Reilly Media</subtitle>
    <generator uri="http://www.sixapart.com/movabletype/">Movable Type Pro 4.21-en</generator>

<atom10:link xmlns:atom10="http://www.w3.org/2005/Atom" rel="self" type="application/atom+xml" href="http://feeds.feedburner.com/oreilly/xml" /><feedburner:info uri="oreilly/xml" /><atom10:link xmlns:atom10="http://www.w3.org/2005/Atom" rel="hub" href="http://pubsubhubbub.appspot.com/" /><entry>
    <title>The agile upside of XML</title>
    <link rel="alternate" type="text/html" href="http://feedproxy.google.com/~r/oreilly/xml/~3/JI5QSXpVhuw/xml-publisher-workflow-ebook-design.html" />
    <id>tag:radar.oreilly.com,2011://57.47256</id>

    <published>2011-10-03T13:00:00Z</published>
    <updated>2011-10-03T13:00:00Z</updated>

    <summary>Frankfurt TOC presenters Anna von Veh, a consultant at Say Books, and Mike McNamara, managing director at Araman Consulting Ltd &amp; Outsell-Gilbane UK Affiliate, discuss xml workflows, the (sorry) state of ebook design, and how books and the web will evolve.</summary>
    <author>
        <name>Jenn Webb</name>
        <uri>http://radar.oreilly.com/jennw</uri>
    </author>
    
        <category term="Publishing" scheme="http://www.sixapart.com/ns/types#category" />
    
    <category term="digitalpublishing" label="digital publishing" scheme="http://www.sixapart.com/ns/types#tag" />
    <category term="digitalreading" label="digital reading" scheme="http://www.sixapart.com/ns/types#tag" />
    <category term="futureofthebook" label="future of the book" scheme="http://www.sixapart.com/ns/types#tag" />
    <category term="tocfrankfurt" label="toc frankfurt" scheme="http://www.sixapart.com/ns/types#tag" />
    <category term="workflows" label="workflows" scheme="http://www.sixapart.com/ns/types#tag" />
    <category term="xml" label="xml" scheme="http://www.sixapart.com/ns/types#tag" />
    
    <content type="html" xml:lang="en" xml:base="http://radar.oreilly.com/">
        Frankfurt TOC presenters Anna von Veh, a consultant at Say Books, and Mike McNamara, managing director at Araman Consulting Ltd &amp; Outsell-Gilbane UK Affiliate, discuss xml workflows, the (sorry) state of ebook design, and how books and the web will evolve.
     &lt;img src="http://feeds.feedburner.com/~r/oreilly/xml/~4/JI5QSXpVhuw" height="1" width="1"/&gt;</content>
<feedburner:origLink>http://radar.oreilly.com/2011/10/xml-publisher-workflow-ebook-design.html</feedburner:origLink></entry>

<entry>
    <title>XML Schema development approaches</title>
    <link rel="alternate" type="text/html" href="http://feedproxy.google.com/~r/oreilly/xml/~3/qCC5f88Ib6Y/xml-schema-development-methodo.html" />
    <id>tag:broadcast.oreilly.com,2011://53.47013</id>

    <published>2011-08-09T00:53:16Z</published>
    <updated>2011-08-09T00:53:16Z</updated>

    <summary>The way that people approach developing schemas has evolved over the years: each new approach grows out of problems with the status quo (see Hegelian dialectic) but enriches rather than supplants. I thought I would take a little walk through...</summary>
    <author>
        <name>Rick Jelliffe</name>
        
    </author>
    
    <category term="xml" label="xml" scheme="http://www.sixapart.com/ns/types#tag" />
    <category term="xmlschemas" label="xml schemas" scheme="http://www.sixapart.com/ns/types#tag" />
    
    <content type="html" xml:lang="en" xml:base="http://broadcast.oreilly.com/">
        The way that people approach developing schemas has evolved over the years: each new approach grows out of problems with the status quo (see Hegelian dialectic) but enriches rather than supplants. I thought I would take a little walk through...
     &lt;img src="http://feeds.feedburner.com/~r/oreilly/xml/~4/qCC5f88Ib6Y" height="1" width="1"/&gt;</content>
<feedburner:origLink>http://broadcast.oreilly.com/2011/08/xml-schema-development-methodo.html</feedburner:origLink></entry>

<entry>
    <title>ETL and Publishing</title>
    <link rel="alternate" type="text/html" href="http://feedproxy.google.com/~r/oreilly/xml/~3/bLqE1P1jc_s/etl-and-publishing.html" />
    <id>tag:broadcast.oreilly.com,2011://53.46565</id>

    <published>2011-06-05T12:52:12Z</published>
    <updated>2011-06-05T12:52:12Z</updated>

    <summary>I have for a few years been trying to come up with a good definition of publishing workflows: as an architectural pattern. The two key distinctive features, I think, are that publishing workflows are one-way flows rather than two-way flows...</summary>
    <author>
        <name>Rick Jelliffe</name>
        
    </author>
    
    <category term="etl" label="etl" scheme="http://www.sixapart.com/ns/types#tag" />
    <category term="xml" label="xml" scheme="http://www.sixapart.com/ns/types#tag" />
    <category term="xslt" label="xslt" scheme="http://www.sixapart.com/ns/types#tag" />
    
    <content type="html" xml:lang="en" xml:base="http://broadcast.oreilly.com/">
        I have for a few years been trying to come up with a good definition of publishing workflows: as an architectural pattern. The two key distinctive features, I think, are that publishing workflows are one-way flows rather than two-way flows...
     &lt;img src="http://feeds.feedburner.com/~r/oreilly/xml/~4/bLqE1P1jc_s" height="1" width="1"/&gt;</content>
<feedburner:origLink>http://broadcast.oreilly.com/2011/06/etl-and-publishing.html</feedburner:origLink></entry>

<entry>
    <title>Australian Whole-of-Government Common Operating Environment Policy and OOXML</title>
    <link rel="alternate" type="text/html" href="http://feedproxy.google.com/~r/oreilly/xml/~3/Org2R0ZiC5A/australian-whole-of-government.html" />
    <id>tag:broadcast.oreilly.com,2011://53.45636</id>

    <published>2011-01-28T12:16:36Z</published>
    <updated>2011-01-28T12:16:36Z</updated>

    <summary>Two big stories this week: AGIMO's COE and LibreOffice. AGIMO is the Australian Government Information Management Office. They are the ones who set policies such as requiring govt web page meet the W3C's WCAG 2.0 guidelines for accessibility, or that...</summary>
    <author>
        <name>Rick Jelliffe</name>
        
    </author>
    
    <category term="odf" label="odf" scheme="http://www.sixapart.com/ns/types#tag" />
    <category term="ooxml" label="ooxml" scheme="http://www.sixapart.com/ns/types#tag" />
    <category term="standards" label="standards" scheme="http://www.sixapart.com/ns/types#tag" />
    <category term="xml" label="xml" scheme="http://www.sixapart.com/ns/types#tag" />
    
    <content type="html" xml:lang="en" xml:base="http://broadcast.oreilly.com/">
        Two big stories this week: AGIMO's COE and LibreOffice. AGIMO is the Australian Government Information Management Office. They are the ones who set policies such as requiring govt web page meet the W3C's WCAG 2.0 guidelines for accessibility, or that...
     &lt;img src="http://feeds.feedburner.com/~r/oreilly/xml/~4/Org2R0ZiC5A" height="1" width="1"/&gt;</content>
<feedburner:origLink>http://broadcast.oreilly.com/2011/01/australian-whole-of-government.html</feedburner:origLink></entry>

<entry>
    <title>Four short links: 3 December 2010</title>
    <link rel="alternate" type="text/html" href="http://feedproxy.google.com/~r/oreilly/xml/~3/uvjlz2WRvX8/four-short-links-3-december-20-1.html" />
    <id>tag:radar.oreilly.com,2010://57.43499</id>

    <published>2010-12-03T11:00:00Z</published>
    <updated>2010-12-03T11:00:00Z</updated>

    <summary> Data is Snake Oil (Pete Warden) -- data is powerful but fickle. A lot of theoretically promising approaches don't work because there's so many barriers between spotting a possible relationship and turning it into something useful and actionable. This is the pin of reality which deflates the bubble of inflated expectations. Apologies for the camel's nose of rhetoric poking...</summary>
    <author>
        <name>Nat Torkington</name>
        <uri>http://radar.oreilly.com/nat/</uri>
    </author>
    
    <category term="bigdata" label="big data" scheme="http://www.sixapart.com/ns/types#tag" />
    <category term="data" label="data" scheme="http://www.sixapart.com/ns/types#tag" />
    <category term="datamining" label="data mining" scheme="http://www.sixapart.com/ns/types#tag" />
    <category term="devops" label="devops" scheme="http://www.sixapart.com/ns/types#tag" />
    <category term="games" label="games" scheme="http://www.sixapart.com/ns/types#tag" />
    <category term="json" label="json" scheme="http://www.sixapart.com/ns/types#tag" />
    <category term="programming" label="programming" scheme="http://www.sixapart.com/ns/types#tag" />
    <category term="web" label="web" scheme="http://www.sixapart.com/ns/types#tag" />
    <category term="xml" label="xml" scheme="http://www.sixapart.com/ns/types#tag" />
    
    <content type="html" xml:lang="en" xml:base="http://radar.oreilly.com/">
         Data is Snake Oil (Pete Warden) -- data is powerful but fickle. A lot of theoretically promising approaches don't work because there's so many barriers between spotting a possible relationship and turning it into something useful and actionable. This is the pin of reality which deflates the bubble of inflated expectations. Apologies for the camel's nose of rhetoric poking...
     &lt;img src="http://feeds.feedburner.com/~r/oreilly/xml/~4/uvjlz2WRvX8" height="1" width="1"/&gt;</content>
<feedburner:origLink>http://radar.oreilly.com/2010/12/four-short-links-3-december-20-1.html</feedburner:origLink></entry>

<entry>
    <title>Schema coverage report</title>
    <link rel="alternate" type="text/html" href="http://feedproxy.google.com/~r/oreilly/xml/~3/ARtLG_4BSzA/schema-coverage.html" />
    <id>tag:broadcast.oreilly.com,2010://53.43181</id>

    <published>2010-10-23T03:48:43Z</published>
    <updated>2010-10-23T03:48:43Z</updated>

    <summary>You have a large or complex Schematron schema and it produces no errors. How do you know it is working? A coverage report lets you see how many of each Schematron rule was fired when checking the document(s). The report...</summary>
    <author>
        <name>Rick Jelliffe</name>
        
    </author>
    
    <category term="schematron" label="schematron" scheme="http://www.sixapart.com/ns/types#tag" />
    <category term="xml" label="xml" scheme="http://www.sixapart.com/ns/types#tag" />
    
    <content type="html" xml:lang="en" xml:base="http://broadcast.oreilly.com/">
        You have a large or complex Schematron schema and it produces no errors. How do you know it is working? A coverage report lets you see how many of each Schematron rule was fired when checking the document(s). The report...
     &lt;img src="http://feeds.feedburner.com/~r/oreilly/xml/~4/ARtLG_4BSzA" height="1" width="1"/&gt;</content>
<feedburner:origLink>http://broadcast.oreilly.com/2010/10/schema-coverage.html</feedburner:origLink></entry>

<entry>
    <title>Understanding C#: Simple LINQ to XML examples (tutorial)</title>
    <link rel="alternate" type="text/html" href="http://feedproxy.google.com/~r/oreilly/xml/~3/JZibwfQ1CEc/understanding-c-simple-linq-to.html" />
    <id>tag:broadcast.oreilly.com,2010://53.43133</id>

    <published>2010-10-16T14:21:23Z</published>
    <updated>2010-10-16T14:21:23Z</updated>

    <summary>XML is one of the most popular formats for files and data streams that need to represent complex data. The .NET Framework gives you some really powerful tools for creating, loading, and saving XML files. And once you've got your hands on XML data, you can use LINQ to query anything from data that you created to an RSS feed. In this post, I'll show you two simple LINQ to XML tutorial style examples that highlight basic patterns that you can use to create or query XML data using LINQ to XML.</summary>
    <author>
        <name>Andrew Stellman</name>
        <uri>http://www.stellman-greene.com</uri>
    </author>
    
    <category term="net" label=".net" scheme="http://www.sixapart.com/ns/types#tag" />
    <category term="c" label="c#" scheme="http://www.sixapart.com/ns/types#tag" />
    <category term="csharp" label="csharp" scheme="http://www.sixapart.com/ns/types#tag" />
    <category term="dotnet" label="dotnet" scheme="http://www.sixapart.com/ns/types#tag" />
    <category term="headfirst" label="headfirst" scheme="http://www.sixapart.com/ns/types#tag" />
    <category term="linq" label="Linq" scheme="http://www.sixapart.com/ns/types#tag" />
    <category term="microsoft" label="microsoft" scheme="http://www.sixapart.com/ns/types#tag" />
    <category term="xml" label="xml" scheme="http://www.sixapart.com/ns/types#tag" />
    
    <content type="html" xml:lang="en" xml:base="http://broadcast.oreilly.com/">
        XML is one of the most popular formats for files and data streams that need to represent complex data. The .NET Framework gives you some really powerful tools for creating, loading, and saving XML files. And once you've got your hands on XML data, you can use LINQ to query anything from data that you created to an RSS feed. In this post, I'll show you two simple LINQ to XML tutorial style examples that highlight basic patterns that you can use to create or query XML data using LINQ to XML.
     &lt;img src="http://feeds.feedburner.com/~r/oreilly/xml/~4/JZibwfQ1CEc" height="1" width="1"/&gt;</content>
<feedburner:origLink>http://broadcast.oreilly.com/2010/10/understanding-c-simple-linq-to.html</feedburner:origLink></entry>

<entry>
    <title>Under-estimating XML as just a Tree</title>
    <link rel="alternate" type="text/html" href="http://feedproxy.google.com/~r/oreilly/xml/~3/yc7DSkV9m_M/under-estimating-xml-as-just-a.html" />
    <id>tag:broadcast.oreilly.com,2010://53.43112</id>

    <published>2010-10-09T05:11:45Z</published>
    <updated>2010-10-09T05:11:45Z</updated>

    <summary>Programmers and academics often think and theorize about XML as kind of tree data structure. And so indeed it is. But it also allows much more: it is a series of different graph structures composed into or imposed on that tree. </summary>
    <author>
        <name>Rick Jelliffe</name>
        
    </author>
    
    <category term="xml" label="xml" scheme="http://www.sixapart.com/ns/types#tag" />
    
    <content type="html" xml:lang="en" xml:base="http://broadcast.oreilly.com/">
        Programmers and academics often think and theorize about XML as kind of tree data structure. And so indeed it is. But it also allows much more: it is a series of different graph structures composed into or imposed on that tree. 
     &lt;img src="http://feeds.feedburner.com/~r/oreilly/xml/~4/yc7DSkV9m_M" height="1" width="1"/&gt;</content>
<feedburner:origLink>http://broadcast.oreilly.com/2010/10/under-estimating-xml-as-just-a.html</feedburner:origLink></entry>

<entry>
    <title>Four short links: 8 October 2010</title>
    <link rel="alternate" type="text/html" href="http://feedproxy.google.com/~r/oreilly/xml/~3/h3KO723VlQE/four-short-links-8-october-201.html" />
    <id>tag:radar.oreilly.com,2010://57.43105</id>

    <published>2010-10-08T10:00:00Z</published>
    <updated>2010-10-08T10:00:00Z</updated>

    <summary> Training Lessons Learned: Interactivity (Selena Marie Deckelmann) -- again I see parallels between how the best school teachers work and the best trainers. I was working with a group of people with diverse IT backgrounds, and often, I asked individuals to try to explain in their own words various terms (like “transaction”). This helped engage the students in a...</summary>
    <author>
        <name>Nat Torkington</name>
        <uri>http://radar.oreilly.com/nat/</uri>
    </author>
    
    <category term="education" label="education" scheme="http://www.sixapart.com/ns/types#tag" />
    <category term="license" label="license" scheme="http://www.sixapart.com/ns/types#tag" />
    <category term="opensource" label="open source" scheme="http://www.sixapart.com/ns/types#tag" />
    <category term="poetry" label="poetry" scheme="http://www.sixapart.com/ns/types#tag" />
    <category term="programming" label="programming" scheme="http://www.sixapart.com/ns/types#tag" />
    <category term="training" label="training" scheme="http://www.sixapart.com/ns/types#tag" />
    <category term="visualization" label="visualization" scheme="http://www.sixapart.com/ns/types#tag" />
    <category term="xml" label="xml" scheme="http://www.sixapart.com/ns/types#tag" />
    
    <content type="html" xml:lang="en" xml:base="http://radar.oreilly.com/">
         Training Lessons Learned: Interactivity (Selena Marie Deckelmann) -- again I see parallels between how the best school teachers work and the best trainers. I was working with a group of people with diverse IT backgrounds, and often, I asked individuals to try to explain in their own words various terms (like “transaction”). This helped engage the students in a...
     &lt;img src="http://feeds.feedburner.com/~r/oreilly/xml/~4/h3KO723VlQE" height="1" width="1"/&gt;</content>
<feedburner:origLink>http://radar.oreilly.com/2010/10/four-short-links-8-october-201.html</feedburner:origLink></entry>

<entry>
    <title>Do you need to make your own XSLT2 function definitions when using Schematron?</title>
    <link rel="alternate" type="text/html" href="http://feedproxy.google.com/~r/oreilly/xml/~3/hfugKS4uT2s/do-you-need-to-make-your-own-x.html" />
    <id>tag:broadcast.oreilly.com,2010://53.43025</id>

    <published>2010-09-27T10:52:58Z</published>
    <updated>2010-09-27T10:52:58Z</updated>

    <summary>Recently I have seen some Schematron schemas written by good XSLT programmers which basically represented all assertion tests as custom XSLT2 functions. (Schematron allows this.) The schemas were successful, in that they functioned as desired, but I don't think there...</summary>
    <author>
        <name>Rick Jelliffe</name>
        
    </author>
    
    <category term="schematron" label="schematron" scheme="http://www.sixapart.com/ns/types#tag" />
    <category term="xml" label="xml" scheme="http://www.sixapart.com/ns/types#tag" />
    <category term="xslt2" label="xslt2" scheme="http://www.sixapart.com/ns/types#tag" />
    
    <content type="html" xml:lang="en" xml:base="http://broadcast.oreilly.com/">
        Recently I have seen some Schematron schemas written by good XSLT programmers which basically represented all assertion tests as custom XSLT2 functions. (Schematron allows this.) The schemas were successful, in that they functioned as desired, but I don't think there...
     &lt;img src="http://feeds.feedburner.com/~r/oreilly/xml/~4/hfugKS4uT2s" height="1" width="1"/&gt;</content>
<feedburner:origLink>http://broadcast.oreilly.com/2010/09/do-you-need-to-make-your-own-x.html</feedburner:origLink></entry>

<entry>
    <title>How to Install MongoDB</title>
    <link rel="alternate" type="text/html" href="http://feedproxy.google.com/~r/oreilly/xml/~3/_uOV7AJmBUM/" />
    <id>tag:blogs.oreilly.com,2010:/blurbs//59.42940</id>

    <published>2010-09-16T13:54:40Z</published>
    <updated>2010-09-16T13:54:40Z</updated>

    <summary>In this excerpt from MongoDB: The Definitive Guide we offer a step by step guide on how to install MongoDB and get it up and running smoothly.  Precompiled binaries are available for Linux, Mac OS X, Windows, and Solaris. On most platforms you can download the archive from mongodb.org, inflate it, and run the binary. The MongoDB server requires a directory it can write database files to and a port it can listen for connections on. The following section covers the entire install on the two variants of system: Windows and everything else (Linux, Max, Solaris). Read more.More from O'Reilly Answers:Using the iPhone's GPS internationallyI just learned HTML/CSS. Now what?Which Perl XML module should I use?5 ways to get music and video on your iPhone using iTunes Share knowledge, ask questions on O'Reilly Answers today.</summary>
    <author>
        <name>O'Reilly Media</name>
        
    </author>
    
    <category term="css" label="css" scheme="http://www.sixapart.com/ns/types#tag" />
    <category term="databases" label="databases" scheme="http://www.sixapart.com/ns/types#tag" />
    <category term="html" label="html" scheme="http://www.sixapart.com/ns/types#tag" />
    <category term="iphone" label="iphone" scheme="http://www.sixapart.com/ns/types#tag" />
    <category term="perl" label="perl" scheme="http://www.sixapart.com/ns/types#tag" />
    <category term="xml" label="xml" scheme="http://www.sixapart.com/ns/types#tag" />
    
    <content type="html" xml:lang="en" xml:base="http://blogs.oreilly.com/blurbs/">
        In this excerpt from &lt;a href="http://oreilly.com/catalog/0636920001096"&gt;MongoDB: The Definitive Guide&lt;/a&gt; we offer a step by step guide on how to install MongoDB and get it up and running smoothly.  Precompiled binaries are available for Linux, Mac OS X, Windows, and Solaris. On most platforms you can download the archive from &lt;a href="http://www.mongodb.org"&gt;mongodb.org&lt;/a&gt;, inflate it, and run the binary. The MongoDB server requires a directory it can write database files to and a port it can listen for connections on. The following section covers the entire install on the two variants of system: Windows and everything else (Linux, Max, Solaris). &lt;a href="http://answers.oreilly.com/topic/2066-how-to-install-mongodb/" rel="nofollow"&gt;&lt;strong&gt;Read more&lt;/strong&gt;&lt;/a&gt;.&lt;br /&gt;&lt;br /&gt;More from O'Reilly Answers:&lt;br /&gt;&lt;br /&gt;&lt;ul style="margin: 0 0 0 1.2em; padding: 3px 0 10px 0;"&gt;&lt;li style="padding-bottom: 6px;"&gt;&lt;a href="http://answers.oreilly.com/topic/2062-use-of-iphone-gps-overseas/"&gt;Using the iPhone's GPS internationally&lt;/a&gt;&lt;/li&gt;&lt;li style="padding-bottom: 6px;"&gt;&lt;a href="http://answers.oreilly.com/topic/2063-just-finished-htmlcss-which-would-be-the-next-best-book/"&gt;I just learned HTML/CSS. Now what?&lt;/a&gt;&lt;/li&gt;&lt;li style="padding-bottom: 6px;"&gt;&lt;a href="http://answers.oreilly.com/topic/1908-which-perl-xml-module-should-i-use/"&gt;Which Perl XML module should I use?&lt;/a&gt;&lt;/li&gt;&lt;li style="padding-bottom: 0px;"&gt;&lt;a href="http://answers.oreilly.com/topic/2048-5-ways-to-get-music-and-video-on-your-iphone-using-itunes/"&gt;5 ways to get music and video on your iPhone using iTunes&lt;/a&gt;&lt;/li&gt;&lt;/ul&gt; Share knowledge, ask questions on &lt;a href="http://answers.oreilly.com/"&gt;O'Reilly Answers&lt;/a&gt; today.
     &lt;img src="http://feeds.feedburner.com/~r/oreilly/xml/~4/_uOV7AJmBUM" height="1" width="1"/&gt;</content>
<feedburner:origLink>http://answers.oreilly.com/topic/2066-how-to-install-mongodb/</feedburner:origLink></entry>

<entry>
    <title>Vale Java? Scala Vala palava</title>
    <link rel="alternate" type="text/html" href="http://feedproxy.google.com/~r/oreilly/xml/~3/LLsq7yLcUA0/vale-java-scala-vala-palava.html" />
    <id>tag:broadcast.oreilly.com,2010://53.42003</id>

    <published>2010-08-28T05:21:10Z</published>
    <updated>2010-08-28T05:21:10Z</updated>

    <summary>Dave Megginson (who drove the development of the SAX API that will be familiar to many XML developers who use Java) recently wrote Java is dead. Java stood out as a programming language (though not as a platform) in that...</summary>
    <author>
        <name>Rick Jelliffe</name>
        
    </author>
    
    <category term="go" label="go" scheme="http://www.sixapart.com/ns/types#tag" />
    <category term="java" label="java" scheme="http://www.sixapart.com/ns/types#tag" />
    <category term="scala" label="scala" scheme="http://www.sixapart.com/ns/types#tag" />
    <category term="vala" label="vala" scheme="http://www.sixapart.com/ns/types#tag" />
    <category term="xml" label="xml" scheme="http://www.sixapart.com/ns/types#tag" />
    
    <content type="html" xml:lang="en" xml:base="http://broadcast.oreilly.com/">
        Dave Megginson (who drove the development of the SAX API that will be familiar to many XML developers who use Java) recently wrote Java is dead. Java stood out as a programming language (though not as a platform) in that...
     &lt;img src="http://feeds.feedburner.com/~r/oreilly/xml/~4/LLsq7yLcUA0" height="1" width="1"/&gt;</content>
<feedburner:origLink>http://broadcast.oreilly.com/2010/08/vale-java-scala-vala-palava.html</feedburner:origLink></entry>

<entry>
    <title>UK PRESTO</title>
    <link rel="alternate" type="text/html" href="http://feedproxy.google.com/~r/oreilly/xml/~3/9B0LYXHf3aI/uk-presto.html" />
    <id>tag:broadcast.oreilly.com,2010://53.41887</id>

    <published>2010-08-16T13:51:59Z</published>
    <updated>2010-08-16T13:51:59Z</updated>

    <summary>From the Cornell Law School's blog, Head of e-Services and Strategy at The (UK) National Archives, John Sheridan has written on the launch of Legislation.gov.uk. and mentioned this blog! A major influence on legislation.gov.uk was a blog posting by Rick...</summary>
    <author>
        <name>Rick Jelliffe</name>
        
    </author>
    
    <category term="egovernment" label="e-government" scheme="http://www.sixapart.com/ns/types#tag" />
    <category term="egov" label="egov" scheme="http://www.sixapart.com/ns/types#tag" />
    <category term="opengovernment" label="open government" scheme="http://www.sixapart.com/ns/types#tag" />
    <category term="presto" label="presto" scheme="http://www.sixapart.com/ns/types#tag" />
    <category term="xml" label="xml" scheme="http://www.sixapart.com/ns/types#tag" />
    
    <content type="html" xml:lang="en" xml:base="http://broadcast.oreilly.com/">
        From the Cornell Law School's blog, Head of e-Services and Strategy at The (UK) National Archives, John Sheridan has written on the launch of Legislation.gov.uk. and mentioned this blog! A major influence on legislation.gov.uk was a blog posting by Rick...
     &lt;img src="http://feeds.feedburner.com/~r/oreilly/xml/~4/9B0LYXHf3aI" height="1" width="1"/&gt;</content>
<feedburner:origLink>http://broadcast.oreilly.com/2010/08/uk-presto.html</feedburner:origLink></entry>

<entry>
    <title>Deliberate non-conformances in XML Schema implementations</title>
    <link rel="alternate" type="text/html" href="http://feedproxy.google.com/~r/oreilly/xml/~3/3iP6o42BrhE/deliberate-non-conformances-in.html" />
    <id>tag:broadcast.oreilly.com,2010://53.41835</id>

    <published>2010-08-06T04:49:01Z</published>
    <updated>2010-08-06T04:49:01Z</updated>

    <summary>From SAXON's Michael Kay, on the XML-DEV mail list today: On interoperability, there are at least three reasons why you might get different results from different processors. One is because the specification leaves the behaviour of certain things implementation-defined (for...</summary>
    <author>
        <name>Rick Jelliffe</name>
        
    </author>
    
    <category term="standards" label="standards" scheme="http://www.sixapart.com/ns/types#tag" />
    <category term="xml" label="xml" scheme="http://www.sixapart.com/ns/types#tag" />
    <category term="xmlschemas" label="xml schemas" scheme="http://www.sixapart.com/ns/types#tag" />
    
    <content type="html" xml:lang="en" xml:base="http://broadcast.oreilly.com/">
        From SAXON's Michael Kay, on the XML-DEV mail list today: On interoperability, there are at least three reasons why you might get different results from different processors. One is because the specification leaves the behaviour of certain things implementation-defined (for...
     &lt;img src="http://feeds.feedburner.com/~r/oreilly/xml/~4/3iP6o42BrhE" height="1" width="1"/&gt;</content>
<feedburner:origLink>http://broadcast.oreilly.com/2010/08/deliberate-non-conformances-in.html</feedburner:origLink></entry>

<entry>
    <title>Schema languages as if annotation mattered</title>
    <link rel="alternate" type="text/html" href="http://feedproxy.google.com/~r/oreilly/xml/~3/TNDJnwgaaLU/schema-languages-as-if-annotat.html" />
    <id>tag:broadcast.oreilly.com,2010://53.40344</id>

    <published>2010-07-26T08:25:02Z</published>
    <updated>2010-07-26T08:25:02Z</updated>

    <summary>In 2001 we had an interesting exchange about schema languages on the XML-DEV mail list. I had written Are we losing out because of grammars?.  What do I think of it now?  Four heads: disconnection, importance, a category error, and operator grammars. </summary>
    <author>
        <name>Rick Jelliffe</name>
        
    </author>
    
    <category term="schematron" label="schematron" scheme="http://www.sixapart.com/ns/types#tag" />
    <category term="xml" label="xml" scheme="http://www.sixapart.com/ns/types#tag" />
    
    <content type="html" xml:lang="en" xml:base="http://broadcast.oreilly.com/">
        In 2001 we had an interesting exchange about schema languages on the XML-DEV mail list. I had written &lt;i&gt;Are we losing out because of grammars?&lt;/i&gt;.  What do I think of it now?  Four heads: disconnection, importance, a category error, and operator grammars. 
     &lt;img src="http://feeds.feedburner.com/~r/oreilly/xml/~4/TNDJnwgaaLU" height="1" width="1"/&gt;</content>
<feedburner:origLink>http://broadcast.oreilly.com/2010/07/schema-languages-as-if-annotat.html</feedburner:origLink></entry>

<entry>
    <title>ZVON: the Information Plunger</title>
    <link rel="alternate" type="text/html" href="http://feedproxy.google.com/~r/oreilly/xml/~3/5pRTEuiHuCw/zvon-the-information-plunger.html" />
    <id>tag:broadcast.oreilly.com,2010://53.40226</id>

    <published>2010-07-09T08:34:32Z</published>
    <updated>2010-07-09T08:34:32Z</updated>

    <summary>I see the ZVON.org site has recently been renovated. It is a great site with tutorials or reference material on dozens of Web-related topics. Highly recommended. The site slogan is ZVON.org cleaning information pipelines but the logo says ZVON the...</summary>
    <author>
        <name>Rick Jelliffe</name>
        
    </author>
    
    <category term="schematron" label="schematron" scheme="http://www.sixapart.com/ns/types#tag" />
    <category term="xml" label="xml" scheme="http://www.sixapart.com/ns/types#tag" />
    
    <content type="html" xml:lang="en" xml:base="http://broadcast.oreilly.com/">
        I see the ZVON.org site has recently been renovated. It is a great site with tutorials or reference material on dozens of Web-related topics. Highly recommended. The site slogan is ZVON.org cleaning information pipelines but the logo says ZVON the...
     &lt;img src="http://feeds.feedburner.com/~r/oreilly/xml/~4/5pRTEuiHuCw" height="1" width="1"/&gt;</content>
<feedburner:origLink>http://broadcast.oreilly.com/2010/07/zvon-the-information-plunger.html</feedburner:origLink></entry>

<entry>
    <title>Highly Generic Schemas</title>
    <link rel="alternate" type="text/html" href="http://feedproxy.google.com/~r/oreilly/xml/~3/-t2EJnoIxGk/highly-generic-schemas.html" />
    <id>tag:broadcast.oreilly.com,2010://53.40216</id>

    <published>2010-07-07T06:54:00Z</published>
    <updated>2010-07-07T06:54:00Z</updated>

    <summary>Developer Christophe Lauret recently commented: "A schema is like an aircraft: it can be designed for stability or maneuverability but not both." I recently have been trying a different method for designing intermediate schemas in publication chains. It is an exercise in taking the three-layer model for XML with Schematron to an extreme. The best name I can think of this is Highly Generic Schemas.</summary>
    <author>
        <name>Rick Jelliffe</name>
        
    </author>
    
    <category term="relaxng" label="relax ng" scheme="http://www.sixapart.com/ns/types#tag" />
    <category term="schemas" label="schemas" scheme="http://www.sixapart.com/ns/types#tag" />
    <category term="schematron" label="schematron" scheme="http://www.sixapart.com/ns/types#tag" />
    <category term="xml" label="xml" scheme="http://www.sixapart.com/ns/types#tag" />
    <category term="xsd" label="xsd" scheme="http://www.sixapart.com/ns/types#tag" />
    <category term="xslt" label="xslt" scheme="http://www.sixapart.com/ns/types#tag" />
    
    <content type="html" xml:lang="en" xml:base="http://broadcast.oreilly.com/">
        Developer Christophe Lauret recently commented: "A schema is like an aircraft: it can be designed for stability or maneuverability but not both." I recently have been trying a different method for designing intermediate schemas in publication chains. It is an exercise in taking the three-layer model for XML with Schematron to an extreme. The best name I can think of this is Highly Generic Schemas.
     &lt;img src="http://feeds.feedburner.com/~r/oreilly/xml/~4/-t2EJnoIxGk" height="1" width="1"/&gt;</content>
<feedburner:origLink>http://broadcast.oreilly.com/2010/07/highly-generic-schemas.html</feedburner:origLink></entry>

<entry>
    <title>ODF and OOXML Translation: Working Draft 2 of ISO technical report out</title>
    <link rel="alternate" type="text/html" href="http://feedproxy.google.com/~r/oreilly/xml/~3/oyT62jmi2vo/odf-and-ooxml-translation-work.html" />
    <id>tag:broadcast.oreilly.com,2010://53.40170</id>

    <published>2010-06-28T17:07:44Z</published>
    <updated>2010-06-28T17:07:44Z</updated>

    <summary>The gnomes of ISO (err, ISO/IEC JTC1 SC34 WG5) have released the second draft of their Technical Report comparing ODF and OOXML (PDF). It is up to 126 pages now, and much more fleshed out than the first draft. One...</summary>
    <author>
        <name>Rick Jelliffe</name>
        
    </author>
    
    <category term="odf" label="odf" scheme="http://www.sixapart.com/ns/types#tag" />
    <category term="ooxml" label="ooxml" scheme="http://www.sixapart.com/ns/types#tag" />
    <category term="xml" label="xml" scheme="http://www.sixapart.com/ns/types#tag" />
    
    <content type="html" xml:lang="en" xml:base="http://broadcast.oreilly.com/">
        The gnomes of ISO (err, ISO/IEC JTC1 SC34 WG5) have released the second draft of their Technical Report comparing ODF and OOXML (PDF). It is up to 126 pages now, and much more fleshed out than the first draft. One...
     &lt;img src="http://feeds.feedburner.com/~r/oreilly/xml/~4/oyT62jmi2vo" height="1" width="1"/&gt;</content>
<feedburner:origLink>http://broadcast.oreilly.com/2010/06/odf-and-ooxml-translation-work.html</feedburner:origLink></entry>

<entry>
    <title>Is ZIP in the public domain or not?</title>
    <link rel="alternate" type="text/html" href="http://feedproxy.google.com/~r/oreilly/xml/~3/TTfLDZuGIsk/is-zip-in-the-public-domain-or.html" />
    <id>tag:broadcast.oreilly.com,2010://53.40131</id>

    <published>2010-06-22T08:27:28Z</published>
    <updated>2010-06-22T08:27:28Z</updated>

    <summary>What is the IP status of ZIP? This is a question of interest to standardizers and developers implementing standards, because so many new standards use ZIP. ODF and OOXML for example. Here is what the current PKWARE site says (with...</summary>
    <author>
        <name>Rick Jelliffe</name>
        
    </author>
    
    <category term="xml" label="xml" scheme="http://www.sixapart.com/ns/types#tag" />
    <category term="zip" label="zip" scheme="http://www.sixapart.com/ns/types#tag" />
    
    <content type="html" xml:lang="en" xml:base="http://broadcast.oreilly.com/">
        What is the IP status of ZIP? This is a question of interest to standardizers and developers implementing standards, because so many new standards use ZIP. ODF and OOXML for example. Here is what the current PKWARE site says (with...
     &lt;img src="http://feeds.feedburner.com/~r/oreilly/xml/~4/TTfLDZuGIsk" height="1" width="1"/&gt;</content>
<feedburner:origLink>http://broadcast.oreilly.com/2010/06/is-zip-in-the-public-domain-or.html</feedburner:origLink></entry>

<entry>
    <title>Understanding C#: XML Comments</title>
    <link rel="alternate" type="text/html" href="http://feedproxy.google.com/~r/oreilly/xml/~3/H1o8BtD0EX0/understanding-c-xml-comments.html" />
    <id>tag:broadcast.oreilly.com,2010://53.40077</id>

    <published>2010-06-14T18:52:47Z</published>
    <updated>2010-06-14T18:52:47Z</updated>

    <summary>As C# developers get more experienced, there are a lot of things they pick up along the way that are really useful and important to know, even if they aren't necessarily directly code-related. One of those topics is XML comments, and I've been surprised at how many developers -- even really experienced ones -- don't use them, or even know about them. They're really useful, and they can help you build better software, even if they don't actually change the way your programs behave.</summary>
    <author>
        <name>Andrew Stellman</name>
        <uri>http://www.stellman-greene.com</uri>
    </author>
    
    <category term="c" label="c#" scheme="http://www.sixapart.com/ns/types#tag" />
    <category term="csharp" label="csharp" scheme="http://www.sixapart.com/ns/types#tag" />
    <category term="headfirst" label="head first" scheme="http://www.sixapart.com/ns/types#tag" />
    <category term="headfirst" label="headfirst" scheme="http://www.sixapart.com/ns/types#tag" />
    <category term="microsoft" label="microsoft" scheme="http://www.sixapart.com/ns/types#tag" />
    <category term="xml" label="xml" scheme="http://www.sixapart.com/ns/types#tag" />
    
    <content type="html" xml:lang="en" xml:base="http://broadcast.oreilly.com/">
        As C# developers get more experienced, there are a lot of things they pick up along the way that are really useful and important to know, even if they aren't necessarily directly code-related. One of those topics is XML comments, and I've been surprised at how many developers -- even really experienced ones -- don't use them, or even know about them. They're really useful, and they can help you build better software, even if they don't actually change the way your programs behave.
     &lt;img src="http://feeds.feedburner.com/~r/oreilly/xml/~4/H1o8BtD0EX0" height="1" width="1"/&gt;</content>
<feedburner:origLink>http://broadcast.oreilly.com/2010/06/understanding-c-xml-comments.html</feedburner:origLink></entry>

<entry>
    <title>Europe to force all 'significant market players' to provide information necessary for interoperability?</title>
    <link rel="alternate" type="text/html" href="http://feedproxy.google.com/~r/oreilly/xml/~3/FAuQjR9yyug/europe-to-force-all-significan.html" />
    <id>tag:broadcast.oreilly.com,2010://53.40074</id>

    <published>2010-06-12T05:54:26Z</published>
    <updated>2010-06-12T05:54:26Z</updated>

    <summary>Three news items caught my interest this week. all slightly related: Dr. Neelie Kroes has made a significant speech How to get more interoperability in Europe on practical steps on interoperability and standards. She presents this as building on the...</summary>
    <author>
        <name>Rick Jelliffe</name>
        
    </author>
    
    <category term="odf" label="odf" scheme="http://www.sixapart.com/ns/types#tag" />
    <category term="ooxml" label="ooxml" scheme="http://www.sixapart.com/ns/types#tag" />
    <category term="standards" label="standards" scheme="http://www.sixapart.com/ns/types#tag" />
    <category term="xml" label="xml" scheme="http://www.sixapart.com/ns/types#tag" />
    
    <content type="html" xml:lang="en" xml:base="http://broadcast.oreilly.com/">
        Three news items caught my interest this week. all slightly related: Dr. Neelie Kroes has made a significant speech How to get more interoperability in Europe on practical steps on interoperability and standards. She presents this as building on the...
     &lt;img src="http://feeds.feedburner.com/~r/oreilly/xml/~4/FAuQjR9yyug" height="1" width="1"/&gt;</content>
<feedburner:origLink>http://broadcast.oreilly.com/2010/06/europe-to-force-all-significan.html</feedburner:origLink></entry>

<entry>
    <title>Ruby Schematron</title>
    <link rel="alternate" type="text/html" href="http://feedproxy.google.com/~r/oreilly/xml/~3/2YXpKfmkymo/ruby-schematron.html" />
    <id>tag:broadcast.oreilly.com,2010://53.40006</id>

    <published>2010-06-04T03:25:04Z</published>
    <updated>2010-06-04T03:25:04Z</updated>

    <summary>Francesco Lazzarino has a project up at RubyForge for a Ruby runner for ISO Schematron. (Open source: MIT/ Consortium License) Schematron is a small ISO-standard language for making assertions or reports about patterns in and between XML documents, typically using...</summary>
    <author>
        <name>Rick Jelliffe</name>
        
    </author>
    
    <category term="ruby" label="ruby" scheme="http://www.sixapart.com/ns/types#tag" />
    <category term="schematron" label="schematron" scheme="http://www.sixapart.com/ns/types#tag" />
    <category term="xml" label="xml" scheme="http://www.sixapart.com/ns/types#tag" />
    
    <content type="html" xml:lang="en" xml:base="http://broadcast.oreilly.com/">
        Francesco Lazzarino has a project up at RubyForge for a Ruby runner for ISO Schematron. (Open source: MIT/ Consortium License) Schematron is a small ISO-standard language for making assertions or reports about patterns in and between XML documents, typically using...
     &lt;img src="http://feeds.feedburner.com/~r/oreilly/xml/~4/2YXpKfmkymo" height="1" width="1"/&gt;</content>
<feedburner:origLink>http://broadcast.oreilly.com/2010/06/ruby-schematron.html</feedburner:origLink></entry>

<entry>
    <title>Australian Government procurement policy on Open Standard document formats</title>
    <link rel="alternate" type="text/html" href="http://feedproxy.google.com/~r/oreilly/xml/~3/w-BZbI0MqxM/australian-government-procurem.html" />
    <id>tag:broadcast.oreilly.com,2010://53.39991</id>

    <published>2010-06-02T06:39:44Z</published>
    <updated>2010-06-02T06:39:44Z</updated>

    <summary>Over the last few years I have linked to various national government policies on Open Source software and procurement policies. But I see I omitted us in Australia. So here is what I can find, from 2005: Guide to Open...</summary>
    <author>
        <name>Rick Jelliffe</name>
        
    </author>
    
    <category term="government" label="government" scheme="http://www.sixapart.com/ns/types#tag" />
    <category term="standards" label="standards" scheme="http://www.sixapart.com/ns/types#tag" />
    <category term="xml" label="xml" scheme="http://www.sixapart.com/ns/types#tag" />
    
    <content type="html" xml:lang="en" xml:base="http://broadcast.oreilly.com/">
        Over the last few years I have linked to various national government policies on Open Source software and procurement policies. But I see I omitted us in Australia. So here is what I can find, from 2005: Guide to Open...
     &lt;img src="http://feeds.feedburner.com/~r/oreilly/xml/~4/w-BZbI0MqxM" height="1" width="1"/&gt;</content>
<feedburner:origLink>http://broadcast.oreilly.com/2010/06/australian-government-procurem.html</feedburner:origLink></entry>

<entry>
    <title>Four short links: 1 June 2010</title>
    <link rel="alternate" type="text/html" href="http://feedproxy.google.com/~r/oreilly/xml/~3/9A-mdD5Mk-E/four-short-links-1-june-2010.html" />
    <id>tag:radar.oreilly.com,2010://57.39984</id>

    <published>2010-06-01T10:00:00Z</published>
    <updated>2010-06-01T10:00:00Z</updated>

    <summary> XML in Legislature/Parliament Environments (Sean McGrath) -- quite detailed background on the use of XML in legislation drafting systems, and the problems caused by convention in that world--page/line number citations, in particular. (Quick gloat: NZ's legislature management system is kick-ass, and soon we'll switch from print authoritative to digital authoritative) Large-Scale Social Media Analysis with Hadoop -- In this...</summary>
    <author>
        <name>Nat Torkington</name>
        <uri>http://radar.oreilly.com/nat/</uri>
    </author>
    
        <category term="Data" scheme="http://www.sixapart.com/ns/types#category" />
    
    <category term="bigdata" label="big data" scheme="http://www.sixapart.com/ns/types#tag" />
    <category term="copyright" label="copyright" scheme="http://www.sixapart.com/ns/types#tag" />
    <category term="crowdflower" label="Crowdflower" scheme="http://www.sixapart.com/ns/types#tag" />
    <category term="crowdsourcing" label="crowdsourcing" scheme="http://www.sixapart.com/ns/types#tag" />
    <category term="gov20" label="gov20" scheme="http://www.sixapart.com/ns/types#tag" />
    <category term="hadoop" label="hadoop" scheme="http://www.sixapart.com/ns/types#tag" />
    <category term="socialgraph" label="social graph" scheme="http://www.sixapart.com/ns/types#tag" />
    <category term="xml" label="xml" scheme="http://www.sixapart.com/ns/types#tag" />
    
    <content type="html" xml:lang="en" xml:base="http://radar.oreilly.com/">
         XML in Legislature/Parliament Environments (Sean McGrath) -- quite detailed background on the use of XML in legislation drafting systems, and the problems caused by convention in that world--page/line number citations, in particular. (Quick gloat: NZ's legislature management system is kick-ass, and soon we'll switch from print authoritative to digital authoritative) Large-Scale Social Media Analysis with Hadoop -- In this...
     &lt;img src="http://feeds.feedburner.com/~r/oreilly/xml/~4/9A-mdD5Mk-E" height="1" width="1"/&gt;</content>
<feedburner:origLink>http://radar.oreilly.com/2010/06/four-short-links-1-june-2010.html</feedburner:origLink></entry>

<entry>
    <title>EGovernment at the Legislature</title>
    <link rel="alternate" type="text/html" href="http://feedproxy.google.com/~r/oreilly/xml/~3/xVUzq-K2kFw/egovernment-at-the-legislature.html" />
    <id>tag:broadcast.oreilly.com,2010://53.39976</id>

    <published>2010-05-29T06:27:17Z</published>
    <updated>2010-05-29T06:27:17Z</updated>

    <summary>Sean McGrath is writing a series around the design issues for KLISS (Kansas Legislative Information Services System) which his company is doing.</summary>
    <author>
        <name>Rick Jelliffe</name>
        
    </author>
    
    <category term="egovernment" label="egovernment" scheme="http://www.sixapart.com/ns/types#tag" />
    <category term="legislation" label="legislation" scheme="http://www.sixapart.com/ns/types#tag" />
    <category term="xml" label="xml" scheme="http://www.sixapart.com/ns/types#tag" />
    
    <content type="html" xml:lang="en" xml:base="http://broadcast.oreilly.com/">
        Sean McGrath is writing a series around the design issues for KLISS (Kansas Legislative Information Services System) which his company is doing.
     &lt;img src="http://feeds.feedburner.com/~r/oreilly/xml/~4/xVUzq-K2kFw" height="1" width="1"/&gt;</content>
<feedburner:origLink>http://broadcast.oreilly.com/2010/05/egovernment-at-the-legislature.html</feedburner:origLink></entry>

<entry>
    <title>An Open, Webby, Book-Publishing Platform</title>
    <link rel="alternate" type="text/html" href="http://feedproxy.google.com/~r/oreilly/xml/~3/sVEbdmo73Yg/-wordpress-as-book-publishing.html" />
    <id>tag:toc.oreilly.com,2010://40.39917</id>

    <published>2010-05-19T19:50:02Z</published>
    <updated>2010-05-19T19:50:02Z</updated>

    <summary>This short article outlines some ideas about an open source, online platform for making books, based on WordPress. </summary>
    <author>
        <name>Hugh McGuire</name>
        <uri>http://hughmcguire.net</uri>
    </author>
    
        <category term="Authoring" scheme="http://www.sixapart.com/ns/types#category" />
    
        <category term="Ebooks" scheme="http://www.sixapart.com/ns/types#category" />
    
        <category term="Open Questions" scheme="http://www.sixapart.com/ns/types#category" />
    
        <category term="Tools" scheme="http://www.sixapart.com/ns/types#category" />
    
    <category term="bookoven" label="bookoven" scheme="http://www.sixapart.com/ns/types#tag" />
    <category term="collaboration" label="collaboration" scheme="http://www.sixapart.com/ns/types#tag" />
    <category term="digtial" label="digtial" scheme="http://www.sixapart.com/ns/types#tag" />
    <category term="epub" label="epub" scheme="http://www.sixapart.com/ns/types#tag" />
    <category term="html" label="html" scheme="http://www.sixapart.com/ns/types#tag" />
    <category term="indesign" label="indesign" scheme="http://www.sixapart.com/ns/types#tag" />
    <category term="latex" label="LaTeX" scheme="http://www.sixapart.com/ns/types#tag" />
    <category term="mpub" label="MPub" scheme="http://www.sixapart.com/ns/types#tag" />
    <category term="online" label="online" scheme="http://www.sixapart.com/ns/types#tag" />
    <category term="opensource" label="open source" scheme="http://www.sixapart.com/ns/types#tag" />
    <category term="platform" label="platform" scheme="http://www.sixapart.com/ns/types#tag" />
    <category term="simonfraseruniversity" label="Simon Fraser University" scheme="http://www.sixapart.com/ns/types#tag" />
    <category term="wordpress" label="wordpress" scheme="http://www.sixapart.com/ns/types#tag" />
    <category term="xml" label="xml" scheme="http://www.sixapart.com/ns/types#tag" />
    
    <content type="html" xml:lang="en" xml:base="http://toc.oreilly.com/">
        This short article outlines some ideas about an open source, online platform for making books, based on WordPress. 
     &lt;img src="http://feeds.feedburner.com/~r/oreilly/xml/~4/sVEbdmo73Yg" height="1" width="1"/&gt;</content>
<feedburner:origLink>http://toc.oreilly.com/2010/05/-wordpress-as-book-publishing.html</feedburner:origLink></entry>

<entry>
    <title>An Open, Webby, Book-Publishing Platform</title>
    <link rel="alternate" type="text/html" href="http://feedproxy.google.com/~r/oreilly/xml/~3/SyiRQMM9W1s/-wordpress-as-book-publishing.html" />
    <id>tag:radar.oreilly.com,2010://57.42794</id>

    <published>2010-05-19T22:50:02Z</published>
    <updated>2010-05-19T22:50:02Z</updated>

    <summary>This short article outlines some ideas about an open source, online platform for making books, based on WordPress.</summary>
    <author>
        <name>Hugh McGuire</name>
        <uri>http://hughmcguire.net</uri>
    </author>
    
        <category term="Publishing" scheme="http://www.sixapart.com/ns/types#category" />
    
    <category term="bookoven" label="bookoven" scheme="http://www.sixapart.com/ns/types#tag" />
    <category term="collaboration" label="collaboration" scheme="http://www.sixapart.com/ns/types#tag" />
    <category term="digtial" label="digtial" scheme="http://www.sixapart.com/ns/types#tag" />
    <category term="epub" label="epub" scheme="http://www.sixapart.com/ns/types#tag" />
    <category term="html" label="html" scheme="http://www.sixapart.com/ns/types#tag" />
    <category term="indesign" label="indesign" scheme="http://www.sixapart.com/ns/types#tag" />
    <category term="latex" label="LaTeX" scheme="http://www.sixapart.com/ns/types#tag" />
    <category term="mpub" label="MPub" scheme="http://www.sixapart.com/ns/types#tag" />
    <category term="online" label="online" scheme="http://www.sixapart.com/ns/types#tag" />
    <category term="opensource" label="open source" scheme="http://www.sixapart.com/ns/types#tag" />
    <category term="platform" label="platform" scheme="http://www.sixapart.com/ns/types#tag" />
    <category term="simonfraseruniversity" label="Simon Fraser University" scheme="http://www.sixapart.com/ns/types#tag" />
    <category term="wordpress" label="wordpress" scheme="http://www.sixapart.com/ns/types#tag" />
    <category term="xml" label="xml" scheme="http://www.sixapart.com/ns/types#tag" />
    
    <content type="html" xml:lang="en" xml:base="http://radar.oreilly.com/">
        This short article outlines some ideas about an open source, online platform for making books, based on WordPress.
     &lt;img src="http://feeds.feedburner.com/~r/oreilly/xml/~4/SyiRQMM9W1s" height="1" width="1"/&gt;</content>
<feedburner:origLink>http://radar.oreilly.com/2010/05/-wordpress-as-book-publishing.html</feedburner:origLink></entry>

<entry>
    <title>Miguel de Icaza: we can't blame third parties for our failures</title>
    <link rel="alternate" type="text/html" href="http://feedproxy.google.com/~r/oreilly/xml/~3/nxj7el-LUhI/miguel-de-icaza-we-cant-blame.html" />
    <id>tag:broadcast.oreilly.com,2010://53.39807</id>

    <published>2010-05-05T01:42:46Z</published>
    <updated>2010-05-05T01:42:46Z</updated>

    <summary>I wish I did not agree with Miguel de Icaza's blog from last month The Right Spirit. I interpret him as not meaning "you should" when he says "we should": I think he is not being dogmatic. Here are some...</summary>
    <author>
        <name>Rick Jelliffe</name>
        
    </author>
    
    <category term="opensource" label="open source" scheme="http://www.sixapart.com/ns/types#tag" />
    <category term="xml" label="xml" scheme="http://www.sixapart.com/ns/types#tag" />
    
    <content type="html" xml:lang="en" xml:base="http://broadcast.oreilly.com/">
        I wish I did not agree with Miguel de Icaza's blog from last month The Right Spirit. I interpret him as not meaning "you should" when he says "we should": I think he is not being dogmatic. Here are some...
     &lt;img src="http://feeds.feedburner.com/~r/oreilly/xml/~4/nxj7el-LUhI" height="1" width="1"/&gt;</content>
<feedburner:origLink>http://broadcast.oreilly.com/2010/05/miguel-de-icaza-we-cant-blame.html</feedburner:origLink></entry>

<entry>
    <title>Tim O'Reilly State of the Internet Operating System</title>
    <link rel="alternate" type="text/html" href="http://feedproxy.google.com/~r/oreilly/xml/~3/j_-EFocxvv8/tim-oreilly-state-of-the-inter.html" />
    <id>tag:broadcast.oreilly.com,2010://53.39801</id>

    <published>2010-05-04T09:22:59Z</published>
    <updated>2010-05-04T09:22:59Z</updated>

    <summary>I usually don't link to posts here at oreilly.com (which kindly hosts this blog), but Tim O'Reilly has a strong pair of articles out: The State of the Internet Operating System in two parts: Part 1 and Handicapping the Internet...</summary>
    <author>
        <name>Rick Jelliffe</name>
        
    </author>
    
    <category term="consumerism" label="consumerism" scheme="http://www.sixapart.com/ns/types#tag" />
    <category term="standards" label="standards" scheme="http://www.sixapart.com/ns/types#tag" />
    <category term="xml" label="xml" scheme="http://www.sixapart.com/ns/types#tag" />
    
    <content type="html" xml:lang="en" xml:base="http://broadcast.oreilly.com/">
        I usually don't link to posts here at oreilly.com (which kindly hosts this blog), but Tim O'Reilly has a strong pair of articles out: The State of the Internet Operating System in two parts: Part 1 and Handicapping the Internet...
     &lt;img src="http://feeds.feedburner.com/~r/oreilly/xml/~4/j_-EFocxvv8" height="1" width="1"/&gt;</content>
<feedburner:origLink>http://broadcast.oreilly.com/2010/05/tim-oreilly-state-of-the-inter.html</feedburner:origLink></entry>

<entry>
    <title>Harmonization</title>
    <link rel="alternate" type="text/html" href="http://feedproxy.google.com/~r/oreilly/xml/~3/-oqI2R2Ov5A/harmonization.html" />
    <id>tag:broadcast.oreilly.com,2010://53.39800</id>

    <published>2010-05-04T06:13:30Z</published>
    <updated>2010-05-04T06:13:30Z</updated>

    <summary>It strikes me that harmonization of XML standards (i.e. where you have different XML standards covering much the same ground and you want a workable strategy for converging them) needs to be as much concerned with granularity issues as it...</summary>
    <author>
        <name>Rick Jelliffe</name>
        
    </author>
    
    <category term="schemas" label="schemas" scheme="http://www.sixapart.com/ns/types#tag" />
    <category term="xml" label="xml" scheme="http://www.sixapart.com/ns/types#tag" />
    
    <content type="html" xml:lang="en" xml:base="http://broadcast.oreilly.com/">
        It strikes me that harmonization of XML standards (i.e. where you have different XML standards covering much the same ground and you want a workable strategy for converging them) needs to be as much concerned with granularity issues as it...
     &lt;img src="http://feeds.feedburner.com/~r/oreilly/xml/~4/-oqI2R2Ov5A" height="1" width="1"/&gt;</content>
<feedburner:origLink>http://broadcast.oreilly.com/2010/05/harmonization.html</feedburner:origLink></entry>

</feed>
