In response to NoSQL before NoSQL was cool and the proof
I have been working at Marklogic now for a little short of 2 months and I must say it has been an awesome experience to work in a place where everyone shares your passion for XML development and XQuery. I can say that I find it hard to write in any other language and have to remind myself to not to start writing let statements $var as xs:string := “xxxx” or beginning a loop as a flwor statement. With my total love for ML and XQuery, I still find myself defending my its honor to my Java/.NET colleagues. While I may win on many levels with regards to object orientation and how imperative languages are beginning to look alot like functional languages. And how more natural (yet verbose) XML is to Object Orientation than say the Relational model. I don’t lose to many arguments on those points. I think I am one to fight tooth and nail to support XQuery. I can say that Marklogic, makes building Search and REST services a trivial effort and pretty much anything that is exposed as XML can be easily worked with. . Yet I have been thinking for sometime that I would love to see it evolve from XML Search Platform and XML Query Language into the Rapid Application development Platform for____fill in the blanks_______. This evolution needs to start with writing the next killer application that can reach the masses of developers who struggle to develop XML applications, but rely on Java/.NET because of the lack frameworks beyond Parsing, Transforming and Searching XML.
- We need a Rails type frameworks for web development.
- We need a Service Bus framework for Enterprise integration
- We need an AOP framework that allows loose coupling between our application and business logic.
- We need the ability to inspect and parse XQuery to support dynamic programming.
- We need better integration with our imperative brothers and sisters.
- We need XQuery to Change!!!!
I have been thinking about this issue for a while in regards to working on a Marklogic as an Xml Platform. My wish is for an XQuery Reflection functionality that would allow me to inspect module metadata for various programming tasks such as dynamic programming, documentation stubs and plugin modules. So given a module at a specific uri, you could ask for an xml representation of the module in a serialized xml version.
define function map($node as element(ns2:object)) as element(ns1:object)*
<namespace-declaration prefix=”ns1″ uri=”http://www.myns.com”/>
<namespace-declaration prefix=”ns2″ uri=”http://www.ns2.com”/>
<module-declaration prefix=”util” uri=”urn:my-utilities” location=”../utilities.xqy”/>
<return type=”element” prefix=”ns1″ localname=”object” cardinality=”*”/>
<parameter name=”node” type=”element” prefix=”ns2″ localname=”object” cardinality=””/>
Question: How would anybody else see this being useful?