Louis, I ended my OASIS membership at renewal time in August 2013.
I have not submitted any of my current work to the ODF TC or the W3C change-tracking community group. I occasionally glance at their lists and the JIRA, just to gauge what is going on. That is all. I will probably use the comment lists when my investigations uncover anything that might need repair in an errata. In May, I was inspired to look into change-tracking anew when I saw the interest of the OSB Alliance at <http://www.osb-alliance.de/en/working-groups/projekte/major-features-in-loaoo/>. Although I had not been thinking about it much, I realized that it is indeed possible to accomplish what they want by relatively simple repairs to the current ODF 1.2 approach. I had no interest in responding to the request for tender, however. I did start investigating ODF 1.2 tracked-changes, conducting tedious case analysis, and developing of a profile that could be used as an extension of what is already in ODF 1.2 and current implementations. It may well be much easier to describe than to implement, and that remains to be resolved. If there is to be implementation, it should be developed in Apache OpenOffice and thereby available to all other implementations in the openoffice.org lineage. I am unfolding this on a set of web pages. Currently, there is a bare skeleton, starting at <http://nfoworks.org/notes/2014/05/n140501.htm> and the other content that is linked to there. All of that work will be conducted in public and be available under Creative Commons Attribution license. I don't expect there to be any code, although I foresee a suite of test documents that do not disturb current software while including the foreign attributes that support the repairing extensions. Coincidentally, I have been encouraged to submit to a forthcoming workshop. If my submission is accepted, there will be presentation of progress and a short paper in 3rd Quarter, 2014. The work is just starting. Here is an abstract: Editing of word-processing documents at the presentation level, with visible tracking of changes, operates at a different level of abstraction and granularity than representation of the document in common document-file formats. The consequent mismatches are demonstrated using OpenDocument format provisions for tracked changes. A selection-copy analogy is introduced for bridging the abstraction levels while adhering to file-format provisions. The enhancements improve reliability and interoperability and are implementable incrementally without obsoleting current software and documents. Here's something I needed so that I could link my analysis to it. It was fun to figure out how to accomplish in a reliable way: <http://nfoworks.org/notes/2014/05/n140504f1.htm>. -- Dennis E. Hamilton [email protected] +1-206-779-9430 https://keybase.io/orcmid PGP F96E 89FF D456 628A -----Original Message----- From: Louis Suárez-Potts [mailto:[email protected]] Sent: Sunday, June 22, 2014 01:06 To: [email protected]; Dennis E. Hamilton Cc: Andrea Pescetti; Kay Schenk; Melissa Warnkin Subject: Re: Apache@ OSCON question HI Dennis, *, On 21 Jun 2014, at 21:01, Dennis E. Hamilton <[email protected]> wrote: > I am willing to make a day trip from Seattle to the OSCON Expo Hall. > That is affordable for me and appealing if can meet ASF and > especially AOO folks that I have not yet met in person. > > (I have started some work on change- > tracking for which there might be discussion interest as well.) Are you demonstrating this work on the Oasis lists? I don't follow the office@ list any longer. And by change tracking, what do you mean, exactly? If that's too broad a question, feel free to ignore it or answer off list, if it seems beside the point of this list to you. [ ... ] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
