<?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>2009-11-23T05:54:32Z</updated>

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

<entry>
<title>How fuzzy should a date be?</title>
<link rel="alternate" type="text/html" href="http://broadcast.oreilly.com/2009/11/how-fuzzy-should-a-date-be.html" />
<id>tag:broadcast.oreilly.com,2009://53.38570</id>

<published>2009-11-23T05:54:32Z</published>
<updated>2009-11-23T05:54:32Z</updated>

<summary>From Bruce D&apos;Arcus&apos; Darcusblog comes a pointer on a U.S. Library of Congress initiative for a better date format Extended Date Time Format (EDTF). ISO 8601&apos;s problem is that almost anything is a date: if my memory serves me, some...</summary>
<author>
<name>Rick Jelliffe</name>

</author>

<category term="dates" label="dates" 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 Bruce D&apos;Arcus&apos; Darcusblog comes a pointer on a U.S. Library of Congress initiative for a better date format Extended Date Time Format (EDTF). ISO 8601&apos;s problem is that almost anything is a date: if my memory serves me, some...
</content>
</entry>

<entry>
<title>My feed</title>
<link rel="alternate" type="text/html" href="http://broadcast.oreilly.com/2009/11/my-feed.html" />
<id>tag:broadcast.oreilly.com,2009://53.38502</id>

<published>2009-11-14T10:41:29Z</published>
<updated>2009-11-14T10:41:29Z</updated>

<summary>A couple of people have asked again this week for the RSS feed address for my blog. Here is is: I believe you can get the individual feeds for other bloggers on OReilly sites using the same URL and the...</summary>
<author>
<name>Rick Jelliffe</name>

</author>

<category term="blog" label="blog" scheme="http://www.sixapart.com/ns/types#tag" />
<category term="rss" label="rss" 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/">
A couple of people have asked again this week for the RSS feed address for my blog. Here is is: I believe you can get the individual feeds for other bloggers on OReilly sites using the same URL and the...
</content>
</entry>

<entry>
<title>Schematron and time: complex event processing?</title>
<link rel="alternate" type="text/html" href="http://broadcast.oreilly.com/2009/11/schematron-and-time-complex-ev.html" />
<id>tag:broadcast.oreilly.com,2009://53.38501</id>

<published>2009-11-14T03:37:20Z</published>
<updated>2009-11-14T03:37:20Z</updated>

<summary>I have been thinking a little bit about whether Schematron&apos;s pattern approach could be applied to complex event processing where the input is a stream of discrete XML documents, for example each one being a reading from a set of...</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 have been thinking a little bit about whether Schematron&apos;s pattern approach could be applied to complex event processing where the input is a stream of discrete XML documents, for example each one being a reading from a set of...
</content>
</entry>

<entry>
<title>Adam Bosworth on picking standards</title>
<link rel="alternate" type="text/html" href="http://broadcast.oreilly.com/2009/11/adam-bosworth-on-picking-stand.html" />
<id>tag:broadcast.oreilly.com,2009://53.38472</id>

<published>2009-11-11T10:03:26Z</published>
<updated>2009-11-11T10:03:26Z</updated>

<summary>I enjoyed Adam Bosworth&apos;s Talking to DC. But don&apos;t his points apply to most software/interface specifications, without being doctrinaire? What is the difference between his Standards work best when they are focused and, say, Agile&apos;s YAGNI?...</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" />

<content type="html" xml:lang="en" xml:base="http://broadcast.oreilly.com/">
I enjoyed Adam Bosworth&apos;s Talking to DC. But don&apos;t his points apply to most software/interface specifications, without being doctrinaire? What is the difference between his Standards work best when they are focused and, say, Agile&apos;s YAGNI?...
</content>
</entry>

<entry>
<title>Leaked Draft of EU Interop Framework</title>
<link rel="alternate" type="text/html" href="http://broadcast.oreilly.com/2009/11/leaked-draft-of-eu-interop-fra.html" />
<id>tag:broadcast.oreilly.com,2009://53.38471</id>

<published>2009-11-11T08:02:24Z</published>
<updated>2009-11-11T08:02:24Z</updated>

<summary>Two months ago I alerted readers Europeans: only two weeks left to comment on ICT &amp; standards whitepaper. I am not sure on which dots actually join up, but a Dutch website has what is claimed to be a leaked late draft in English of European Interoperability Framework for European Public Services (EIF) Version 2.0. Here are some of the general recommendations related to standards and issues raised on this blog.</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" />

<content type="html" xml:lang="en" xml:base="http://broadcast.oreilly.com/">
Two months ago I alerted readers Europeans: only two weeks left to comment on ICT &amp; standards whitepaper. I am not sure on which dots actually join up, but a Dutch website has what is claimed to be a leaked late draft in English of European Interoperability Framework for European Public Services (EIF) Version 2.0. Here are some of the general recommendations related to standards and issues raised on this blog.
</content>
</entry>

<entry>
<title>Tactical and strategic XML design</title>
<link rel="alternate" type="text/html" href="http://broadcast.oreilly.com/2009/11/tactical-and-strategic-xml-des.html" />
<id>tag:broadcast.oreilly.com,2009://53.38436</id>

<published>2009-11-06T03:35:58Z</published>
<updated>2009-11-06T03:35:58Z</updated>

<summary>So I guess when we look at a system&apos;s architecture, the first thing we can do is ask &apos;Is this XML here being used strategically or tactically?&apos;  A strategic use might be, for example, to allow long-term archiving; a tactical use might be XML in AJAX (where using JSON would be another tactic.)  If the answer is tactical, then we can ask &apos;Is it implemented in a way that allows flexible rearrangement, when a different tactic becomes appropriate?&apos;   </summary>
<author>
<name>Rick Jelliffe</name>

</author>

<category term="architecture" label="architecture" scheme="http://www.sixapart.com/ns/types#tag" />
<category term="design" label="design" 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/">
So I guess when we look at a system&apos;s architecture, the first thing we can do is ask &apos;Is this XML here being used strategically or tactically?&apos;  A strategic use might be, for example, to allow long-term archiving; a tactical use might be XML in AJAX (where using JSON would be another tactic.)  If the answer is tactical, then we can ask &apos;Is it implemented in a way that allows flexible rearrangement, when a different tactic becomes appropriate?&apos;   
</content>
</entry>

<entry>
<title>Participation, participation, participation</title>
<link rel="alternate" type="text/html" href="http://broadcast.oreilly.com/2009/10/participation-participation-pa.html" />
<id>tag:broadcast.oreilly.com,2009://53.38337</id>

<published>2009-10-29T08:17:43Z</published>
<updated>2009-10-29T08:17:43Z</updated>

<summary>IBM marketing guy Rob Weir has half of a new series of blogs  The Final OOXML Update up. Readers may be surprised that I agree with many of the points he makes, among them, the importance of a balance of interests, the need for continued participation and the need for followthrough on the BRM decisions. </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/">
IBM marketing guy Rob Weir has half of a new series of blogs  The Final OOXML Update up. Readers may be surprised that I agree with many of the points he makes, among them, the importance of a balance of interests, the need for continued participation and the need for followthrough on the BRM decisions. 
</content>
</entry>

<entry>
<title>The indexed XML website as a commodity</title>
<link rel="alternate" type="text/html" href="http://broadcast.oreilly.com/2009/10/the-indexed-xml-website-as-a-c.html" />
<id>tag:broadcast.oreilly.com,2009://53.38186</id>

<published>2009-10-14T13:59:40Z</published>
<updated>2009-10-14T13:59:40Z</updated>

<summary>Reviewing a few long-term, continuing multi-publishing projects I have been involved in recently, I am struck that several are morphing in a particular direction. The projects might have started as publishing paper or webpages, and moved to publishing high-level XML, but increasingly the commodity that needs to be packaged and distributed (for re-skinning and re-use by third parties) is the whole indexed dataset: in effect the website (without the implication of HTML pages.)  The client-person doesn&apos;t GET a webpage, they get a whole website (this is for B2B not B2C.)</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/">
Reviewing a few long-term, continuing multi-publishing projects I have been involved in recently, I am struck that several are morphing in a particular direction. The projects might have started as publishing paper or webpages, and moved to publishing high-level XML, but increasingly the commodity that needs to be packaged and distributed (for re-skinning and re-use by third parties) is the whole indexed dataset: in effect the website (without the implication of HTML pages.)  The client-person doesn&apos;t GET a webpage, they get a whole website (this is for B2B not B2C.)
</content>
</entry>

<entry>
<title>What are useful Software Engineering approaches for legislated requirements?</title>
<link rel="alternate" type="text/html" href="http://broadcast.oreilly.com/2009/09/what-are-useful-software-engin.html" />
<id>tag:broadcast.oreilly.com,2009://53.38057</id>

<published>2009-09-30T06:02:29Z</published>
<updated>2009-09-30T06:02:29Z</updated>

<summary>More projects seem to be coming across my desk that ultimately involve building information systems whose primary requirements come from legislation or regulations. And sometimes even the detailed requirements. Legislation is sometimes quite a nice Requirement Specification: it is expressed...</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/">
More projects seem to be coming across my desk that ultimately involve building information systems whose primary requirements come from legislation or regulations. And sometimes even the detailed requirements. Legislation is sometimes quite a nice Requirement Specification: it is expressed...
</content>
</entry>

<entry>
<title>Now I have seen everything!</title>
<link rel="alternate" type="text/html" href="http://broadcast.oreilly.com/2009/09/now-i-have-seen-everything.html" />
<id>tag:broadcast.oreilly.com,2009://53.38056</id>

<published>2009-09-30T05:01:43Z</published>
<updated>2009-09-30T05:01:43Z</updated>

<summary>I have always thought the context-senstive { a^n, b^n, c^n: n &gt;=1} s was a kind of theoretical construct that you would never see in a real-life XML document.  Today, I have actually seen one!</summary>
<author>
<name>Rick Jelliffe</name>

</author>

<category term="schema" label="schema" 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 have always thought the context-senstive { a^n, b^n, c^n: n &gt;=1} s was a kind of theoretical construct that you would never see in a real-life XML document.  Today, I have actually seen one!
</content>
</entry>

<entry>
<title>Linking a public government dataset into the semantic web with RDF</title>
<link rel="alternate" type="text/html" href="http://broadcast.oreilly.com/2009/09/linking-a-public-government-da.html" />
<id>tag:broadcast.oreilly.com,2009://53.38035</id>

<published>2009-09-28T05:27:44Z</published>
<updated>2009-09-28T05:27:44Z</updated>

<summary>A few months ago, a client wanted to dip their toes in the semantic web. So I took a fresh look at the status quo, and where the current sweet spot is. Here are my conclusions, and how things panned out for this particular job. </summary>
<author>
<name>Rick Jelliffe</name>

</author>

<category term="rdf" label="rdf" 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/">
A few months ago, a client wanted to dip their toes in the semantic web. So I took a fresh look at the status quo, and where the current sweet spot is. Here are my conclusions, and how things panned out for this particular job. 
</content>
</entry>

<entry>
<title>The Norwegians still get it!</title>
<link rel="alternate" type="text/html" href="http://broadcast.oreilly.com/2009/09/the-norwegians-still-get-it.html" />
<id>tag:broadcast.oreilly.com,2009://53.38034</id>

<published>2009-09-28T00:53:50Z</published>
<updated>2009-09-28T00:53:50Z</updated>

<summary>These all seem the right way to do things: a user decides what it needs for specific uses, is pragmatic or generous about timing, and doesn&apos;t exclude any of the technical eco-systems from equal participation. I think it also represents a real challenge to the software vendors: starting 2011 they will have to compete on features, quality and support, not file format: they won&apos;t have the supposed lock-in to benefit or excuse them from providing value. </summary>
<author>
<name>Rick Jelliffe</name>

</author>

<category term="odf" label="odf" 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/">
These all seem the right way to do things: a user decides what it needs for specific uses, is pragmatic or generous about timing, and doesn&apos;t exclude any of the technical eco-systems from equal participation. I think it also represents a real challenge to the software vendors: starting 2011 they will have to compete on features, quality and support, not file format: they won&apos;t have the supposed lock-in to benefit or excuse them from providing value. 
</content>
</entry>

<entry>
<title>Programming languages available in-house determines architecture?</title>
<link rel="alternate" type="text/html" href="http://broadcast.oreilly.com/2009/09/inhouse-programming-language-c.html" />
<id>tag:broadcast.oreilly.com,2009://53.37993</id>

<published>2009-09-22T15:07:11Z</published>
<updated>2009-09-22T15:07:11Z</updated>

<summary>A solid refactoring, the kind that you don&apos;t do every year, also needs to involve a tooling up, but scoped to making the new desired architecture something that programmers won&apos;t subvert but find natural. In a way, the programming languages become  the interfaces that  provides the boundaries for the layers of the system. </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/">
A solid refactoring, the kind that you don&apos;t do every year, also needs to involve a tooling up, but scoped to making the new desired architecture something that programmers won&apos;t subvert but find natural. In a way, the programming languages become  the interfaces that  provides the boundaries for the layers of the system. 
</content>
</entry>

<entry>
<title>W3C Widgets: Yet another XML-in-ZIP file format?</title>
<link rel="alternate" type="text/html" href="http://broadcast.oreilly.com/2009/09/w3c-widgets-yet-another-xml-in.html" />
<id>tag:broadcast.oreilly.com,2009://53.37983</id>

<published>2009-09-21T03:37:53Z</published>
<updated>2009-09-21T03:37:53Z</updated>

<summary>It will be interesting to see how big a widget can get: can it be a full word processor? And what makes widget so different from applets?</summary>
<author>
<name>Rick Jelliffe</name>

</author>

<category term="html" label="html" 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 will be interesting to see how big a widget can get: can it be a full word processor? And what makes widget so different from applets?
</content>
</entry>

<entry>
<title>Beware of browser and OS numbers</title>
<link rel="alternate" type="text/html" href="http://broadcast.oreilly.com/2009/09/beware-of-browser-and-os-numbe.html" />
<id>tag:broadcast.oreilly.com,2009://53.37962</id>

<published>2009-09-17T05:45:37Z</published>
<updated>2009-09-17T05:45:37Z</updated>

<summary>For some markets the success/domination by Microsoft is much stronger than blanket figures indicate.</summary>
<author>
<name>Rick Jelliffe</name>

</author>

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

<content type="html" xml:lang="en" xml:base="http://broadcast.oreilly.com/">
For some markets the success/domination by Microsoft is much stronger than blanket figures indicate.
</content>
</entry>

</feed> 