RE: Transformative Programming: Flow-based, functional,and mor

I think that might be true of some of the approaches in the rebirth of flow-based programming, but I don't think it's axiomatically true. For example, you mention UNIX pipes, which involve breathtakingly unstructured data (usually the only structure is the line break).

In my observation of 21st century FBP, people do at last seem aware that they should be simplifying and reducing the coupling of the packets between nodes. There was a time that the XML community seemed aware of this as well, then in 2002 or so it all went haywire.

Peter, i think you and I are using "structured data" in a very different way. For me, an example of structured data is a relational tablespace, or a Java class. XML is semi-structured, and neither XSLT 1.x nor XProc require anything I'd call strong structure. XSLT 2.x and 3.x can work efficiently with strong structure if you have it, but do not require it.  Therefore I disagree with the notion that the utility of XSLT or XProc comes at the cost of structure. But that's an old debate, circling around these parts for over a decade, and I'm not just now up for a big rehash.

Author, Ndewo, Colorado                     http://uche.ogbuji.net/ndewo/
Founding editor, Kin Poetry Journal      http://wearekin.org
Editor & Contributor, TNB     http://www.thenervousbreakdown.com/author/uogbuji/
http://copia.ogbuji.net    http://www.linkedin.com/in/ucheogbuji    http://twitter.com/uogbuji