Planet Free-Office

A collection of blogs from all Free-OpenSource Office vendors

July 24, 2008

Bob Sutor

Open source and piracy

Over at ZDNet, Dana Blankenhorn has a blog entry about whether software piracy benefits or hurts open source adoption. Evidently this originated from comments by Louis Suraez-Potts at OSCON noting that the availability of “free” (that is, pirated) proprietary software makes open source less necessary from a cost perspective. I’m not at OSCON this week (long story) and so I don’t know who said what and in what context, so I’ll let you read Dana’s piece and linked articles. I will instead add a few remarks of my own on the topic.

Let’s consider a couple of extreme if unlikely situations.

Suppose that it is 100% guaranteed that you could not pirate proprietary software. In that case the price of the software would very much factor into the Total Cost of Ownership (TCO) calculation. Given the existence of “good enough” open source competitors, the proprietary software would need to offer significant advantages in terms of price, quality, features, security, ease of use, upgrade policies, support, and service. In turn, however, open source software would evolve to keep pace with the proprietary software. Whether you think open source or proprietary software wins in this case, the consumer of the software comes out ahead.

On the opposite end, assume that piracy is rampant and use of stolen software carries no consequences. Then all software is “free” and price is no longer part of the equation of how users decide what to use. The other factors such as quality, ease of use, and security become much more relevant. Once again, competition improves both kinds of software and consumers win again. Unless they have other sources of income, providers of proprietary software will probably not stay in business very long in this scenario.

Life in the software world doesn’t exist at either of these extremes and there is a lot one could argue about the freedoms afforded by free and open source software. In practice today, I think the balance and competition between proprietary and open source software is improving software in general and driving innovation. We even need vigorous competition within the open source world if we choose to ignore proprietary software.

We want better software. We want software that gets the job done with the flexibility and assurances for the future that our situations require. Competition among software providers is good for consumers, especially when there are open standards that allow interoperability and interchangeability.

As I think Dana concludes, I think it’s probably a wash as to whether piracy helps or hurts open source adoption. I think there are more important questions to be asked on this topic.

  • How much is anti-piracy enforced in areas that are seeing adoption growth of open source software?
  • Have some vendors and their surrogates adopted an attitude of “we don’t like that they steal our software, but we would rather they used our software than someone else’s, including open source”?
  • Are we seeing measurable movement to or from open source software when piracy increases or decreases?

In answering these questions it is important to look at particular countries and regions and not make blanket world-wide statements about the relationship between piracy and open source. The occurrence of piracy and the ways it is fought is not uniform everywhere.


© Robert S. Sutor for Bob Sutor's Open Blog, 2008.
This work is licensed under a Creative Commons Attribution-Noncommercial-No Derivative Works 3.0 Unported License.
Posted under: Open Source, Standards.
Permalink | 2 comments

by Bob Sutor at July 24, 2008 11:08 PM

Daily Links 07/24/2008 (p.m.)

  • August 1-3, 2008. “The Newport Folk Festival is a multi-day, multi-stage music festival held at the historic International Tennis Hall of Fame and Fort Adams State Park in Newport, Rhode Island.”

    tags: OB, music, folk, Newport

  • “The b5media tech team was having a discussion today about what criteria we use when reviewing a WordPress plugin for possible inclusion on one of our sites or across our network. It makes for a good list of what not to do (or not do) when writing a WordPress plugin, something that might be generally useful to plugin authors. These things won’t make your plugin good — they’ll just help make it secure and stable.”

    tags: OB, open source, WordPress


© Robert S. Sutor for Bob Sutor's Open Blog, 2008.
This work is licensed under a Creative Commons Attribution-Noncommercial-No Derivative Works 3.0 Unported License.
Posted under: News.
Permalink | No comments

by Bob Sutor at July 24, 2008 08:30 PM

Diary of a CrazyFrench

Guadec slides

Just a quick note to let people know that I have put my slides online. They are linked from lgo (in OpenDocument).

I'll provide PDF and HTML versions soon.

by hub at July 24, 2008 03:57 PM

Bob Sutor

Daily Links 07/24/2008 (a.m.)


© Robert S. Sutor for Bob Sutor's Open Blog, 2008.
This work is licensed under a Creative Commons Attribution-Noncommercial-No Derivative Works 3.0 Unported License.
Posted under: News.
Permalink | No comments

by Bob Sutor at July 24, 2008 08:30 AM

July 23, 2008

Bob Sutor

Daily Links 07/23/2008 (p.m.)


© Robert S. Sutor for Bob Sutor's Open Blog, 2008.
This work is licensed under a Creative Commons Attribution-Noncommercial-No Derivative Works 3.0 Unported License.
Posted under: News.
Permalink | No comments

by Bob Sutor at July 23, 2008 08:30 PM

Daily Links 07/23/2008 (a.m.)

  • “Neal Stephenson’s new novel, ANATHEM, germinated in 01999 when Danny Hillis asked him and several other contributors to sketch out their ideas of what the Millennium Clock might look like. Stephenson tossed off a quick sketch and promptly forgot about it. Five years later however, when he was between projects, the idea came back to him, and he began to explore the possibility of building a novel around it. ANATHEM is the result, and will be released on September 9th, 02008.”

    tags: OB, books, scifi


© Robert S. Sutor for Bob Sutor's Open Blog, 2008.
This work is licensed under a Creative Commons Attribution-Noncommercial-No Derivative Works 3.0 Unported License.
Posted under: News.
Permalink | No comments

by Bob Sutor at July 23, 2008 08:30 AM

Andy Updegrove

Please Welcome the Alliance for Sustainable Air Transportation

At any one time I'm usually helping set up anywhere from two to five new standards consortia and open source foundations, and the gestational stealth period can be anywhere from two to eight months.  That's because the time will vary depending on how much time it takes to work everything out among the founders and recruit the type of starter set of members that you'd like to have to give an impression of inevitability to whatever it is that the founders are trying to make happen in the wider world.  As a result, it's always a pleasure to help introduce a new organization that has just emerged onto the public stage, and particularly so when the new consortium's mission is socially relevant.

That's the case with the Alliance for Sustainable Air Transportation, whose mission will ultimately effect just about everyone that reads this blog...

July 23, 2008 08:00 AM

Rob Weir

Sed quis custodiet ipsos custodes?



We are coming down to the last week for JTC1 to decide on whether to hear the four NB appeals concerning various claimed errors in the processing of DIS 29500 (OOXML), or whether summarily to dismiss these appeals without hearing them. The decision lies with two committees, the Technical Management Board (TMB) in ISO and the Standards Management Board (SMB) in the IEC.

Back on July 4th, the Secretaries General of ISO and the IEC referred the four NB appeals, with their comments, to the TMB/SMB. Groklaw has the text of these comments, in PDF format, as well as HTML transcription.

The comments of the Secretary General are accompanied by a ballot, asking the question:

ACTION

The members of the Technical Management Board are invited to indicate, by replying yes, no or
abstention on EITHER a) OR b) for each of the four appeals (see item 14 in annex A):

a) not to process the appeal any further:
Item 1 ABNT
Item 2 BIS
Item 3 FONDONORMA
Item 4 SABS

OR

b) to process one or more of the appeals, which would require setting up of a conciliation panel

Item 5 ABNT
Item 6 BIS
Item 7 FONDONORMA
Item 8 SABS

by no later than 4 August 2008.

This is quite a strange animal to see. Why are we having a ballot at all, and only a 30-day one? This is questionable from several perspectives.

First, why are the Secretaries General the ones calling for a ballot? The Directives do not call for them to do so. In fact the Secretaries General are not even called upon to make a recommendation. They are only asked for comments. The Directives say:


11.3.3 The Secretaries-General shall, following whatever consultations they deem appropriate, refer the appeal together with their comments to the TMB/SMB within one month after receipt of the appeal.

11.3.4 The TMB/SMB shall decide whether an appeal shall be further processed or not. If the decision is in favour of proceeding, the Chairmen of the TMB/SMB shall form a conciliation panel (see 9.2).

But deciding is not the same as voting. One of the cardinal principles of JTC1 is to discuss and seek consensus, not rush to a vote. Indeed, this is one of the matters under appeal, the rush to voting at the OOXML BRM. JTC1 Directives, section 1.2 says (my emphasis):

These Directives are inspired by the principle that the objective in the development of International Standards should be the achievement of consensus between those concerned rather than a decision based on counting votes.

But here we are, with a vote pushed on the TMB/SMB.

The sense of the vote is wrong as well. The Directives call for a decision on "whether an appeal shall be further processed or not." Note the wording. It did not call for a decision on "whether to accept the recommendation of the Secretaries General". But somehow, we skip discussion, skip over consensus and get a ballot question which asks the opposite question first "not to process the appeal any further". In an environment where many parties automatically vote Yes to the ballot question, changing the sense of the question in this way is prejudicial to the appellants.

So it is clear from the start that the powers that be do not want to give these four NB's the opportunity to make their case or be heard. In any case, let's take a deeper look at some of the subjects under appeal and see if we can detect what it is exactly that cannot bear the scrutiny of a duly processed appeal.

First up is the alleged mishandling of the contradiction period last year. The Secretaries General dismiss this complaint, saying that it was a matter of judgment:

The Directives give the JTC 1 Secretariat and ITTF latitude to use judgement as to whether a meeting should be organized to address alleged contradictions. Considering that other issues could potentially be identified during the DIS ballot, the JTC 1 secretariat and ITTF concluded that it was preferable to initiate the ballot and to allow all issues to be addressed by the BRM. The NBs were fully informed of all the claimed contradictions and Ecma's responses to them.

This argument doesn't hold water. Although the JTC1 Secretariat and ITTF are allowed judgment, this is not an absolute license which cannot be questioned. The Secretariat and ITTF also have defined duties, and their actions or inactions with respect to these duties can be questioned and are subject to appeal. Specifically, an NB may appeal the issue of an inaction of JTC1, according to JTC1 Directives, 11.3. So for the Secretaries General to suggest that this inaction cannot be appealed because it is a matter of judgment is nonsense. Judgment and duty are the proper matters for an appeal.

So what is the duty in this case? As stated in JTC1 Directives, 13.4:

If a contradiction is alleged, the JTC 1 Secretariat and ITTF shall make a best effort to resolve the matter in no more than a three month period, consulting with the proposer of the fast-track document, the NB(s) raising the claim of contradiction and others, as they deem necessary. A meeting of these parties, open to all NBs, may be convened by the JTC 1 Secretariat, if required.

If the resolution requires a change to the document submitted for fast-track processing, the initial document submitted will be considered withdrawn. The proposer may submit a revised document, to be processed as a new proposal.

If the resolution results in no change to the document or if a resolution cannot be reached, the five month fast-track ballot commences immediately after such a determination is made.


The Directives call for the JTC1 Secretariat to make a best effort to resolve the matter (JTC1 Directives, 13.4). The JTC1 Secretariat is not given latitude to do nothing, or allowed discretion to immediately defer this question to the ballot period, without making a best effort to resolve the matter.

When a new 6,000 page DIS is submitted to JTC1 only one month after the publication of another standard (ODF) in the exact same space (XML document formats for office applications) and 19 NB's submit contradiction statements, and the JTC1 Secretariat's "best effort" is to hold no consolations with the NB's claiming contradictions, to hold no meeting, to make no attempt to resolve the question, then I believe that any NB would has a legitimate grounds for appeal on the inaction of JTC1 with regards to contradictions. There is no evidence that a "best effort" was made here to resolve the contradictions. Doing nothing is clearly incompatible with the required “best effort”.

It should be noted that JTC1 has had challenges in the past getting ITTF to carry out their responsibilities with respect to contradictions, which lead to this resolution adopted unamimously at the 2000 JTC1 Plenary:

Resolution 27 - Consistency of JTC 1 Products

JTC 1 stresses the strong need for consistency of its products (ISs and TRs) irrespective of the route through which they were developed. Any inconsistency will confuse users of JTC 1 standards and, hence, jeopardize JTC 1's reputation. Therefore, referring to clauses 13.2 (Fast Track) and 18.4.3.2 (PAS) of its Directives, JTC 1 reminds ITTF of its obligation to ascertain that a proposed DIS contains no evident contradiction with other ISO/IEC standards. JTC 1 offers any help to ITTF in such undertaking. However, should an inconsistency be detected at any point in the ratification process, JTC 1 together with ITTF will take immediate action to cure the problem.

Perhaps it is time to give ITTF another reminder of their obligations in this regard?

Further, the determination claimed to have been made by the JTC1 Secretariat and ITTF was not communicated to JTC1 NB's. Instead, the JTC1 Secretariat merely forwarded Ecma's responses to the contradiction submissions along with a notification that the DIS ballot should then commence. No statement was made as to whether the ballot was commencing because the contradictions had in fact been resolved, or because a resolution could not be made, which are the only two outcomes allowed by the Directives in 13.4. Not to notify NB's of the actual state of the resolution of the contradictions submissions is incompatible with the JTC1 Secretariat's duty to make a best effort to resolve the matter.

This failure by JTC1 materially effected the ensuing ballot, since Microsoft was then able to take advantage of this procedural nonperformance and repeatedly represent to NB's that the contradictions had been rejected as invalid and could not be considered in the DIS ballot. In fact, this led to several NB's issuing explicit, but erroneous instructions to their members that the contradictions had been resolved and thus could not be raised again as a criterion for determining their national position, e.g., in Australia.

Further, although the Secretaries General claim that “the JTC 1 secretariat and ITTF concluded that it was preferable to initiate the ballot and to allow all issues to be addressed by the BRM” the documented fact is that the BRM Convenor explicitly disallowed any discussion of contradictions at the BRM.

Another subject of appeal was the irregular voting procedures used at the DIS 29500 BRM in February. This is the P-member versus O-member question. The Secretaries General dismiss this appeal in this way:

2e. Correct but inapplicable. The BRM was neither a meeting of JTC 1 nor of SC 34 but was open to all 87 national bodies which submitted a vote (including abstentions) on the DIS. Applying 9.1.4 would have disenfranchised the voting NBs present at the BRM which were not P-members. The fact that any votes in the BRM would be open to all national delegations present was communicated over three months prior to the BRM.

This argument presented is flawed, and amounts to saying, “The voting was done by P- and O-members because the meeting was attended by delegations from P- and O-members”. Who attended the meeting is immaterial. Liaisons such as Ecma also attended the BRM? Should they have been able to vote merely because they attended? No, of course not. Voting rights are defined in JTC1 Directives, and this must not be set aside in favor of an ad-hoc rule made without NB consultation or approval.

Asserting that applying 9.1.4 would disenfranchise NB's is an example of circular reasoning. One can only be disenfranchised if one first has the right to vote. So the statement by the Secretaries General is arguing a conclusion (O-members are permitted to vote at BRM's) by assuming the very thing it tries to prove.

JTC1 Directives 14.4.3.9, which defines the parallel BRM process for the Publicly Available Specification (PAS) transposition process, reads: “At the ballot resolution group meeting, decisions should be reached preferably by consensus. If a vote is unavoidable, the approval criteria in the subclause 9.1.4 is applied.” So here we see 9.1.4 explicitly called for. By the argument put forth by the Secretaries General, all PAS BRM's which follow the Directives are also flawed because they “disenfranchise” those NB's who are not P-members of JTC1. I believe this is a tortured reading of the Directives. The voting rules of 9.1.4 are explicitly and unambiguously called for in PAS BRM's, so one cannot dismiss their application to Fast Track on general principles that would apply equally to PAS. When Fast Track rules say that the BRM vote shall ("if a vote is unavoidable") "be taken according to normal JTC 1 procedures" then we are faced with two alternatives:
  • Use the voting rules of 9.1.4, which declares itself to be the normal voting procedures ("In a meeting, except as otherwise specified in these directives, questions are decided by a majority of the votes cast at the meeting by P-members expressing either approval or disapproval.")
  • Or use a voting rule which is not to be found anywhere within the Directives.
Which one is "normal JTC 1 procedures"? Where is the basis in the Directives for believing that O-members had the right to vote at the BRM?

Finally, neither BRM Convenor, Alex Brown, nor ITTF, nor indeed the assembled delegations at the BRM were competent nor had the mandate to make or change voting rules for a DIS BRM. The rules are set in JTC1 Directives, and must be followed. “These Directives shall be complied with in all respects and no deviations can be made without the consent of the Secretaries-General.” (JTC1 Directives 1.2).

Notifications made by the BRM Convenor in advance of the BRM have no weight on matters which exceed his mandate and authority. The communication referred to by the Secretaries General, which was given in advance by the BRM Convenor, was from this FAQ:

6.8 If votes are taken during the BRM, who votes?

Those present.

This in fact was not the rule applied at the BRM. For example, Liaison representatives could not vote, though they were undoubtedly present at the BRM and participated fully in other ways. Also individual participants could not vote, only delegations, via their HoD could vote. So the Convenor's glib communication should not be taken as notification of a novel voting procedure.

Additionally, the BRM Convenor was unambiguous in his communications on his blog where he clearly stated that the voting rules of 9.1.4 would be applied:

...Now, paper balloting follows normal JTC 1 in-meeting rules: In a meeting, except as otherwise specified in these directives, questions are decided by a majority of the votes cast at the meeting by P-members expressing either approval or disapproval. (9.1.4)

(After the BRM the Convenor dutifully went back and “corrected” his earlier blog post to reflect how the BRM actually operated.)

The Secretaries General further dismiss the concerns regarding BRM voting procedure, saying:

4e. Not correct. Decisions on the comments not discussed during the BRM and proposed dispositions were taken by a process agreed by the BRM itself (29 votes in favour, none against and 2 abstentions).

On the contrary, the BRM was not competent and had not the mandate to set its own voting rules or to negate the provisions for consensus stated in JTC1 Directives 1.2:

These Directives are inspired by the principle that the objective in the development of International Standards should be the achievement of consensus between those concerned rather than a decision based on counting votes.

[Note: Consensus is defined as general agreement, characterised by the absence of sustained opposition to substantial issues by any important part of the concerned interests and by a process that involves seeking to take into account the views of all parties concerned and to reconcile any conflicting arguments. Consensus need not imply unanimity. (ISO/IEC Guide 2:1996)]

The Directives specify the rules. If NB's do not like the rules, then NB's may work with SWG-Directives to define new rules and then vote on them using the defined process. But if the rules are not applied correctly, then the proper course is for NB's to appeal against the actions or inactions of those with a duty to carry out the rules. This is the essential governance model of JTC1. NB's rule, but they rule through the rules. We may not merely decide by majority vote to ignore rules for this DIS, or to institute new rules for that DIS, or to substitute different rules for another DIS, in an ad-hoc fashion, based on a BRM vote.

Using the logic given by the Secretaries General, what in principle would prevent a BRM from voting itself an Augur in addition to a Convenor for the purpose of observing the flights of birds to decide whether a given change to the DIS text was auspicious or not? Is there any voting procedure that would not be permitted them once we say that a BRM, by majority vote, can institute their own voting rules? Are TMB/SMB certain that this is the principle that they want affirmed by their rejection of the NB's appeals?

Further, NB's were not duly notified that their BRM delegations would be determining their own voting rules, so few if any of them had NB instructions on that matter. An agreement among BRM HoD's to set aside cardinal principles of JTC1, in the absence of NB consultations, should not be allowed to stand.

Finally, the existence of a vote at the BRM is not incompatible with the assertion that the BRM was “too short, arbitrarily short, or otherwise incorrectly conducted”. When given the choice between several bad alternatives, the delegations made a choice. That does not legitimatize the flawed application of JTC1 process that incorrectly gave them only bad choices and forced upon them a vote which they did not have the mandate to hold.

I could go on and on, but I'll spare you all more of the same. I am sorry to report that I find the response by the Secretaries General to be perfunctory, poorly reasoned and self-serving. It does not serve to resolve the issues, including important issues where clarification is needed. Majority rule, within the rules, should be encouraged. But to dismiss legitimate complaints by arguing that the majority agreed to not follow the rules, this is to substitute mob rule (or orchestrated monopoly rule) for the rule of law. We know where that leads to -- curtailed rights for those with minority opinions. And that should concern everyone.

The Secretary General of ISO, Alan Bryden, retires at the end of the year. August vacation is approaching, and before you know it there will be a retirement party with the cake and gifts, maybe a wall plaque or pewter paperweight. I am sure he does not need or desire to spend more time being reminded of the OOXML disaster that occurred during his last year at ISO. TMB/SMB members all want vacation as well. So do I. But out of respect for Mr. Bryden's eventual successor, and our shared mission in JTC1, shouldn't we urge TMB/SMB to do their job and not leave this all unresolved for the next guy to deal with? Dismissing an appeal with so many open unresolved issue is not expediency. It is merely creating more dissent, more distrust and more trouble that we'll all need to deal with next time around. It is better, I think, to hear the appeals, get to the bottom of this, seek resolution, consensus and closure, and then to move on. Ignoring mistakes will not make them go away.

by Rob (noreply@blogger.com) at July 23, 2008 08:31 AM

July 22, 2008

Bob Sutor

OOXML appeals: Now or never

Rob Weir has published an extensive blog entry detailing why the OOXML appeals process should be allowed to go on. He says, in part,

Dismissing an appeal with so many open unresolved issue is not expediency. It is merely creating more dissent, more distrust and more trouble that we’ll all need to deal with next time around. It is better, I think, to hear the appeals, get to the bottom of this, seek resolution, consensus and closure, and then to move on. Ignoring mistakes will not make them go away.

We are now down to a matter of days for the countries on the ISO TMB and IEC SMB to decide whether the appeal process should continue. From what I have seen and heard, most people are extremely pessimistic about the likelihood of this happening. That is, the sentiment is that the conservative bureaucracies that let OOXML get this far will not tolerate any challenge to their process and decision making, and therefore want this appeals business to be killed right now. This, in my opinion, would be a huge mistake.

I think that ISO and IEC are on the edge of a precipice which, if they fall off, will cause them to rapidly lose relevance to IT (ICT) developments in many parts of the world, especially emerging markets.

What they appear to be saying to India, Brazil, South Africa, and Venezuela is “Go away, our process works. We love our process. You are wrong. Live by our rules and be quiet.”

If the appeals process is cut off without detailed community examination of the charges against what happened in the OOXML experience, I think that the reputations of the ISO and IEC will continue to diminish. It does not seem to me that anyone at the senior levels of these organizations gets this. Rather than giving these four nations the cold shoulder, and doing it with what appears to this reader as having arrogant undertones, it makes far more sense for ISO and IEC to allow the process to carry on.

This would allow the various stakeholders to explain their arguments, mutually understand what did and didn’t work, and come to common conclusions. It would also lay the groundwork for whatever reforms are necessary so that the OOXML embarrassment never happens again.

If this is stopped now, we will instead be left with the sense if not knowledge that the monolithic ISO and IEC organizations are inflexible and ultimately believe themselves to be infallible. “Thanks for your opinion. You are wrong. Go away.”

To the countries that are voting on whether to continue the appeals process, I say that stopping it now is just bad foreign policy. The emerging nations are critically important to the IT future of the world. Want them to use common standards with everyone else? Want them to stop developing regional or national standards in conflict with “international standards”? Want them to believe that engaging in the international standards process is not a bureaucratic waste of time? Let the appeals process continue.

Read Rob’s blog entry to understand the reasons why the process should continue. Demonstrate that the stakeholders in the international standards process will not be stifled. Show that the ISO and IEC processes can withstand examination and evolve to support the needs of this century.

Either way, things are going to change. The OOXML debacle was a wakeup call for people around the world to see how the game was played. Many of them didn’t like it. If the ISO and IEC does not want to be pushed into the background in the future of ICT, they need to change and respond intelligently and responsibly to what we saw happen with OOXML.

For reference, here are the countries that sit on the boards:

ISO TMB Countries IEC SMB Countries
Brazil Brazil
Canada Canada
China China
Denmark Denmark
France France
Germany Germany
Japan Japan
Netherlands Netherlands
Spain Spain
UK UK
USA USA
Australia Norway
Italy South Africa
Korea
Sweden

© Robert S. Sutor for Bob Sutor's Open Blog, 2008.
This work is licensed under a Creative Commons Attribution-Noncommercial-No Derivative Works 3.0 Unported License.
Posted under: Document Formats, Standards.
Permalink | No comments

by Bob Sutor at July 22, 2008 09:30 PM

Daily Links 07/22/2008 (p.m.)

  • “Creating an alternate standards organization will be an exceedingly tough task, but standards are not an area where compromises can be tolerated. Standards govern our lives in a million different ways and the common man and woman deserve to have their standards created in an open, transparent manner that benefits everyone. Let me know what you think of the idea of creating an open standards organization for the benefit of the emerging economies.”

    tags: OB, ISO, IEC, OOXML, India, standards

  • “As travel costs rise and airlines cut service, companies large and small are rethinking the face-to-face meeting — and business travel as well. At the same time, the technology has matured to the point where it is often practical, affordable and more productive to move digital bits instead of bodies.”

    tags: OB, travel

  • “Long time followers of the ODF-OOXML story will recall that there is a third editable, XML-based document format in the race to create the documentary record of history. That contender is called UOF - for Uniform Office Format, and it has been under development in China since 2002, although I first heard and wrote about it back in November of 2006. Last summer, UOF was adopted as a Chinese National Standard, and last Friday the first complete office suite based upon UOF was released. It’s called Evermore Integrated Office 2009 (EIOffice 2009 for short), and here’s the story.”

    tags: OB, China, UOF


© Robert S. Sutor for Bob Sutor's Open Blog, 2008.
This work is licensed under a Creative Commons Attribution-Noncommercial-No Derivative Works 3.0 Unported License.
Posted under: News.
Permalink | No comments

by Bob Sutor at July 22, 2008 08:30 PM

FaceBook Group: Parents of UChicago Class of 2012

U of Chicago logoI’ve started a group over at FaceBook for parents of students entering the University of Chicago this Fall. Feel free to join if you fall into that category!

FaceBook Group: Parents of UChicago Class of 2012


© Robert S. Sutor for Bob Sutor's Open Blog, 2008.
This work is licensed under a Creative Commons Attribution-Noncommercial-No Derivative Works 3.0 Unported License.
Posted under: Education.
Permalink | 3 comments

by Bob Sutor at July 22, 2008 02:23 PM

Solveig Haugland

If you use Linux, you MUST try gLabels

Download it now, use it now.

http://glabels.sourceforge.net/

This is a beautiful program, a well-balanced combination of power, simplicity, good design, and ease of use. Thanks to Keith for pointing it out to me.

There's no Windows or Mac version, sadly.

Among the things you can do are:
- automatically (no effort on your party) suppress empty address lines
- do bar codes
- point straight to a CSV or similar format file to bring in records
- deselect records you don't want to print
- add graphics and drawing shapes
- apply formatting
- easily preview the whole sheet

Here's a screen shot with a summary of what you do. I'll do more detailed instructions later but here's the quick info. I love it.

Glabelscallouts  

by training@getopenoffice.org (Solveig Haugland) at July 22, 2008 01:39 PM

Boudewijn Rempt

Tablet woes...

For months, everything seemed fine in tablet-on-linux-with-Qt land. Or relatively fine. I could sketch with impunity using Krita 1.x and Krita trunk (unless I tried to paint outside the image itself, that is). A first gentle reminder of the state of tablet support under Linux/X11 came when Naomi wanted to try the Gimp for a change and she noticed that there was an offset of about a hundred pixels between her pointer on screen and where the drawing went. I shrugged and told her she'd better use Krita then.

Then Krita started crashing whenever I tried to use the stylus on my tablet notebook. Lukas Tvrdy suddenly lost tablet support. Cyrille Berger went on to investigate and discovered that we were getting spurious mouse events between the tablet events. Now KOffice is pretty smart in that it tries to map every input device, every individual wacom stylus, art pen or whatever the user has to its own tool. Spurious events that belong to another input device mean that tools started switching in mid-drawing, which in turn deletes the brush engine we were drawing with before we are done drawing. Ouch. A workaround is possible, of course, but workarounds have a nasty habit of coming back to bite the developer in the fleshy parts.

But plain painting with a tablet at least used to work without crashing -- and I have no idea what has changed. And, unfortunately, there is a host of issues with Qt's tablet support anyway: ranging from being hard-coded to certain names in X11.org (stylus and eraser, cursor isn't supported at all), which means Qt effectively doesn't have tablet support on OpenSUSE, to event compression (which means that we don't get all tablet events, which in turn means ugly lines because we cannot track exactly the artist's hand movement.

For reference, these are the Qt issues we're dealing with:

None of them seem close to being closed. The last one is for OS X -- I'm not sure how good the support for tablets on Windows is since I cannot test Krita on Windows with my tablet due to Microsoft messing up their upgrades. (In order to have a Windows in a virtual machine, I first need a Windows installer, and those are not free.)

So... What now? We have basically two choices: try to improve Qt's tablet support and submit a patch to Trolltech (or try to get paid for improving it?), or re-instate our old Krita 1.x tablet code. It had the same problems with detecting devices that aren't called "stylus" and "eraser", but at least we handled the "cursor" device and we managed to handle the event compression very well. Detecting when a user had changed between tablet and mouse was quite buggy, though, in 1.6. And if we resurrect our old code, we can do so for just Krita, or for all of KOffice. Or we could disable the code that maps an input device to a tool instance, but that would suck big time for artists who have gotten used to pan with the mouse and paint with the pen (like me).

July 22, 2008 10:25 AM

July 21, 2008

Andy Updegrove

Don't Forget UOF: Here Comes EIOffice 2009 (Updated)

Long time followers of the ODF-OOXML story will recall that there is a third editable, XML-based document format in the race to create the documentary record of history.  That contender is called UOF - for Uniform Office Format, and it has been under development in China since 2002, although I first heard and wrote about it back in November of 2006.  Last summer, UOF was adopted as a Chinese National Standard, and last Friday the first complete office suite based upon UOF was released.  It's called Evermore Integrated Office 2009 (EIOffice 2009 for short), and here's the story.
According to an English language article posted at t...

July 21, 2008 09:05 PM

Bob Sutor

Daily Links 07/21/2008 (p.m.)


© Robert S. Sutor for Bob Sutor's Open Blog, 2008.
This work is licensed under a Creative Commons Attribution-Noncommercial-No Derivative Works 3.0 Unported License.
Posted under: News.
Permalink | No comments

by Bob Sutor at July 21, 2008 08:30 PM

Ten questions on standards practice and leadership

Two weeks ago Stephe Walli published a blog entry called “Developing a Standards Office for Google.” I’m not sure what prompted this advice nor how it was received at Google, but it contains a lot of interesting insights and is worth a read. I especially encourage you to substitute in your organization’s name for “Google” and see how much of it should apply to what you are doing.

There are a few other questions I’ve been thinking about that I would like to throw out there. In practice, those of us who do have a lot of organization around standards deal with these all the time. That said, they may not get the focused attention they need when other more urgent matters are being dealt with.

  • Do you have a purposeful program to bring younger technologists into your standards participation program?
  • Within your standards program, how do you do leadership development?
  • When you do year-end evaluations of your employees, how do you measure and weight standards participation?
  • What roles do standards participation and leadership play in career development?
  • Do standards participation and leadership count when considering job promotions?
  • How do you balance the technical, business, and legal needs within your standards program?
  • Does one of technical, business, and legal tend to dominate your program and is it the right one?
  • How do you coordinate standards that affect multiple business areas?
  • How do you supply the resources for standards efforts that affect multiple business areas?
  • Do standards people spend more time “tin cupping” for necessary money and resources than they do actually creating, evaluating, managing, or implementing standards?

There are a lot of questions that could be asked about standards programs and how best to manage them. What do you think are the most important questions your organization needs to answer today to be better equipped to benefit from open standards in the next five or ten years?


© Robert S. Sutor for Bob Sutor's Open Blog, 2008.
This work is licensed under a Creative Commons Attribution-Noncommercial-No Derivative Works 3.0 Unported License.
Posted under: Standards.
Permalink | No comments

by Bob Sutor at July 21, 2008 08:26 PM

Family UK Trip, Days 3 and 4 - Guest Blog Entry

It’s been a couple of weeks since my last entry on the family trip we took to the UK. In that piece I described what we did in Bath and the drive to Liverpool. Unfortunately for me, I spent almost all my time in Liverpool recovering from food poisoning. My wife Judith Hunter wrote today’s guest entry about what she and the kids mostly did without me during that part of the trip.

I have been waiting to write this entry until I got photos from my daughter’s camera to illustrate it. Since it appears that isn’t going to happen, I’ll just forge ahead, pictureless.

Bob was clearly not up to being a tourist the day after his epic drive through Wales. He had a simply awful night, thanks to his food poisoning, and we just let him be the next morning. So, after being assured by the hotel concierge that it was an easy walk down to the Albert Dock, Liverpool’s nicely executed tourist district, the kids and I set out after breakfast. Well, it was the only time of driving rain we had during our sightseeing, so the walk was a wet one. And the concierge had explicitly told us to walk along the water rather than the very busy road, not realizing that there was a massive construction project that would involve a long detour and end us up on the busy road (which had sidewalks anyway, so what was the problem?). We arrived at the Albert Dock literally soaked through.

The Albert Dock is an area of large brick warehouses right along the waterfront, one of which had a wharf in the middle where a courtyard might otherwise be. The buildings have been turned into restaurants, shops, and museums, and the whole thing is very nicely done. Liverpool is clearly trying to make itself into a tourist destination, which involves giving visitors a little something beyond the Beatles, and I think they have largely succeeded.

We, however, were there for the Beatles. So we quickly made our way over to “The Beatles Story,” the smallish museum at the end of the Albert Dock that had been our goal for the morning. Now, I must have looked pretty pathetic after our long, sodden trek from the hotel, which must have led the staff of the museum to feel I was in need of a break. To our astonishment, they decided to allow us entry free, even though they don’t normally accept the British Heritage passes I had shown them when I was inquiring about admission. That must have saved us $50 or so. Gratefully, we hustled in to the museum after a group of school children and were soon submerged in Beatlemania.

The bulk of the collection is reproductions of black and white photographs with only a few artifacts, but they are all explained and presented so well that one hardly cares, especially because it is all accompanied by a jaunty Fab Four soundtrack. There is also a display of suits just like the Beatles wore when they first became so popular (the grey collarless ones with the black piping) and a loving reproduction of the dive the Beatles spent so many nights playing in, “The Cavern.”

I say “loving” reproduction, but perhaps I should say “painstaking.” One of the details they made sure to include was the overwhelming smell of disinfectant, which I guess they had to use to hose down the establishment every night after closing time. The collection ends with an exhibit on the post-Beatles careers of each of the members of the band, after which you are deposited in—what else?—the “Beatles Story” store (a very well-stocked one, I might add). I’m someone who was born a little too late (1961) to have been aware of most of the Beatles’ trajectory as it was happening, and I’m also an historian, so I was struck by a very odd feeling of how this entire Beatles experience could at once feel like the very distant past and current events.

More than anything, I think that is a testament to how important their music was and how the Beatles truly were more than the sum of their parts. In fact, whenever our family, with all of us having very distinct musical tastes, wants to listen to something together, the Beatles makes us all happy. I’m not quite sure how that works, but it does, and I suspect it’s true for many other families as well. And I think that’s why their music still seems present to us in our everyday lives. But the “Beatles Story” makes it clear that that music was produced in a very particular context, one that is increasingly distant from our lives. It’s a good way to make us appreciate the music on a wholly different level, or it was for me.

That afternoon, Bob willed himself well enough to accompany us on the bus tour of Liverpool geared to the Beatles’ lives, which Bob described in an earlier post. That was fun in a lot of ways, and there is one description I would add to Bob’s that reinforces the point I was trying to make in the previous paragraph. There was a 40-ish man from Argentina in the front row of the bus, and it was very clear to us all that this man was fulfilling one of his life’s goals by visiting the physical origins of the Beatles. What really brought it home for us when when we noticed this man, who spoke very little English and yet was so clearly a Beatlemanic, ecstatically scraping some dirt from around the base of the Strawberry Fields gate to bring home with him. I’ve never been a Beatlemaniac myself, but I’ve always enjoyed them. Seeing this man’s happiness was a real testament to the enduring power of their music.

As Bob noted, he needed the next morning off, and the kids were happy to join him in some down time. So I walked down to the Albert Dock myself. As an historian of nineteenth-century America, I wasn’t about to leave Liverpool without seeing the International Slavery Museum (ISM). We needed to be checking out of the hotel that morning and leaving for York, so I didn’t have a great deal of time, but it was time very well spent.

This museum is within the larger Maritime Museum, but it could just as easily stand on its own. Liverpool’s status (before its twentieth-century decline) was built on shipping, and its shipping trade was an integral part of the slave trade that so transformed the world. Liverpool merchants would invest in shares of cargoes of goods to trade in Africa in exchange for slaves. The ships would then cross the Atlantic (the “Middle Passage”) and sell their cargoes of human flesh in the slave markets of the new World. The ships would then return with their profits invested in raw materials, usually plantation-grown crops, to Liverpool.

By splitting these shipments into shares, merchants spread the risk at a time when disease and shipwreck made any such investment perilous and allowed almost an entire city to profit from the slave trade. The museum has three main galleries: the first on the Africa the slaves were forced to leave, the second on the experiences of slavery, and the third on the continuing effects of slavery. The subtext of each of these seems to be “Liverpool did this and we are VERY sorry.” As you might expect, the second gallery is the most harrowing and effective. The museum uses video and audio in compelling ways to drive home aspects of slavery we have a very hard time grappling with. One room uses video of a woman describing the experience of preparing her daughters for sale, knowing she will never see them again. Obviously, this is a recreation, but it is very well done.

I think its effectiveness is enhanced by the fact that you view it in a very small space, and the depiction is of disparate moments in the process, projected onto different walls. The whole experience moved me to tears. Even more effective, devastating even, was the circular room where you were literally hemmed in and made to feel as if you were one of the slaves in a cramped and dark hold, just like the man projected on the wall who clearly could not move and might not survive his ordeal. And, of course, you had to consider, even if the slaves did survive the horrors of the Middle Passage, what waited for them at the end of the journey? This is certainly not feel-good tourist material, but it is something all of us need to see. We cannot begin to understand our own world until we understand this part of the past and its ongoing ramifications.

Having spent way almost all of my time in the ISM, I could only race through the galleries of the Maritime Museum as I left. I wish I had had more time to give it, as the one thing that sunk in was compelling. There was a display about the Titanic, as the White Star Line had only just previously left its company home of Liverpool due to competition from the Cunard Line. That meant that many of the crew members and staff were from Liverpool, and they, of course, went down with the ship. As I was quickly taking this in, I realized that the audio being piped in was of an orchestra playing “Nearer My God to Thee,” which is exactly what the Titanic’s orchestra played as the ship sank. I also saw that there were displays on the Lusitania (a Cunard ship) and World War I and U-boats in general. Another display was about World War II in the North Atlantic. I’m sure if we’re ever back in Liverpool we will build in time to see this museum properly, especially as Bob’s father served in the U.S. Navy in the North Atlantic during the war.

It was a little odd to be without the family for the morning during this family vacation, but I think the Museum of Slavery is a solitary experience, whether you have company or not. I hope my family will be able to see it someday, but I won’t be sorry that William will be older when he does. It has frightening, intensely moving moments, which I think he will be able to appreciate more in a few years. I’m sorry Katie and Bob couldn’t see it this time, but I’m also glad that I got to explore it at my own pace in my own way. I would highly recommend it, but I wouldn’t call it a family outing.


© Robert S. Sutor for Bob Sutor's Open Blog, 2008.
This work is licensed under a Creative Commons Attribution-Noncommercial-No Derivative Works 3.0 Unported License.
Posted under: Travel.
Permalink | No comments

by Bob Sutor at July 21, 2008 01:44 PM

July 20, 2008

Jan Hambrecht

Managing guide lines


Some Planet KDE readers have probably noticed some KOffice soft-freeze anouncing blog entries (1, 2). I want to jump on the bandwagon and write about a feature from the feature plan I just finished today.
It started already some days ago when I brought back dragging guide lines from rulers to the current open document of a KOffice application. As that was done in KOffice shared libraries all applications benefit from that after adding a few lines enabling it. The next thing I did was adding support for snapping to these guides lines when e.g. moving objects on the canvas. This was relatively easy as I only had to add a new snapping strategy to the existing snapping framework in the flake library.
As dragging guides lines to the canvas and snapping to them is only a nice start but not the whole thing, I worked the last 2 days to further improve the guide line support. So I implemented a guide line tool which is activated when the user double clicks on a guide line just dragged to the canvas. The tool helps in easily selecting single guide lines, moving them around, adding new lines, deleting existing ones and specifying exact guide line positions by using an input field. This makes it really a joy to manage guide lines in an interactive manner. And the best is that all KOffice applications are supported for free. I love code sharing!
And for those readers asking themselves what the hell I am talking about here is a short screencast demonstrating some of the things i just explained.

by jaham at July 20, 2008 10:43 PM

Cyrille Berger

Darkroom 1.0 and Import Raw in Krita

It all started on Friday when I had a look at the pictures I took in Berlin, during the KDE-Bindings meeting and on my way to the airport in the city center. I found them incredibly noisy, my digital camera is starting to age, it's more than four years old, so I was wondering if it wouldn't be a good idea to replace it. At first, I had decided to wait a little bit before buying a DSLR, but seeing how poorly hand-held camera still behave, yay they have more mega-pixels, but why is it useful if the results is completely noisy and blurry ? And you can't tell yourself that you will buy one of the low mega-pixels camera, since they also have crap results, since they sell their product on the number of mega-pixels, no manufacturer will take the time of making a good hand-held camera, sad. So I turned myself to a DSLR (help with the fact that price have considerably dropped recently).

Since new babies are introduces with a picture:





I didn't had time to use it much, but I still spend sometime yesterday afternoon taking pictures in Toulouse, but I already like it a lot, since I was able to concentrate on just taking pictures instead of spending time adjusting options, while still having the possibility to adjust them for extreme situation. Which is good, I am so used to take picture with a silver film, entry level camera Nikon F60, where the only things you can do is adjust the speed and aperture, which is about all you usually need.

Here is a view of the Capitole:





Darkroom 1.0



Back to the point, KDE applications, since that's probably all you want to hear about. One of the usual feature of DSLR camera is the possibility to save pictures as RAW file, which is basically a dump of the sensor output to memory. To be precise, there is no such things as a RAW file format, there are about hundred of them, for each camera manufacturer, model and sensors.

Now that I have a camera with RAW, I want proper support for it in Krita and in my KDE environment. Especially that I was stupid enough to shot around 20 pictures as RAW files while I just wanted to have one or two for testing.

On unix, the main application to decode RAW files in something useful is dcraw. In the KDE side we have libkdcraw, which offers a front-end to a stable dcraw version (yes one of the bad side of dcraw is that it is not a library, but a command line tool whose option changes all the time) and a configuration widget. Using that library I told myself it would be easy to write a KDE based RAW decoder. Yes, I know there are already quiet a few of them, but Darkroom is like 400 lines of code, since all the logic is either in dcraw or in libkdcraw which is shared among KDE applications.

A few hours later, here is the result:





You can get it from my website if you want to play with it. I am not to sure about its future, one things is certain, I don't want to invest much time in Darkroom, maybe on libkdcraw, or of course Krita, which would bring back improvements to Darkroom.

Import RAW in Krita



The next logical things to do is to get an importer for RAW in Krita, actually there was one in Krita 1.6, but did I mentioned that interfacing with dcraw sucked ? Well, that means the Krita RAW importer start stopping working and there was no one who had time to fix it and maintaining, that's where using libkdcraw will help us, since the maintaining burden is shared (or currently delegated).

So a few minutes after Darkroom was finished, a new RAW importer from Krita was written (things are much easier when you know the API of a library):





I have some RAWorld Domination Plan for Krita, I am toying with the idea of editing the RAW file inside Krita instead of importing it, but that's for an other time, maybe in a year or two.

by Cyrille Berger (noreply@blogger.com) at July 20, 2008 03:50 PM

July 19, 2008

Bob Sutor

Daily Links 07/19/2008 (p.m.)

  • “NATO has included the International Standardization Organization’s (ISO) certified Open Document Format (ODF) in its list of mandatory standards to promote interoperability. NATO’s standards list includes Rich Text Format (RTF), extensible markup language (XML) and Office XP formats as requirements for the sharing of data.”

    tags: OB, NATO, ODF


© Robert S. Sutor for Bob Sutor's Open Blog, 2008.
This work is licensed under a Creative Commons Attribution-Noncommercial-No Derivative Works 3.0 Unported License.
Posted under: News.
Permalink | One comment

by Bob Sutor at July 19, 2008 08:30 PM

Andy Updegrove

Welcoming Brian Proffitt (and looking forward to the LDN)

Although I'm a little late doing so, I'd like to add my voice to Amanda McPherson's in welcoming Brian Proffitt to the Linux Foundation.  Amanda is the Linux Foundation's Vice President, Marketing and Developer Programs, and posted the official welcome on Thursday at the Linux Foundation Web site here.

As I expect just about every reader of this blog knows, Brian has been the Managing Editor of LinuxToday for quite a few years (as well as Managing Editor
of various other Jupiter Media properties: LinuxPlanet, Enterprise Linux Today, AllLinuxDevices, LinuxPR, and JustLinux).  If you missed it, you can find Brian's  farewell column at Linux...

July 19, 2008 03:55 PM

Boudewijn Rempt

I'm really, really glad

That I am a Linux user. I would probably be just as happy as a BSD user or an OpenSolaris user -- and I'm really glad that I'm not really a Windows Vista user. I used to keep a Vista partition around to test Corel Painter X with (because Corel Painter doesn't install under Wine), but seldom boot Vista.

So, when I last booted into Vista, it had an enormous backlog of updates to install. Which I foolishly allowed it to do. The result? Something called winload.exe is apparently borked beyond recovery. A quick google shows that it's apparently a know problem. Right... Breaking your basic OS kernel loading during an update, that makes Ubuntu's X11 foul-up look good in comparison! At least with Ubuntu, you can get all the media you like -- my laptop came without installation media, and the recovery thing on the recovery partition seems to want to erase my whole hard disk.

Oh, well -- another 16GB of hard disk available!

July 19, 2008 02:25 PM

Playing with the Wacom tablets

Lukas Tvrdy, the Krita Google Summer of Code student currently has one of the two wacom Intuos tablets with art pens the community has sponsored us with. (The other is with Emanuale Tamponi). One of the goals of us having these fancy tablets is making sure Krita does interesting things with features like tilt and rotation, and one of the goals of Lukas' summer of code project is to make a chinese brush brush engine that takes these parameters into account. But, of course, serendipity is always welcome:

I've asked Lukas to make sure that we won't lose this effect through over-eager debugging :-)

July 19, 2008 01:25 PM

July 18, 2008

Cyrille Berger

Howto: fun blog entry while stabilizing software

Boudewijn just mentioned that KOffice was entering soft-freeze and that it would mean more boring blog entries while we work on stabilizing KOffice. Well I must disagree with that, I usually find the most annoying bugs while preparing blog entry, and when working on stabilizing Krita, it usually wake up my creativity part (mostly because it's not sucked by my coder side while designing new features), which can be turn in fun entries.

I just bought the new Super Smash Brawl for WII (yeah not the best way to concentrate yourself on bug fixing, but very good to clear your mind), which includes the infamous Mr Game & Watch character (probably for nostalgic reason, my favorite). So this has inspired me: it should be easy to reproduce it using Karbon:





And I must say, the work that was done on Karbon14 by Jan Hambrecht for 2.0 is really impressive, the curve editing is really good now (compared to older version). And the nice thing is that you can use what you have create in Karbon14 directly in other KOffice and you will benefit from the same editing capabilities:




by Cyrille Berger (noreply@blogger.com) at July 18, 2008 10:03 PM

Bob Sutor

Daily Links 07/18/2008 (p.m.)

  • “Due to my past involvement in OpenOffice.org and ODF, I was curious to find out if and where the SAP products already support the ISO standard OpenDocument Format. I was happily surprised when I found out that ODF is already supported by the SAP List Viewer component (also known as the ABAP List Viewer or ALV), which is used many many times in all kinds of areas for displaying tabular data in a grid. The SAP List Viewer component allows exporting to ODF spreadsheet files in addition to Microsoft Excel files.”

    tags: OB, ODF, SAP


© Robert S. Sutor for Bob Sutor's Open Blog, 2008.
This work is licensed under a Creative Commons Attribution-Noncommercial-No Derivative Works 3.0 Unported License.
Posted under: News.
Permalink | No comments

by Bob Sutor at July 18, 2008 08:32 PM

List of US Starbucks store closures

I had to look around a bit to find this, so here’s the full list of Starbucks store closures in the United States.

We have only one Starbucks within 15 miles of here (in town, in fact), and that is being closed. Rochester, NY, appears to have been saved.


© Robert S. Sutor for Bob Sutor's Open Blog, 2008.
This work is licensed under a Creative Commons Attribution-Noncommercial-No Derivative Works 3.0 Unported License.
Posted under: News.
Permalink | One comment

by Bob Sutor at July 18, 2008 06:05 PM

Boudewijn Rempt

Freeze!

Well, only a soft freeze, not hard yet. But that means that we won't add new features to KOffice anymore that haven't yet been announced in our feature plan. And those features, even though in the plan, that haven't been at least a little credibly implemented by September 16th won't make the cut for 2.0.

What does that mean? Well, our blogs will become a lot more boring. We'll be doing more and more stabilisation work. And more and more bug fixing. And more and more smoothing out of wrinkles. And more and more things no-one can interpret as a "promise", even though it's only the enthusiastic articulation of a developer in the heat of the hunt.

On the other hand, we've been working on KOffice 2.0 since 2006. That's right -- we started porting KOffice to Qt4 and KDE4 March 27th, 2006. And it's no denying the road has been gruelling. Really, I totally grok the GTK people who don't want an api break for GTK 3.0. On the other hand, unless GTK gets gingered up a lot, any GTK app will be too nineties for words in a year or two.

And moving an app over to a new API is only the beginning. Frictions among KOffice developers, chasing the taillights of kdelibs, Qt4 that wasn't really as excellent as it should have been until 4.3, personal things like job or house changes, an increase in bad manners among the general public (although I remember saying the dot wasn't any fun anymore in 2006 already). Sometimes the fun and excitement was hard to find. And now we're in boring stabilisation mode again...

And I'm still worried about sustainability. I worry whether it's possible to write world class office software with more or less one part-time coder per application. Especially when that part-time aspect gets eroded by days jobs. That is why it's so great that NLnet sponsors us, with money for logos and money for Girish Ramakrishnan to really focus on some issues. But we really need more people!

You don't need to know C++ -- we can teach you that, no problem. And despite the aforementioned frictions we're a nice bunch of people, really. And we're pretty patient with questions. We cannot promise money or riches, but we can guarantee fame and fun! And we're committed -- we'l go on and on, alpha after alpha until we have something we dare call a beta -- and then we'll go on and on until we've got a release candidate.

July 18, 2008 03:25 PM

Bob Sutor

NATO: ODF is fine with us

A colleague just sent me a link to the NATO “3.4. NNEC Core Enterprise Services” which is part of the NATO Interoperability Standards and Profiles document. Lo and behold, about half way down the document in the Standards section is “OpenDocument ISO/IEC 26300:2006.” That is ODF.

Adopter by adopter, person by person, country by country, organization by organization, ODF keeps winning.

Preceding the mention of ODF are two entries which I find a little confusing.

  • Office 2000 formats: Office XP - Not to be used for new systems.
  • Office XP formats - Pertains to the interchange formats of MS Word, Excel and PowerPoint, irrespective of the actual MS Office version or general office automation package being used.

My interpretation of this is that they want people to use the Microsoft Office XP binary formats, even if they are using Office 2003 or 2007. People are not to save in, say, Office 97 formats.

Clarifications and corrections welcome.


© Robert S. Sutor for Bob Sutor's Open Blog, 2008.
This work is licensed under a Creative Commons Attribution-Noncommercial-No Derivative Works 3.0 Unported License.
Posted under: Document Formats, Standards.
Permalink | 3 comments

by Bob Sutor at July 18, 2008 02:22 PM

Rob Weir

What is Rick smoking?

Former Microsoft consultant Rick Jelliffe has posted his own particular brand of science fiction/fantasy, this time in his favorite subgenre, a parody of a drug-induced psychosis, where after uneasy slumber Rick awakes in some alternate parallel universe and finds that JTC1/SC34 is open and transparent and OASIS is closed, and decides to write a rambling blog post about it.

If you like unintentional humor, you will enjoy reading Rick's over-the-top post.

Rick suggests that organizationally JTC1/SC34 is a more participatory environment for developing standards than OASIS.

JTC1's process, based on National Body voting is both effective ... and more genuinely open, because it is impossible to stack either directly or indirecty.

Let's test that proposition. Let's compare OASIS and JTC1/SC34.

Who can participate? In OASIS, anyone can participate, from any company, organization, government agency, non-profit corporation in the world. Or you can join as an unaffiliated individual, as many have. You don't need your government's permission to join. You just do it. Most join with a nominal membership fee ($300 for individuals) but membership grants are available in some cases, when the fee would be burden for active individual contributors.

What about participation in JTC1/SC34? First, you must be a member of your NB. How do you become a member of your NB? In the US the price is $1,200 and you must be representing a company or organization. Individuals? Sorry, you are not allowed to participate. In other countries the rules vary. In some cases membership is not available at all at any price. You are essentially wait-listed until an opening becomes available. (Sorry, we don't have enough seats, we heard in Portugal). In some countries, like China, membership is forbidden to native citizens who are employees of foreign subsidiaries in China. In other countries you can't join at all. It is entirely a government decision. So, good luck joining the NB of Syria, where the constitution has been suspended under emergency rule since 1963. (But somehow they managed to make time to vote on the OOXML ballot. Zimbabwe as well, that paragon of open participation.)

Now, it is entirely possible for a standards organization to appear open, but in practice to be inaccessible. So we must look at the complete cost of participation, not just the initial membership fees.

The OASIS ODF TC does its work entirely on an email list, a wiki, and via weekly phone calls, which are toll-free calls for most participants. I don't recall there ever being a face-to-face meeting, certainly not so long as I've been a member. This use of technology lowers the barrier to participation, so anyone can be effective on the TC if they wish. In particular it makes it easier for those who have day jobs and can only contribute to the mailing list during non-work hours.

What about JTC1/SC34? To participate effectively requires attendance at several international meetings each year (Plenary's, WG's, Ad-hocs, BRM's, etc.), as well as participation at NB meetings. Since many of the participants are representative of large corporations or government agencies, a junket mentality prevails and the meetings are often held in some of the most expensive places in the world: Geneva, Granada, London, Kyoto, Jeju Island, etc.

JTC1 does not allow meeting participation by telephone. Since important votes, are held at these meetings, and no provision is made for remote participation, one cannot effectively participate in JTC1/SC34 without a substantial budget for international travel. Attendance at a single meeting — the DIS 29500 BRM — was $3687.52 for me, and I flew coach and ate cheap. How many standards meetings like that can you as an individual or your small company afford per year?

Further, note the nature of your membership — what can you actually do? Can you vote? In OASIS, it is one person/one vote. In the TC, your vote as an individual with a $300 membership fee is counted exactly the same as my vote representing an OASIS Foundational Sponsor. At the organizational level, it is one company/one vote, and the smallest OASIS member organization has exactly the same vote as the largest.

In JTC1/SC34 however, you typically can't vote at all. NB's vote, not individuals, not companies. So your opinion and your wishes are subject to the will of your NB. If your opinion varies from your NB's, you may not be accredited to attend an international meeting, and even if you are able to attend you may not be allowed to speak your opinions. This extra level of indirection and censorship means that you, as an individual, can do little. And to the extent your NB's committee is stacked by a single vendor and their partner community, or your NB decides to overrule or ignore its technical committee, or Microsoft calls your head of state to change the NB's vote, or any of the dozens of other documented shenanigans that recently occurred, your entire membership fee and participation will be an entire waste of time, money and effort.

Membership is OASIS is far more open and inclusive. You join. You discuss. You vote. Period. In JTC1/SC34, you are mired in layers of bureaucracy at the national and international level, in a system crafted by and for the big boys to cut back room deals and manipulate the process to the benefit of large corporations.

(Now that isn't to say that there are not some individual consultants out there who thrive in the JTC1 environment by mastering its dark, dusty, demon-haunted hallways. Even the largest corporations occasionally have need of this expertise, as Rick and others are quite aware. If JTC1/SC34 were truly open and transparent, such skills would not be needed. You certainly don't see anyone selling their services to help companies navigate OASIS, do you?)

What about transparency? As Rick demonstrates, OASIS meeting minutes and agenda are all posted and public. So is our mailing list. So are all of our drafts. So is our member and public comments.

But in JTC1/SC34, most of the documents are private, only accessible to SC34 members by password. And then occasionally JTC1 will step in prevent SC34 from releasing their own work , suppressing documents even from their own SC members. There are no public comments to speak of, and member comments on draft standards are secret.

So when you are back from your "trip", Rick, please let us know again, who wins on openness, participation and transparency?




And for the record, a couple of outright deceptions in Rick's post:

  • Rick says that there are 80 NB's, and thousands people participating in JTC1, but only 13 people participating on the ODF TC. This is a particularly inept comparison. Why is he comparing all of JTC1 to a single OASIS TC? If you look at OASIS overall, you will see that OASIS has more than 5,000 participants, representing over 600 organizations and individual members in 100 countries. The ODF TC itself has 53 members, including 7 members of JTC1/SC34.
  • Rick picks a "random" ODF TC minutes post from a year ago to attempt to suggest domination by a single company. Not so random a choice, methinks. It was a rare joint meeting of the ODF TC and the Metadata subcommittee, which brought in a far greater number of Sun employees than typically participate in a call.

by Rob (noreply@blogger.com) at July 18, 2008 09:18 AM

July 17, 2008

Bob Sutor

Daily Links 07/17/2008 (p.m.)

  • “Businesses launching online communities repeat a series of blunders. First, they have a tendency to get seduced by bells and whistles and blow their online-community budget on technology. Moran suggests that businesses spend resources identifying and reaching out to potential community members instead of investing in software that makes predictions, or even social-networking technology.”

    tags: OB, online, communities


© Robert S. Sutor for Bob Sutor's Open Blog, 2008.
This work is licensed under a Creative Commons Attribution-Noncommercial-No Derivative Works 3.0 Unported License.
Posted under: News.
Permalink | No comments

by Bob Sutor at July 17, 2008 08:30 PM

Solveig Haugland

How to create data entry forms from scratch, and make them into PDFs, in OpenOffice.org

Would you like to create:

  • A travel request form that your users fill out, then print or save and submit?
  • A public records form that residents of your city or county need to fill out, that you can just post on your government web site?
  • Any other form that people use that could contain check boxes, radio buttons, dropdown list, date entry fields, regular data entry fields, etc.?

Then use this PDF to learn how. It's a step-by-step guide to creating various types of fields using the Writer form tools. The PDF is for use by anyone for personal or professional use, but not for republication or other reuse in another form; if you'd like to reference it, please link back here.


Would you like to create: A travel request form that your users fill out, then print or save and submit? A public records form that residents of your city or county need to fill out, that you can just post...

by Solveig Haugland (training@getopenoffice.org) at July 17, 2008 05:07 PM

How to apply multiple colors or other fills to a shape you draw in Openoffice.org Draw

There are a lot of very nice prefab shapes in Draw. (And available in Writer and Calc too; just choose View > Toolbars > Drawing.)
Gr0

You can apply one color or other fill to each of them. If you draw a smiley face you either make it blue, or red, or with a rose fill, or whatever. (Let's leave out for now the issue of line color.)

Gragain

But let's say you want to make each point of the sun a different color, or the eyes in the smiley face a dfiferent color. You can't. Well, not by default.

Here's what you do. Right-click on the shape and choose Convert > To Curve.
Converttocurve
After that, right-click on the object again and choose  Ungroup.

You'll get something like this, depending on what the shape is.
Ungroup
And then you can select different parts of the shape and apply different formatting, plus drag parts of it out.
Grrrrrr

Once you're done formatting it, you should probably re-group. Select all the components, right-click, and choose Group.


The easiest way to select a bunch of small items is to "draw" around them with the arrow tool, the normal default selection tool. In this illustration, all the items for the split-apart octagon would be selected, but nothing from the smiley or star because you have to go ALL the way around an object to select it.
Selecting

by training@getopenoffice.org (Solveig Haugland) at July 17, 2008 04:49 PM

Diary of a CrazyFrench