<?xml version="1.0" encoding="utf-8"?>
<feed xmlns="http://www.w3.org/2005/Atom">
<title>Philip Fennell 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-09-14T20:51:19Z</updated>

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

<entry>
<title>XProc and SMIL: Orchestrating Pipelines</title>
<link rel="alternate" type="text/html" href="http://broadcast.oreilly.com/2009/09/xproc-and-smil-orchestrating-p.html" />
<id>tag:broadcast.oreilly.com,2009://53.36039</id>

<published>2009-09-14T20:51:19Z</published>
<updated>2009-09-14T20:51:19Z</updated>

<summary>Although the W3C&apos;s XML Pipeline Language (XProc) hasn&apos;t even left the stable yet, people are already looking beyond its original purpose. XProc was designed to solve the problem of how to describe the joining together of multiple XML processing steps. So, the question is, how do you extend XProc to handle new features like explicit concurrency...</summary>
<author>
<name>Philip Fennell</name>

</author>

<category term="orchestration" label="orchestration" scheme="http://www.sixapart.com/ns/types#tag" />
<category term="pipeline" label="pipeline" scheme="http://www.sixapart.com/ns/types#tag" />
<category term="smil" label="smil" scheme="http://www.sixapart.com/ns/types#tag" />
<category term="xml" label="xml" scheme="http://www.sixapart.com/ns/types#tag" />
<category term="xproc" label="xproc" scheme="http://www.sixapart.com/ns/types#tag" />

<content type="html" xml:lang="en" xml:base="http://broadcast.oreilly.com/">
Although the W3C&apos;s XML Pipeline Language (XProc) hasn&apos;t even left the stable yet, people are already looking beyond its original purpose. XProc was designed to solve the problem of how to describe the joining together of multiple XML processing steps. So, the question is, how do you extend XProc to handle new features like explicit concurrency...
</content>
</entry>

<entry>
<title>Are we losing the Declarative Web?</title>
<link rel="alternate" type="text/html" href="http://broadcast.oreilly.com/2009/03/are-we-losing-the-declarative.html" />
<id>tag:broadcast.oreilly.com,2009://53.35734</id>

<published>2009-03-31T12:11:11Z</published>
<updated>2009-03-31T12:11:11Z</updated>

<summary>I saw something the other day that I was both intrigued and bothered by in equal measure. &apos;Mozilla and the Khronos Group Announce Initiative to Bring Accelerated 3D to the Web&apos;. Apparently, the working group will look at exposing OpenGL capabilities within ECMAScript. The intriguing part is that, as a fan of 3D Computer Graphics and Animation this has got to be a good sign, especially if it is exposed in this way; but the bothersome bit is how people will end up using it because it has been exposed in this way. The crux of the problem for me is the question, JavaScript - what&apos;s it good for? Absolutely...</summary>
<author>
<name>Philip Fennell</name>

</author>

<category term="javascript" label="javascript" scheme="http://www.sixapart.com/ns/types#tag" />
<category term="opengl" label="opengl" 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://broadcast.oreilly.com/">
I saw something the other day that I was both intrigued and bothered by in equal measure. &apos;Mozilla and the Khronos Group Announce Initiative to Bring Accelerated 3D to the Web&apos;. Apparently, the working group will look at exposing OpenGL capabilities within ECMAScript. The intriguing part is that, as a fan of 3D Computer Graphics and Animation this has got to be a good sign, especially if it is exposed in this way; but the bothersome bit is how people will end up using it because it has been exposed in this way. The crux of the problem for me is the question, JavaScript - what&apos;s it good for? Absolutely...
</content>
</entry>

<entry>
<title>To err is human, to Erlang divine</title>
<link rel="alternate" type="text/html" href="http://broadcast.oreilly.com/2009/03/to-err-is-human-to-erlang-divi.html" />
<id>tag:broadcast.oreilly.com,2009://53.35452</id>

<published>2009-03-09T11:27:12Z</published>
<updated>2009-03-09T11:27:12Z</updated>

<summary>About three years ago I was really getting into Functional Programming (FP). Up until then I had been doing a lot of work with XSLT, which has many FP characteristics; Single Assignment, Lazy Evaluation, and the like, but I wanted to explore further what FP had to offer. Then, more by luck than judgement, I ran into Erlang, and we just clicked. To me, it seemed an elegant and expressive language, and a Functional one at that.</summary>
<author>
<name>Philip Fennell</name>

</author>

<category term="erlang" label="erlang" scheme="http://www.sixapart.com/ns/types#tag" />
<category term="programminglanguages" label="programming languages" scheme="http://www.sixapart.com/ns/types#tag" />

<content type="html" xml:lang="en" xml:base="http://broadcast.oreilly.com/">
About three years ago I was really getting into Functional Programming (FP). Up until then I had been doing a lot of work with XSLT, which has many FP characteristics; Single Assignment, Lazy Evaluation, and the like, but I wanted to explore further what FP had to offer. Then, more by luck than judgement, I ran into Erlang, and we just clicked. To me, it seemed an elegant and expressive language, and a Functional one at that.
</content>
</entry>

<entry>
<title>When you&apos;re SMIL-ing, when you&apos;re SMIL-ing...</title>
<link rel="alternate" type="text/html" href="http://broadcast.oreilly.com/2009/01/when-youre-smiling-when-youre.html" />
<id>tag:broadcast.oreilly.com,2009://53.34692</id>

<published>2009-01-08T15:00:00Z</published>
<updated>2009-01-08T15:00:00Z</updated>

<summary>...the whole world smiles with you. No it&apos;s not a typo, the acronym for the W3C&apos;s Synchronized Multimedia Integration Language (SMIL) is pronounced &quot;smile&quot;, and the SMIL Animation module sure makes me smile; even more so given the fact that I&apos;ve seen it mentioned, outside of the usual multi-media circles, three times last year and once already this year...</summary>
<author>
<name>Philip Fennell</name>

</author>

<category term="animation" label="animation" scheme="http://www.sixapart.com/ns/types#tag" />
<category term="prototyping" label="prototyping" scheme="http://www.sixapart.com/ns/types#tag" />
<category term="ria" label="ria" scheme="http://www.sixapart.com/ns/types#tag" />
<category term="smil" label="smil" 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 whole world smiles with you. No it&apos;s not a typo, the acronym for the W3C&apos;s Synchronized Multimedia Integration Language (SMIL) is pronounced &quot;smile&quot;, and the SMIL Animation module sure makes me smile; even more so given the fact that I&apos;ve seen it mentioned, outside of the usual multi-media circles, three times last year and once already this year...
</content>
</entry>

<entry>
<title>XForms, a pause for reflection</title>
<link rel="alternate" type="text/html" href="http://broadcast.oreilly.com/2008/12/xforms-a-pause-for-reflection.html" />
<id>tag:broadcast.oreilly.com,2008://53.34667</id>

<published>2008-12-17T22:07:30Z</published>
<updated>2008-12-17T22:07:30Z</updated>

<summary>The other day I had what could only be described as a &apos;Roy Scheider moment&apos;, you know the bit in the film Jaws where the camera tracks-in whilst zooming-out at the same time. Well, whilst debugging an XForms enabled application, the Mozilla XForms plug-in had exposed the host document, XForms and all, as the content of the empty xf:instance. How odd. I mean, what good is that? That&apos;s when it struck me in a Roy Scheider sort of way; this was Reflection, the ability of a program to look at itself and change its behaviour.</summary>
<author>
<name>Philip Fennell</name>

</author>

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

<content type="html" xml:lang="en" xml:base="http://broadcast.oreilly.com/">
The other day I had what could only be described as a &apos;Roy Scheider moment&apos;, you know the bit in the film Jaws where the camera tracks-in whilst zooming-out at the same time. Well, whilst debugging an XForms enabled application, the Mozilla XForms plug-in had exposed the host document, XForms and all, as the content of the empty xf:instance. How odd. I mean, what good is that? That&apos;s when it struck me in a Roy Scheider sort of way; this was Reflection, the ability of a program to look at itself and change its behaviour.
</content>
</entry>

<entry>
<title>XForms for Prototyping</title>
<link rel="alternate" type="text/html" href="http://broadcast.oreilly.com/2008/12/xforms-for-prototyping.html" />
<id>tag:broadcast.oreilly.com,2008://53.34202</id>

<published>2008-12-01T08:27:29Z</published>
<updated>2008-12-01T08:27:29Z</updated>

<summary>A high-fidelity prototype provides the engineers and QA organization with a rich, interactive description of the product&apos;s intended functionality and
design to be used as a reference basis for implementation and test. Whenever this subject is raised my thoughts turn immediately to XForms. The advantage of prototyping with XForms is that it is quick, declarative, readable and is well defined.</summary>
<author>
<name>Philip Fennell</name>

</author>

<category term="prototyping" label="prototyping" scheme="http://www.sixapart.com/ns/types#tag" />
<category term="xforms" label="xforms" scheme="http://www.sixapart.com/ns/types#tag" />
<category term="xml" label="xml" scheme="http://www.sixapart.com/ns/types#tag" />
<category term="xrx" label="xrx" scheme="http://www.sixapart.com/ns/types#tag" />

<content type="html" xml:lang="en" xml:base="http://broadcast.oreilly.com/">
A high-fidelity prototype provides the engineers and QA organization with a rich, interactive description of the product&apos;s intended functionality and
design to be used as a reference basis for implementation and test. Whenever this subject is raised my thoughts turn immediately to XForms. The advantage of prototyping with XForms is that it is quick, declarative, readable and is well defined.
</content>
</entry>

<entry>
<title>The Future of XForms</title>
<link rel="alternate" type="text/html" href="http://broadcast.oreilly.com/2008/10/the-future-of-xforms.html" />
<id>tag:broadcast.oreilly.com,2008://53.33638</id>

<published>2008-10-02T19:52:00Z</published>
<updated>2008-10-02T19:52:00Z</updated>

<summary>Some of the recent talk on the Mozilla XForms Project&apos;s mailing list (dev-tech-xforms) has been about the winding-down in effort on the Mozilla XForms plug-in. There has been praise for the efforts of those developers involved in the project, and quite rightly so. However, some people may be seeing this as a bad sign for XForms in general. Well, not so I say and the reasons for this are three-fold...</summary>
<author>
<name>Philip Fennell</name>

</author>

<category term="browsers" label="browsers" scheme="http://www.sixapart.com/ns/types#tag" />
<category term="xforms" label="xforms" scheme="http://www.sixapart.com/ns/types#tag" />
<category term="xml" label="xml" scheme="http://www.sixapart.com/ns/types#tag" />
<category term="xrx" label="xrx" scheme="http://www.sixapart.com/ns/types#tag" />

<content type="html" xml:lang="en" xml:base="http://broadcast.oreilly.com/">
Some of the recent talk on the Mozilla XForms Project&apos;s mailing list (dev-tech-xforms) has been about the winding-down in effort on the Mozilla XForms plug-in. There has been praise for the efforts of those developers involved in the project, and quite rightly so. However, some people may be seeing this as a bad sign for XForms in general. Well, not so I say and the reasons for this are three-fold...
</content>
</entry>

</feed> 