Results tagged “xml” from O'Reilly News
These days, it seems it's in vogue to rant about HTML 5. I'd rather explain the need for structured XHTML.
Two drafts of standards are available on the web: Unstructured Operation Markup Language, and Minimum requirements for specifying document rendering systems
"Convention over configuration" is a great way to write code - but a lot harder to explain when it comes time to write documentation.
Here's some links that struck my interest recently on various XML-ish things
One of the reasons I've always liked the Balisage Conference and its predecessors is location: it's in Montreal, in August. This year, though, the pros and cons of that location seemed much much clearer. On a regular basis, several times...
One of the projects I have been working on recently has been a proof-of-concept system to allow a rules-base approach to automatically classifying and annotating XML-in-ZIP documents. The approach we have taken is to use Schematron, using the
report elements rather than the assert elements.
There was one thing missing from XForms 1.0 that would have made all the difference when trying to access RESTful Web Services - the ability to control HTTP headers when making instance data requests and submissions. What compounded the problem was that many of the implementations either inappropriately (in my opinion) set the HTTP Accept header to
*/* or just adopted the string used by the host browser. This made it nigh-on impossible to request, in a RESTful fashion, an XML representation of the resource you wish to edit...
But the bottom line for foreign elements as wrappers in ODF and OOXML is that ODF allows them to be stripped out by the application while OOXML doesn't allow that; neither of course require that any particular application understands them. The bottom line for OpenOffice and Office seems to be that OpenOffice strips them (dangerously, but perhaps allowed because of bad drafting of that part of the ODF standard) while Office 2007 does allow them. In both cases users would be helped by clearer text (better conformance text for the OASIS/ISO text, better references for the Ecma/ISO text.)
On Friday last week, the ISO/IEC JTC1 Technical Management Board (comprised of various National Bodies) narrowly declined to forward the OOXML appeals of India, Venezuela, Brazil and South Africa to a Conciliation Panel. Despite some comments around the place, the appeals process is not necessarily over.
Basing his design on Steven Mesker's seminal work "Building Parsers with Java", Todd Ditchendorf has released the TODParseKit, a Mac OS X Parsing Framework written in Objective-C 2.0.
August markup conferences always leave my brain feeling a bit bubbly. Or maybe it's just melted. As expected, Balisage offered amazing food for thought that should last until next year's event.
I was re-reading NIST's XML Schema Design Quality Test Requirement Documentfrom 2004 recently: it has a great list of various best practices for XSD from different organizations from the lens of five years ago. So would be the set of meta-rules we can extract from these best practice documents?
I was surprised to read a review of Schematron and other schema languages which cited the lack of localization as an important reason to not use it, so the next release of the skeleton has localized messages. Here is the approach I took to localize the XSLT.
A common theme at this year's Balisage Conference has been integrating Semantic Web technologies with more traditional web interfaces. So far, it hasn't been the more common microformats approach, but rather approaches that let users add assertions to documents in...
In his Extreme "first person" talk yesterday, Patrick Durusau asked some of the right questions about the recent explosive battles over standardizing XML generated by Microsoft Office and OpenOffice.org. I can't share his conviction, though, that getting through this firefight...
A new edition of the standard currency codes is out. Currency adoption shows the geo-economic affiliation of countries. Plus polymer banknote links.
It seems that the answer is, yes, a URL can contain an XPath, providing it has been delimited in certain ways. Why would we want to do this? The trouble with using fragment identifiers or queries in URLs (
? and #) is that the resources identified become, in effect, terminal leaves. You cannot merely add more paths underneath, as far as I can see, to drill down further.
In a talk that he'd contemplated naming "XML as the precipitating factor in the upcoming religious wars," Eduardo Gutentag examined how XML participated in, or even started, a revolution that most of the world didn't notice. Gutentag quoted Jon Bosak...
A small but high-powered core of markup specialists converges on Montreal every August. A decade ago there were XML conferences everywhere - everyone wanted to know everything they could about XML. Today, I think it's fair to say that most...
News Topics
Subscribe to our Newsletters
O'Reilly on YouTube
O'Reilly on Twitter
O'Reilly on Facebook
News Feed
