<?xml version="1.0" encoding="utf-8"?>
<feed xmlns="http://www.w3.org/2005/Atom">
<title>Dan McCreary 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-02-24T13:16:50Z</updated>

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

<entry>
<title>Towards a Plugin Architecture for XRX Web Applications</title>
<link rel="alternate" type="text/html" href="http://broadcast.oreilly.com/2009/02/towards-a-plugin-architecture.html" />
<id>tag:broadcast.oreilly.com,2009://53.35410</id>

<published>2009-02-24T13:16:50Z</published>
<updated>2009-02-24T13:16:50Z</updated>

<summary>The growth of XRX web application architectures is driving the need for a new generation of web applications standards beyond the scope of the current XQuery specification.  These standards promise to allow non-programmers to quickly assemble new web sites from libraries of pre-built XRX applications.</summary>
<author>
<name>Dan McCreary</name>
<uri>http://www.danmccreary.com</uri>
</author>

<category term="xml" label="xml" scheme="http://www.sixapart.com/ns/types#tag" />
<category term="xmldatabase" label="xml database" scheme="http://www.sixapart.com/ns/types#tag" />
<category term="xquery" label="xquery" 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 growth of XRX web application architectures is driving the need for a new generation of web applications standards beyond the scope of the current XQuery specification.  These standards promise to allow non-programmers to quickly assemble new web sites from libraries of pre-built XRX applications.
</content>
</entry>

<entry>
<title>How Entity Extraction is Fueling the Semantic Web Fire</title>
<link rel="alternate" type="text/html" href="http://broadcast.oreilly.com/2009/02/how-entity-extraction-is-fueli.html" />
<id>tag:broadcast.oreilly.com,2009://53.35396</id>

<published>2009-02-23T14:41:11Z</published>
<updated>2009-02-23T14:41:11Z</updated>

<summary>New OpenSource Entity Extraction programs are becoming easier than ever for non-programmers to use.  Apache UIMA is one example of a revolutionary technology that will make it easier then ever for non-programmers to tap the power of the Semantic Web.</summary>
<author>
<name>Dan McCreary</name>
<uri>http://www.danmccreary.com</uri>
</author>

<category term="rdf" label="RDF" scheme="http://www.sixapart.com/ns/types#tag" />
<category term="search" label="search" scheme="http://www.sixapart.com/ns/types#tag" />
<category term="semanticweb" label="semantic 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/">
New OpenSource Entity Extraction programs are becoming easier than ever for non-programmers to use.  Apache UIMA is one example of a revolutionary technology that will make it easier then ever for non-programmers to tap the power of the Semantic Web.
</content>
</entry>

<entry>
<title>Your Social Network *IS* Your Computer</title>
<link rel="alternate" type="text/html" href="http://broadcast.oreilly.com/2008/11/your-social-network-is-your-co.html" />
<id>tag:broadcast.oreilly.com,2008://53.34173</id>

<published>2008-11-18T13:40:43Z</published>
<updated>2008-11-18T13:40:43Z</updated>

<summary>Social networking software is making trust more transparent to the user of a service.  It is creating a new paradigm shift in computing: it allows people to just use resources without worrying about trust issues.  Building your social network and integrating social network trust data into your application will be more important than ever.</summary>
<author>
<name>Dan McCreary</name>
<uri>http://www.danmccreary.com</uri>
</author>

<category term="advocacy" label="advocacy" scheme="http://www.sixapart.com/ns/types#tag" />
<category term="security" label="security" scheme="http://www.sixapart.com/ns/types#tag" />
<category term="semanticweb" label="semantic web" scheme="http://www.sixapart.com/ns/types#tag" />
<category term="socialnetworking" label="social networking" scheme="http://www.sixapart.com/ns/types#tag" />

<content type="html" xml:lang="en" xml:base="http://broadcast.oreilly.com/">
Social networking software is making trust more transparent to the user of a service.  It is creating a new paradigm shift in computing: it allows people to just use resources without worrying about trust issues.  Building your social network and integrating social network trust data into your application will be more important than ever.
</content>
</entry>

<entry>
<title>Warning: x = x + 1 May Be Hazardous to Your Brain</title>
<link rel="alternate" type="text/html" href="http://broadcast.oreilly.com/2008/11/warning-x-x-1-may-be-hazardous.html" />
<id>tag:broadcast.oreilly.com,2008://53.34155</id>

<published>2008-11-16T23:56:23Z</published>
<updated>2008-11-16T23:56:23Z</updated>

<summary>Many people that are just starting in their software career have not been exposed to the contrast between two very different approaches to solving server side scalability issues.  And although efficiently using 100 CPUs is not critical today, in the next five years it will become critical for a projects success. In this article we look at how the cognitive styles of functional and imperative software will shape the computing industry.</summary>
<author>
<name>Dan McCreary</name>
<uri>http://www.danmccreary.com</uri>
</author>

<category term="concurrency" label="concurrency" scheme="http://www.sixapart.com/ns/types#tag" />
<category term="xml" label="xml" scheme="http://www.sixapart.com/ns/types#tag" />
<category term="xquery" label="xquery" scheme="http://www.sixapart.com/ns/types#tag" />
<category term="xrx" label="xrx" 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/">
Many people that are just starting in their software career have not been exposed to the contrast between two very different approaches to solving server side scalability issues.  And although efficiently using 100 CPUs is not critical today, in the next five years it will become critical for a projects success. In this article we look at how the cognitive styles of functional and imperative software will shape the computing industry.
</content>
</entry>

<entry>
<title>Five RESTful Friends</title>
<link rel="alternate" type="text/html" href="http://broadcast.oreilly.com/2008/11/five-restful-friends.html" />
<id>tag:broadcast.oreilly.com,2008://53.34099</id>

<published>2008-11-11T14:05:59Z</published>
<updated>2008-11-11T14:05:59Z</updated>

<summary>Sometimes in computing, as in life, we are surrounded by friends that are standing by to help us.  But unless we are aware our friends exist and we give them the information they need to help us, we will not be able to take advantage of their services.  Here is a brief overview of five friends you may not be aware of that are standing by to help you with your web application performance.</summary>
<author>
<name>Dan McCreary</name>
<uri>http://www.danmccreary.com</uri>
</author>

<category term="rest" label="rest" 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/">
Sometimes in computing, as in life, we are surrounded by friends that are standing by to help us.  But unless we are aware our friends exist and we give them the information they need to help us, we will not be able to take advantage of their services.  Here is a brief overview of five friends you may not be aware of that are standing by to help you with your web application performance.
</content>
</entry>

<entry>
<title>Creating Bullet Bars with Google Charts</title>
<link rel="alternate" type="text/html" href="http://broadcast.oreilly.com/2008/11/creating-bullet-bars-with-goog.html" />
<id>tag:broadcast.oreilly.com,2008://53.34078</id>

<published>2008-11-09T21:45:09Z</published>
<updated>2008-11-09T21:45:09Z</updated>

<summary>Using Google Charts REST interface it&apos;s easy to create bullet bar dashboard indicators without using excessive screen area.</summary>
<author>
<name>Dan McCreary</name>
<uri>http://www.danmccreary.com</uri>
</author>

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

<content type="html" xml:lang="en" xml:base="http://broadcast.oreilly.com/">
Using Google Charts REST interface it&apos;s easy to create bullet bar dashboard indicators without using excessive screen area.
</content>
</entry>

<entry>
<title>XRX and Context Delivery Architecture</title>
<link rel="alternate" type="text/html" href="http://broadcast.oreilly.com/2008/11/xrx-and-context-delivery-archi.html" />
<id>tag:broadcast.oreilly.com,2008://53.34054</id>

<published>2008-11-06T23:09:53Z</published>
<updated>2008-11-06T23:09:53Z</updated>

<summary>What if your web applications could all be quickly customized based on needs of a specific person, role or group?  What if you could start out with one general form but it could be easly customized for different roles, groups or class of users?  We call these forms CoDA (for Context Delivery Architecture) forms because they can take advantage of the context aware features of the XRX architecture.</summary>
<author>
<name>Dan McCreary</name>
<uri>http://www.danmccreary.com</uri>
</author>

<category term="designpatterns" label="design patterns" scheme="http://www.sixapart.com/ns/types#tag" />
<category term="rest" label="rest" scheme="http://www.sixapart.com/ns/types#tag" />
<category term="xforms" label="xforms" scheme="http://www.sixapart.com/ns/types#tag" />
<category term="xquery" label="xquery" 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/">
What if your web applications could all be quickly customized based on needs of a specific person, role or group?  What if you could start out with one general form but it could be easly customized for different roles, groups or class of users?  We call these forms CoDA (for Context Delivery Architecture) forms because they can take advantage of the context aware features of the XRX architecture.
</content>
</entry>

<entry>
<title>Content Routing in XRX</title>
<link rel="alternate" type="text/html" href="http://broadcast.oreilly.com/2008/11/content-routing-in-xrx.html" />
<id>tag:broadcast.oreilly.com,2008://53.33993</id>

<published>2008-11-02T20:00:12Z</published>
<updated>2008-11-02T20:00:12Z</updated>

<summary>Does your database management system implement the content routing pattern?  How would your applications be different if content routing were &quot;baked in&quot; to each database server?  Would a rules-based approach to object-persistence make your systems more flexible?</summary>
<author>
<name>Dan McCreary</name>
<uri>http://www.danmccreary.com</uri>
</author>

<category term="designpatterns" label="design patterns" 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/">
Does your database management system implement the content routing pattern?  How would your applications be different if content routing were &quot;baked in&quot; to each database server?  Would a rules-based approach to object-persistence make your systems more flexible?
</content>
</entry>

</feed> 