tag:broadcast.oreilly.com,2008-08-07://53 2009-11-06T04:45:46Z Movable Type Pro 4.21-en tag:broadcast.oreilly.com,2009://53.38436 2009-11-06T03:35:58Z 2009-11-06T04:45:46Z

So I guess when we look at a system's architecture, the first thing we can do is ask 'Is this XML here being used strategically or tactically?' 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 'Is it implemented in a way that allows flexible rearrangement, when a different tactic becomes appropriate?'

Rick Jelliffe So I guess when we look at a system's architecture, the first thing we can do is ask 'Is this XML here being used strategically or tactically?' 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 'Is it implemented in a way that allows flexible rearrangement, when a different tactic becomes appropriate?' tag:broadcast.oreilly.com,2009://53.38337 2009-10-29T08:17:43Z 2009-10-29T19:54:54Z

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.

Rick Jelliffe 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. tag:broadcast.oreilly.com,2009://53.38186 2009-10-14T13:59:40Z 2009-10-15T13:58:38Z

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't GET a webpage, they get a whole website (this is for B2B not B2C.)

Rick Jelliffe 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't GET a webpage, they get a whole website (this is for B2B not B2C.) tag:broadcast.oreilly.com,2009://53.38057 2009-09-30T06:02:29Z 2009-09-30T15:38:31Z

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...

Rick Jelliffe 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... tag:broadcast.oreilly.com,2009://53.38056 2009-09-30T05:01:43Z 2009-09-30T05:35:33Z

I have always thought the context-senstive { a^n, b^n, c^n: n >=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!

Rick Jelliffe I have always thought the context-senstive { a^n, b^n, c^n: n >=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! tag:broadcast.oreilly.com,2009://53.38035 2009-09-28T05:27:44Z 2009-09-29T05:00:50Z

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.

Rick Jelliffe 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. tag:broadcast.oreilly.com,2009://53.38034 2009-09-28T00:53:50Z 2009-09-28T02:31:58Z

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'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't have the supposed lock-in to benefit or excuse them from providing value.

Rick Jelliffe 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'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't have the supposed lock-in to benefit or excuse them from providing value. tag:broadcast.oreilly.com,2009://53.37993 2009-09-22T15:07:11Z 2009-09-23T02:33:51Z

A solid refactoring, the kind that you don't do every year, also needs to involve a tooling up, but scoped to making the new desired architecture something that programmers won't subvert but find natural. In a way, the programming languages become the interfaces that provides the boundaries for the layers of the system.

Rick Jelliffe A solid refactoring, the kind that you don't do every year, also needs to involve a tooling up, but scoped to making the new desired architecture something that programmers won't subvert but find natural. In a way, the programming languages become the interfaces that provides the boundaries for the layers of the system. tag:broadcast.oreilly.com,2009://53.37983 2009-09-21T03:37:53Z 2009-09-21T12:11:58Z

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?

Rick Jelliffe 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? tag:broadcast.oreilly.com,2009://53.37962 2009-09-17T05:45:37Z 2009-09-17T07:35:44Z

For some markets the success/domination by Microsoft is much stronger than blanket figures indicate.

Rick Jelliffe For some markets the success/domination by Microsoft is much stronger than blanket figures indicate. tag:broadcast.oreilly.com,2009://53.37936 2009-09-15T11:15:25Z 2009-09-16T14:51:16Z

A lot of Schematron can be implemented directly in a mildly enhanced version of RELAX NG without (I think) explosions, before it all runs out of steam.

Rick Jelliffe A lot of Schematron can be implemented directly in a mildly enhanced version of RELAX NG without (I think) explosions, before it all runs out of steam. tag:broadcast.oreilly.com,2009://53.37928 2009-09-11T10:06:47Z 2009-09-11T14:51:10Z

CSS quirrel is an online comic that is good for a few laughs. You can tell it would be funny if you knew what on earth they all were talking about. Actually, most of the comics are really paired with blog items giving the back story. It is a really cute format. Read on for a few of my favorites.

Rick Jelliffe CSS quirrel is an online comic that is good for a few laughs. You can tell it would be funny if you knew what on earth they all were talking about. Actually, most of the comics are really paired with blog items giving the back story. It is a really cute format. Read on for a few of my favorites. tag:broadcast.oreilly.com,2009://53.37922 2009-09-10T13:10:26Z 2009-09-14T08:51:43Z

But seriously, what is the point of keeping this kind of rubbish?

Rick Jelliffe But seriously, what is the point of keeping this kind of rubbish? tag:broadcast.oreilly.com,2009://53.37920 2009-09-10T07:40:51Z 2009-09-10T15:19:04Z

The W3C Systeam's blog has a hilarious item W3C's Excessive DTD Traffic. Apparently, generic XML systems are trying to download the DTD using the DOCTYPE declaration system identifier (i.e. what it is for) on XHTML files, or downloading the schemas from the namespace URI (i.e. not what it is for) for documents with XHTML fragments. And it is a lot of bogus traffic. W3C does not want to cop having to serve dumb XHTML requests for DTDs and schemas. A different DOCTYPE and a lazy loading parser policy would help. But I think all the ISO/MathML special character public entity sets should be built into XML.

Rick Jelliffe The W3C Systeam's blog has a hilarious item W3C's Excessive DTD Traffic. Apparently, generic XML systems are trying to download the DTD using the DOCTYPE declaration system identifier (i.e. what it is for) on XHTML files, or downloading the schemas from the namespace URI (i.e. not what it is for) for documents with XHTML fragments. And it is a lot of bogus traffic. W3C does not want to cop having to serve dumb XHTML requests for DTDs and schemas. A different DOCTYPE and a lazy loading parser policy would help. But I think all the ISO/MathML special character public entity sets should be built into XML. tag:broadcast.oreilly.com,2009://53.37917 2009-09-10T04:47:56Z 2009-09-10T08:54:31Z

Collapsing bubbles. Converting a DTD with tag omission to a regular grammar. Needing the stack for less. Term rewriting. On the fly addition of rules. Are SGML-family documents trees? SGML as a centre of gravity no more?

Rick Jelliffe Collapsing bubbles. Converting a DTD with tag omission to a regular grammar. Needing the stack for less. Term rewriting. On the fly addition of rules. Are SGML-family documents trees? SGML as a centre of gravity no more?