Meeting minutes 2014 11 04

Attendance: Robert, Graham, Kris, George, Radu, Shane, Jarno, Eliot, Roger

Item 1: 1.8 release status

Eliot added new issue this morning, asking to update OT1.8 to new Ant version (1.9.4). Robert and Jarno both against - don't want to update major external component in a bug fix. DITA-OT 2.0 already bundles the newer version.

DITA-OT 2.0 status and updates

Smaller changes at this point - getting close to release time. Cleanup, make code easier to use.

Started adding @as to XSLT code to set datatypes. May have some bugs related to that. Could just not use datatypes, but they're part of XSLT 2.0 so seems good to have them.

Docs! needing some help. Roger is helping out primarily with release notes. Robert intends to help. Also an offer from Shane (new to this call).

DITA-OT day in Munich

Webinar / recording set up.

Lots of interest - pretty much full for registrations.

Robert will try to get presentation done this week to send around for review, encourage others to do the same.

Roger wondering about internet access - should be available as part of the conference.

Other topics

Eliot: wondering about new DITA 1.3 features - when/how to implement. Jarno has already implemented much of the simple stuff. Changed preprocessing to make room for many new features. Will have question - how much backwards compatibility to retain with output? For example, today, reference document X 5 times, have one output file. Easier to implement 1.3 by forcing this to create 5 output files. But 2.0 default will still be to get one output file. So - will have to make decisions like that, but don't want to make those decisions yet.

Also question: do we want our first "supports 1.3" release to support everything, or do we want to ignore some features? Eliot: think unrealistic to support full support for keyscope/branch filter quickly. Also, cross-deliverable linking will be significant update that requires deep updates to current output transforms.

Eliot: if we don't know OT plans, it's hard to get people to commit to help out. But I may have client requirements that need 1.3 features so I have to get them. Don't want to be working on redundant features. For example, already needed to do 1.3 L&T items.

Maybe: list 1.3 features as starting point, list any plans to address. Kris points out - could use 1.3 spec topic about "new features" as a starting point.