After the webinar, please feel free to post comments and questions here.
Yesterday we got over 30 comments on a variety of posts, and I was stoked! The comments seem intelligent at first blush, and don’t contain any links… so I didn’t think they were spam. That is, until I started trying match them up with the subject of the posts. For example, on the post about Automating Tasks in a CMIS Repo, which discusses python, there was a comment that discussed a particular python API… only, that API did not have anything to do with the post and did not follow logically with the post it was replying to.
There are others which related particular problems about XSLT… but don’t really ask a question or have anything to do with DITA. Like this one,
"hi Mukul,i have a problem. Can you plesae provide me a good suggestion.the expalnation for the problem is as follows: i have a xslt code which transforms a xml to xsd. i want to throw an error as the output when i execute the xslt if the schema generated by the xslt is not valid. So this should stop the schema generation also. so the output should only be an error message without the generation of the schemas"
That almost makes sense, except that there are no approved comments by “Makul”. Or this one,
If you’re pursuing the beenift of XML to get the separation between form and content, why do you want to reintroduce the requirement to do output by hand?
OK, fair question… only the original comment was about a Facebook like button. So bizarre.
At any rate, I just deleted a ton of comments from the queue–my sincere apologies if any of them were legit. I’m pretty sure the multi-page poem in Japanese, along with the English translation, was not legit. But still… why?
In later chapters, Eliot goes into how to install, run, and make basic customizations to the toolkit. Even though I’ve created lots of plugins, I’m certain I’ll come back to the sections where he explains extension points and best practices for creating ant targets. Part 2 builds on the foundation set in part 1, layering in complexities like specialization, compound maps, vocabularies, reuse, and more. (I’m still trying to wrap my brain around Chapter 8 on linking and addressing.)
In short, I wish I’d had this book when I started out implementing DITA four years ago. I’m certainly glad I have it now.
I will soon add a section on customizing rules and reports.
For a DITA document that contains a single language, the highest level element (i.e. map, concept, task, etc.) that contains content should set the @xml:lang attribute to the language that applies to the document.
The question: How do I set the @xml:lang attribute using lxml? Everyone seems confused on the forums. Continue reading
I’ve presented at this conference for the last several years, and my impression this year is that the level of discourse has noticeably risen. There were more topics that were more technical. Presenters discussed more best practices, more concrete experiences, and more practical advice than in years past, when many discussions were more or less theoretical. Instead of “this is what will/might/should happen,” I heard more of what did happen and is happening. It sounds cliche and, yes, self-serving to say it, but this is an exciting time to be “in” DITA.
For me, these were the highlights of the conference:
- Steve Anderson mentioned the QA plugin in his presentation “Automation and testing DITA OT Content and Customizations”! I was totally stoked.
- George Bina showed us his RelaxNG plugin, which reproduces the DITA DTDs in an easier to manipulate format. By combining RelaxNG with Schematron, you can deeply customize your authoring experience, both constraining elements and attributes and providing in-line guidelines to authors.
- Michael Boses also discussed the awesomeness of Schematron. Ok, fine, I’m convinced. We’ll rewrite the QA plugin in Schematron.
- Bryan Schnabel showed his XLIFF round trip plugin, which converts DITa to and from XLIFF. Just converted a document to XLIFF. It was glorious. I am going to be all over this one.
- Mat Verghese from Citrix discussed a detailed and solid vision for raising the value and esteem of Content Strategists
- Keith Schengili-Roberts, in his keynote, gave me some great ideas for additions to the QA plugin, like calculating Flesch-Kincaid reading scale values. More to come on that front.
- Mark Baker discussed the use cases for his SPFE architecture, which is a different solution to many of the problems DITA implementors face. I particularly liked the idea of automagically creating links based on string matches. It’d be cool if the QA plugin’s link report could suggest new links based on the content….hmmm…
- I learned you can directly style XML with CSS! Who knew? There must be some great applications for this.
- And of course, Eliot Kimberly released his new book on implementing DITA. I’ll be posting a review sooner rather than later.
All told, a great conference.
I ignore QR Codes in marketing, but I think they could be a great way to link to resources, such as videos, from printed technical documents. Readers can simply zap the codes with their phones to pull up the content.