Category: standards

Skunklink a decade later

3 Comment

Alex Milowski asks on Twitter about my thoughts on Skunklink, now a decade old. Linking has long been thought one of the cornerstones of the web, and thereby a key part of XML and related syntaxes. It’s also been frustratingly difficult to get right. XLink in particular once showed great promise, but when it came…

XForms in 2013

5 Comment

This year’s Balisage conference was preceded by the international symposium on Native XML User Interfaces, which naturally enough centered around XForms. As someone who’s written multiple articles surveying XForms implementations, I have to say that it’s fantastic to finally see one break out of the pack. Nearly every demo I saw in Montreal used XSLTForms if…

Semantics!

0 Comment

This week marked the MarkLogic World conference and with it some exciting news. Without formally “announcing” a new release, the company showed off a great deal of semantic technology in-progress. Part of that came from me, on stage during the Wednesday technical keynote. I’ve been at MarkLogic five years next month, and the first piece…

MarkLogic 6 is here

0 Comment

MarkLogic 6 launched today, and it’s full of new and updated goodies. I spent some time designing the new Application Builder including the new Visualization Widgets. If you’ve used Application Builder in the past, you’ll be pleasantly surprised at the changes. It’s leaner and faster under the hood. I’d love to hear what people think…

Is XForms really MVC?

2 Comment

This epic posting on MVC helped me better understand the pattern, and all the variants that have flowed outward from the original design. One interesting observation is that the earlier designs used Views primarily as output-only, and Controllers primarily as input-only, and as a consequence the Controller was the one true path for getting data…

A Hyperlink Offering revisited

0 Comment

The xml-dev mailing list has been discussing XLink 1.1, which after a long quiet period popped up as a “Proposed Recommendation”, which means that a largely procedural vote is is all that stands between the document becoming a full W3C Recommendation. (The previous two revisions of the document date to 2008 and 2006, respectively) In…

Geek Thoughts: reading XProc code

0 Comment

All the input/output/port stuff in XProc seemed incomprehensible to me until I recognized something simple. Every time you see a <pipe> element, read it as “comes from”. For example <p:output port=”result”> <p:pipe step=”validated” port=”result”/> </p:output> reads as ‘output to the “result” port comes from the port “result” on step “validated”‘ and <p:input port=”source”> <p:pipe step=”included”…

© All Right Reserved
Proudly powered by WordPress | Theme: Shree Clean by Canyon Themes.