The W3C’s take on why XQuery is awesome Captured 20110321
Why this image is included: I was confident XQuery was about to have a major market impact several years ago; why is it taking so long?...
Search snapshot on 20110321, excluding Burton Group contentA Gartner search for “NoSQL” returned 11 resultsSimilar overall results with a Forrester search – 31 document hits for XQuery; 799 for SQLReturned 73 results on search when expanded to include all Gartner content – i.e., including Burton Group content; the vast majority of Gartner content referencing XQuery is in Burton Group documents I either personally wrote or influenced
Captured 20110321Point of this slide: checking mainstream tech instead of subscription-based analyst firms, there’s a similar result – a surprising shortage of XQuery news coverage
Captured 20110322A similar search comparing SQL and XQuery makes the latter, relatively, look like it’s flat-lining (is barely discernible)Google Trends is also a useful service, if you want to explore further
Search done on 20110321 for 200101 – 201004
On collab/content – e.g., IBM Notes/Domino, Connections, FileNet; Microsoft SharePoint
Not an exhaustive list
This is a high-level dichotomy – and not meant to be precise or mutually-exclusive (i.e., some info items have both resource and relation attributes)
This is meant to be illustrative – neither precise nor exhaustive
Point of this slide: reinforce ability to discern major similarities/differences between two tools/services focused on similar domain, by comparing/contrasting model diagrams Non-technical people can easily learn how to read/use this type of model – not so with most logical and physical model diagramming techniquesEvernote conceptual model fragment example from http://www.quepublishing.com/articles/article.aspx?p=1684320 Incomplete – a full conceptual model includes accompanying documentation, e.g., with entity definitions and examplesMicrosoft OneNote 2010 conceptual model fragment example from http://www.quepublishing.com/articles/article.aspx?p=1684320 Reason for including it: it provides an example, comparing it to the Evernote conceptual model fragment, of how easy it is to understand domains, when using conceptual models – e.g., the fact that OneNote has a more elaborate info item containment structure, and supports tags at the item/paragraph level, while Evernote tagging is at the note/page level. That’s not meant to be a judgment call; the extent to which Evernote or OneNote is more useful is a function of your info item/note-taking needs.
Point of having a merged cell for physical: it’s all coming together – it’s increasingly difficult to distinguish the underlying physical model services…Here again, hypertext is not 1:1 with HTML – it’s beyond-the-basics hypertext as manifested, e.g., in Web publishing and collaboration-oriented systems/servers
Content/document management view: I don’t need relational, and it’s too restrictive
Database management view of resources: a shrinking info anomalyConsidering these sometimes polarized views, it’s not surprising XQuery often doesn’t find a receptive audience
Altova and Embarcadero are two vendors to explore in this context
Lack of robustly useful and popularconceptual modeling tools is a very big problem
Aside: same is often true to for SQL developers, with similarly unfortunate consequences
Note: challenges will often be more political/cultural than technical