Tag: xml

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…

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…

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…

MarkLogic and XSLT

0 Comment

MarkLogic fans should check out Norm Walsh’s posting about his talk at the NY User Group. If you follow the right Twitter feeds, this is probably not too much of a surprise, but now the cat is officially disjoint with the volume inside the bag. Disclaimer: be sure to read the disclaimer there. -m

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”…

Pragmatic Namespaces

0 Comment

In case any of the 7 regular readers here aren’t following xml-dev, check out and add to the discussion about Pragmatic Namespaces, proposed as a solution for the “distributed extensiblity” problem in HTML5. For years people have been pointing to Java as the model for how XML namespaces should work, so this proposal goes that…

Java-style namespaces for markup

0 Comment

I’m noodling around with requirements and exploring existing work toward a solution for “decentralized extensability” on xml-dev, particularly for HTML. The notion of “Java-style” syntax, with reverse dns names and all, has come up many times in the context of these kinds of discussions, but AFAICT never been fully fleshed out. This is ongoing, slowly,…

See you at Balisage

0 Comment

Balisage, formerly Extreme Markup, is the kind of conference I’ve always wanted to attend. Historically my employers have been not quite enough involved in the deep kinds of topics at this conference (or too cash-strapped, but let’s not go there) to justify spending a week on the road. So I’m glad that’s no longer the…

XIN: Implicit namespaces

0 Comment

An interesting proposal from Liam Quin, relating to the need for huge rafts of namespace declarations on mixed namespace documents. In practice, though, almost all elements [in the given example] are going to be unambiguous if you take their ancestors into account, and attributes too. Amen. I’ve been saying things like this for five years…

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