<?xml version="1.0" encoding="utf-8"?>
<feed xmlns="http://www.w3.org/2005/Atom">
<title>Rick Jelliffe on O&apos;Reilly Broadcast</title>
<link rel="alternate" type="text/html" href="http://broadcast.oreilly.com/" />
<link rel="self" type="application/atom+xml" href="http://broadcast.oreilly.com/atom.xml" />
<id>tag:broadcast.oreilly.com,2008-08-07://53</id>
<updated>2012-03-17T05:18:36Z</updated>

<generator uri="http://www.sixapart.com/movabletype/">Movable Type Pro 4.21-en</generator>

<entry>
<title>XML&apos;s Dialect Problem</title>
<link rel="alternate" type="text/html" href="http://broadcast.oreilly.com/2012/03/xmls-dialect-problem.html" />
<id>tag:broadcast.oreilly.com,2012://53.48008</id>

<published>2012-03-17T05:18:36Z</published>
<updated>2012-03-17T05:18:36Z</updated>

<summary>XML standards and technologies do not provide an adequate layer for coping with dialects.</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/">
XML standards and technologies do not provide an adequate layer for coping with dialects.
</content>
</entry>

<entry>
<title>Joaquín Almunia gets it: &quot;Owners of ... standard essential patents are conferred a power .. that they cannot be allowed to misuse. &quot;</title>
<link rel="alternate" type="text/html" href="http://broadcast.oreilly.com/2012/02/joaquin-almunia-gets-it-owners.html" />
<id>tag:broadcast.oreilly.com,2012://53.47819</id>

<published>2012-02-12T06:16:05Z</published>
<updated>2012-02-12T06:16:05Z</updated>

<summary>I think Almunia&apos;s speech does not go far enough: it still sees standardization as an escape hatch that a company that finds itself in a market dominating position can use when challenged.</summary>
<author>
<name>Rick Jelliffe</name>

</author>

<category term="patents" label="patents" scheme="http://www.sixapart.com/ns/types#tag" />
<category term="standards" label="standards" scheme="http://www.sixapart.com/ns/types#tag" />

<content type="html" xml:lang="en" xml:base="http://broadcast.oreilly.com/">
I think Almunia&apos;s speech does not go far enough: it still sees standardization as an escape hatch that a company that finds itself in a market dominating position can use when challenged.
</content>
</entry>

<entry>
<title>Using Schematron to validate forms in a web browser</title>
<link rel="alternate" type="text/html" href="http://broadcast.oreilly.com/2012/01/using-schematron-to-validate-f.html" />
<id>tag:broadcast.oreilly.com,2012://53.47667</id>

<published>2012-01-08T04:19:26Z</published>
<updated>2012-01-08T04:19:26Z</updated>

<summary>Web programmer Daniel Epstein has a series up on his blog Ursa Dimished, called Simplify with an XML data model: it includes a page on using Schematron for browser-side validation of forms. Daniel is another developer who is frustrated that...</summary>
<author>
<name>Rick Jelliffe</name>

</author>

<category term="ajax" label="ajax" scheme="http://www.sixapart.com/ns/types#tag" />
<category term="javascript" label="javascript" scheme="http://www.sixapart.com/ns/types#tag" />
<category term="schematron" label="schematron" scheme="http://www.sixapart.com/ns/types#tag" />

<content type="html" xml:lang="en" xml:base="http://broadcast.oreilly.com/">
Web programmer Daniel Epstein has a series up on his blog Ursa Dimished, called Simplify with an XML data model: it includes a page on using Schematron for browser-side validation of forms. Daniel is another developer who is frustrated that...
</content>
</entry>

<entry>
<title>Mouse hanging by a thread?</title>
<link rel="alternate" type="text/html" href="http://broadcast.oreilly.com/2011/10/mouse-hanging-by-a-thread.html" />
<id>tag:broadcast.oreilly.com,2011://53.47306</id>

<published>2011-10-09T00:49:00Z</published>
<updated>2011-10-09T00:49:00Z</updated>

<summary>Recent research suggests that the XMRV assay methods are not reliable</summary>
<author>
<name>Rick Jelliffe</name>

</author>

<category term="cfs" label="CFS" scheme="http://www.sixapart.com/ns/types#tag" />

<content type="html" xml:lang="en" xml:base="http://broadcast.oreilly.com/">
Recent research suggests that the XMRV assay methods are not reliable
</content>
</entry>

<entry>
<title>XML Schema development approaches</title>
<link rel="alternate" type="text/html" href="http://broadcast.oreilly.com/2011/08/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...
</content>
</entry>

<entry>
<title>ETL and Publishing</title>
<link rel="alternate" type="text/html" href="http://broadcast.oreilly.com/2011/06/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...
</content>
</entry>

<entry>
<title>Australian Whole-of-Government Common Operating Environment Policy and OOXML</title>
<link rel="alternate" type="text/html" href="http://broadcast.oreilly.com/2011/01/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&apos;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&apos;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&apos;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&apos;s WCAG 2.0 guidelines for accessibility, or that...
</content>
</entry>

<entry>
<title>What to do when you have get a mysterious spotted fever: improve Wikipedia!</title>
<link rel="alternate" type="text/html" href="http://broadcast.oreilly.com/2011/01/what-to-do-when-you-have-get-a.html" />
<id>tag:broadcast.oreilly.com,2011://53.43822</id>

<published>2011-01-10T11:51:53Z</published>
<updated>2011-01-10T11:51:53Z</updated>

<summary>If you get some exotic illness, and you know what it is, make sure the Wikipedia entries have good links to credible sites</summary>
<author>
<name>Rick Jelliffe</name>

</author>

<category term="wikipedia" label="wikipedia" scheme="http://www.sixapart.com/ns/types#tag" />

<content type="html" xml:lang="en" xml:base="http://broadcast.oreilly.com/">
If you get some exotic illness, and you know what it is, make sure the Wikipedia entries have good links to credible sites
</content>
</entry>

<entry>
<title>Nuke!</title>
<link rel="alternate" type="text/html" href="http://broadcast.oreilly.com/2010/12/if-i-wanted-an-xml-for-2010-wh.html" />
<id>tag:broadcast.oreilly.com,2010://53.43569</id>

<published>2010-12-08T14:34:32Z</published>
<updated>2010-12-08T14:34:32Z</updated>

<summary>Is it good, bad or indifferent that JSON is taking over several kinds of data transfers that XML had been used for and in particular does JSON show up XML 1.0&apos;s complexity?  In short, is it time to overhaul XML? Rather than dissecting corpses of old arguments, I thought I&apos;d figure out what I&apos;d like to see in a re-developed XML. See here is my armchair redesign: New XML which I call Nuke! </summary>
<author>
<name>Rick Jelliffe</name>

</author>

<category term="json" label="JSON" 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/">
Is it good, bad or indifferent that JSON is taking over several kinds of data transfers that XML had been used for and in particular does JSON show up XML 1.0&apos;s complexity?  In short, is it time to overhaul XML? Rather than dissecting corpses of old arguments, I thought I&apos;d figure out what I&apos;d like to see in a re-developed XML. See here is my armchair redesign: New XML which I call Nuke! 
</content>
</entry>

<entry>
<title>Schema coverage report</title>
<link rel="alternate" type="text/html" href="http://broadcast.oreilly.com/2010/10/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...
</content>
</entry>

<entry>
<title>Mouse Wars</title>
<link rel="alternate" type="text/html" href="http://broadcast.oreilly.com/2010/10/mouse-wars.html" />
<id>tag:broadcast.oreilly.com,2010://53.43141</id>

<published>2010-10-16T07:28:20Z</published>
<updated>2010-10-16T07:28:20Z</updated>

<summary>In October 2010, the US NIH held a Workshop on XMRV with many new studies presented from different sources.   The results are very striking.</summary>
<author>
<name>Rick Jelliffe</name>

</author>

<category term="xmrv" label="xmrv" scheme="http://www.sixapart.com/ns/types#tag" />

<content type="html" xml:lang="en" xml:base="http://broadcast.oreilly.com/">
In October 2010, the US NIH held a Workshop on XMRV with many new studies presented from different sources.   The results are very striking.
</content>
</entry>

<entry>
<title>Under-estimating XML as just a Tree</title>
<link rel="alternate" type="text/html" href="http://broadcast.oreilly.com/2010/10/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. 
</content>
</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://broadcast.oreilly.com/2010/09/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&apos;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&apos;t think there...
</content>
</entry>

<entry>
<title>Vale Java? Scala Vala palava</title>
<link rel="alternate" type="text/html" href="http://broadcast.oreilly.com/2010/08/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...
</content>
</entry>

<entry>
<title>UK PRESTO</title>
<link rel="alternate" type="text/html" href="http://broadcast.oreilly.com/2010/08/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&apos;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&apos;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...
</content>
</entry>

</feed> 