OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.


Help: OASIS Mailing Lists Help | MarkMail Help

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index]
Re: [xml-dev] Transformative Programming: Flow-based, functional, and more

This nCode demo is good illustration


On Fri, Oct 18, 2013 at 1:52 PM, David Lee <dlee@calldei.com> wrote:

I'd be interested if anyone has used NetKernel ... I perused the front pages and its so full of jargon and marekting speak that I can't tell if its snake oil, insanity, or truly revolutionary.


The license model is interesting too .. a fairly creative (IMHO) mixture of open source and closed license.

But without trying it .. I have no clue reading the marketing literature what it *is* ..




David A. Lee




From: Stephen Cameron [mailto:steve.cameron.62@gmail.com]
Sent: Thursday, October 17, 2013 9:16 PM
To: Uche Ogbuji
Cc: Peter Hunsberger; Simon St.Laurent; xml-dev@lists.xml.org

Subject: Re: [xml-dev] Transformative Programming: Flow-based, functional, and more


I believe the Resource Oriented Computing basis of NetKernel can be added to this 'approach' as well. This is the ability to chain small units of data transforming functionality, using functions/procedures identified via an new 'active' URI scheme.

I cannot tell you much more than that but interested to hear comments.


All derived from original work on an 'XML publishing framework' by HP Labs.



On Fri, Oct 18, 2013 at 11:35 AM, Uche Ogbuji <uche@ogbuji.net> wrote:

On Thu, Oct 17, 2013 at 4:35 PM, Peter Hunsberger <peter.hunsberger@gmail.com> wrote:

Hi Simon,


I'll buy into your view on REST, maybe a better fit is something like Web Sockets?  However, I can't agree with you in regards to tighter specs inside applications and looser between them.  Are you suggesting that (for example) a Java method that has a single String as it's input and output needs a full XSD or some other more formal spec?  I suspect you're indulging in a bit of hyperbole in that, flexibility between applications in what they can accept might simplify the world, but you know as well as anyone that not everything can be mapped to name value pairs or tuples and left at that?


I'm pretty sure I'm baffled by the above paragraph so this might not at all be relevant, but I will say that REST, and the Web itself pretty has loose specification between applications as its fundamental principle. The Verb/Resource model of REST is pretty much exactly the tuple pairs you seem to think cannot work.




Uche Ogbuji                                       http://uche.ogbuji.net
Founding Partner, Zepheira                  http://zepheira.com

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


[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index]

News | XML in Industry | Calendar | XML Registry
Marketplace | Resources | MyXML.org | Sponsors | Privacy Statement

Copyright 1993-2007 XML.org. This site is hosted by OASIS