Acrolinx In Technical Communication Plus

Webinar
22 May 2013 | 12pm ET (18pm CET)

eSeminar Hosted By Adobe and presented by Tom Aldous of Acrolinx

Link To Recorded Video

Date / Time – April 10, 2013 at NOON EST

I am looking forward to presenting this webinar sponsored by Adobe. So many people have asked me, “What is Acrolinx?”, “Can Content Optimization Be Automated”, “How Can I Get Reports On The Shape Of Our Content In Our Repository” and “Can I See a Demo Of The Technology?”.

On Wednesday April 10, 2013 I will be providing answers to all those questions in this fast paced webinar. Register now at http://www.adobe.com/cfusion/event/index.cfm?event=detail&id=2184057&loc=en_us

Find Out How to Write XSLT Statements for XML to XML Transformations in a 5-part eSeminars Series

June 28, 2012 – July 19, 2012 – Recorded

I recieve inquires about how to move a workflow from unstructured content (be it MSWord or FrameMaker) to an XML one often. The process requires several steps, but once mastered you will be able to “Unleash The Protential Within Your Documentation”.

This is where FrameMaker becomes automagical.

It is very important that you follow the series start to finish. I will bring a sample document through the full process and create all necessary system files. I will provide all files created on my blog.

Unstructured To XML Workflow Series Part 1:

Creating A FrameMaker Conversion Table 

https://www.adobe.com/cfusion/event/index.cfm?event=register%5Fno%5Fsession&id=1832114&loc=en%5Fus

Unstructured To XML Workflow Series Part 2:

Creating A FrameMaker Conversion Table

https://www.adobe.com/cfusion/event/index.cfm?event=register%5Fno%5Fsession&id=1839616&loc=en%5Fus

Unstructured To XML Workflow Series Part 3:

Creating A FrameMaker Conversion Table

https://www.adobe.com/cfusion/event/index.cfm?id=1844301&loc=en%5Fus&event=register%5Fno%5Fsession

Unstructured To XML Workflow Series Part 4:

Element Definition Document (EDD) – Home Grown or a Standard

https://www.adobe.com/cfusion/event/index.cfm?loc=en%5Fus&id=1855039&event=register%5Fno%5Fsession

Unstructured To XML Workflow Series Part 5:

Creating your Structured Template from an Unstructured One

https://www.adobe.com/cfusion/event/index.cfm?id=1855043&event=register%5Fno%5Fsession&loc=en%5Fus

Unstructured To XML Workflow Series Part 6:

Structure Applications and What Is Necessary and How To Create

https://www.adobe.com/cfusion/event/index.cfm?loc=en%5Fus&event=register%5Fno%5Fsession&id=1863995

Unstructured To XML Workflow Series Part 7:

Save As XML, Now What?

https://www.adobe.com/cfusion/event/index.cfm?event=register%5Fno%5Fsession&id=1877651&loc=en%5Fus

I will be taking you through all the steps and workflow requirements to move you from anUnstructured To an XML / FrameMaker 10 workflow. It is going to be an instructional series.

Spread the word!

I will be HOSTING this one!

When:

Monday, November 19, 2012 10:00 AM – 11:00 AM US/Pacific

I highly recommend attending these eSeminars.

http://www.adobe.com/cfusion/event/index.cfm?event=detail&id=2076620&loc=en_us
Date: 5 Sep, 10-11AM PST
Topic: Maintaining XSLT code as a structured FrameMaker document
Description:
This webinar describes a structured FrameMaker application for editing XSLT. While the document window appears to show actual XSLT code, the structure of the edited document is an easily-understood variation of that used in the final XML output. Features of this editing structure include:

1) Names of various constructs (variables, templates, modes, and so forth) can be entered once and referenced multiple times as cross-references. To change a name therefore, a user need only change the typed occurrence and update cross-references; there is no need to search for all the individual occurrence.

2) The user can navigate through multiple files with generated lists of elements such as named templates and calls to those templates. Index markers can be used to generate an index into the code.

3) Elements in the structured document spare the user the need to remember details of XSLT syntax such as the names of the different axes and the order of the arguments to various functions. Color is used to visually identify matching parentheses and help prevent some syntax errors.

Once a document is complete, the user saves it as XML using an application that uses XSLT itself to change from the editing structure into actual XSLT code. Furthermore, existing XSLT code can be brought into this environment by opening it using an application that converts XSLT to the editing structure.

In addition to demonstrating a productive environment for maintaining XSLT transforms (or stylesheets), this application illustrates:

1) A practical application of the XSLT features Tom Aldous described in his recent 5-part series of presentations on XSLT in FrameMaker

2) How useful FrameMaker 11 can be for producing XML

3) A situation in which there is more information in a FrameMaker structured document than the corresponding XML

http://www.adobe.com/cfusion/event/index.cfm?event=detail&id=2076630&loc=en_us
Date: Oct 2, 10-11AM PST
Title: Debugging XSLT with FrameMaker 11
Description:
In this presentation, Lynne Price of Text Structure Consulting illustrates how a developer can use new FrameMaker 11 features to test and maintain XSLT code. Lynne will use an XSLT advanced run to transform all files in a test suite and examine the results using XPath to find particular structures, make changes, and repeat the process until correct results are produced.

Free eSeminar

Friday, July 13, 2012 10:00 AM – 11:00 AM US/Pacific

I did an eSeminar with Nancy Harrison, Founder of Infobridge-Solutions, Inc yesterday. The topic was “Expand your Content Reuse Potential through Indirect Addressing: Using @keys-based addressing in DITA 1.2″. Here is the link to the recording.

Nancy came to the eSeminar armed with decades of extensive experience.

• Secretary and charter member of OASIS DITA Technical Committee
• Former member IBM DITA Architect’s Team
• Member of OASIS DocBook Technical Committee
• One of original DocBook DTD developers
• Frequent speaker at industry conferences
• Working with SGML/XML since 1992
• Technical consultant specializing in: Information architecture, XSL / XSL-FO style sheet design, Translation/globalization issues, Migration of unstructured data to structured formats

• DITA 1.2 makes implementing DITA without a Content Management System practical due to mapping reusable content with keys
• In Pre-DITA 1.2, if you were to move the source of a targeted reusable object, you would have to modify every piece of content that pointed to it. Now with keys you only have to modify the one ditamap the contents the link location.
• Conditional content changes are as easy as loading a new ditamap with the same keys defined to different locations. No more ditaval file or reltables …

• Upgrade your DITA 1.1 content to DITA 1.2 with a file / open / save
• How to create and manage keys
• How to use a key for both DITAMAPs and Topics
• Talked about “how to conref a range of sibling” and “topicsets” using DITA 1.2 / FrameMaker 10

June 28 to July 19, 2012  – Recorded Sessions

Part 1 › Thursday, June 28, 2012 – Link To Recording

One of the advantages of using XML as a source file format is that it’s application-independent. Some of the other advantages include easy reusability and language translation cost reductions. Very little has been written about XML to XML Transformations, although there are some books that outline how to do XML to HTML transformations. This series of eSeminars is intended to fill that gap.

Did you know that the one of the biggest advantages of XML is that you can transform your source content with very quick and easy-to-write XSLT statements? FrameMaker can apply an XSLT transform on ‘Open’ and ‘Save’. The possibilities are endless if you know the basics of “how to” write XSLT for XML to XML transforms. You can use attributes to automatically apply Conditional Tag processing instructions. You can build TOC’s at the top of each chapter without having to do it manually with cross references. And there are several other creative uses as well.

The problem used to be that you either had to have an XSLT developer on staff or outsource the requirement. With your imagination, creativity and the knowledge gathered through this webinar series – your possibilities are nearly endless, with staff who don’t have highly developed programming skills.

Join Tom Aldous, Director of Business Development and Evangelism for Adobe’s Tech Comm business, for an interactive and engaging webinar – the 1^st / 2^nd/ 3^rd / 4^th /5^th webinar in a 5-part series . Tom will start off with the basics as a foundation. And soon enough, Tom will be having you building your own XSL transforms to resolve complex and time-consuming issues, automate processes and multiply productivity.

I am working on pulling together a Free 5 part eSeminar series on “How To XSLT” for XML to XML transformations.

This is what I use to make FrameMaker / XML automagical. FrameMaker 10 allows you to apply an XSLT stylesheet on open and save. This is a very unique feature. Writing XSLT stylesheets is not hard for XML to XML processing. In fact, these XSLT stylesheets can be small in length, but very powerful.

Last year I did a 7 part eSeminar series on “Unstructured to XML”, this is the next step in the process. What do you think? What type of problems would you like to solve with XSLT? I am pulling together an outline now. My twitter handle is tmaldous. I also have a LinkedIn and Facebook profile. Let’s connect. Tell me what you would find useful.

Spread the news!

Tom