Category: xml

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…

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…

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

Misunderstanding Markup

3 Comment

On this comic‘s panel 9 describes XHTML 1.1 conformance as: the added unrealistic demand that documents must be served with an XML mime-type I can understand this viewpoint. XHTML 1.1 is a massively misunderstood spec, particularly around the modularization angle. But because of IE, it’s pretty rare to see the XHTML media-type in use on…

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…

XML 2008 liveblog: Introduction to Schematron

0 Comment

Wendell Piez, Mulberry Technologies Assertion-based schema language. A way to test XML documents. Rule-based validation language. Cool report generator. Good for capturing edge cases. Same architecture as XSLT. (Schematron specifies, does not perform) <schema xmlns=”http://purl.cclc.org/dsdl/schematron”> <title>Check sections 12/07</title> <pattern id=”section-check”> <rule context=”section”> <assert test=”title”>This section has no title</assert> <report test=”p”>This section has paragraphs</report> … Demo….

XML 2008 liveblog: Automating Content Analysis with Trang and Simple XSLT Scripts

0 Comment

Bob DuCharme, Innodata Isogen Content analysis: why? You’ve “inherited” content. Need to save time or effort. Handy tool 1: “sort”. As in the Unix command line tool. (Even Windows) Handy tool 2: “uniq -c”  (flag -c means include counts) Elsevier contest: interface for reading journals. Download a bunch of articles, and see what’s all in…

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