Gary Edwards's personal annotations on this page
-
this TC does not have the final word
on what goes into the ODF 1.2 spec. There is still the OASIS vote, the
JTC-1 vote, and the ISO final ballot, with a few other stops along the
way. There is also the market's response to what this TC does. Given
that no one on this TC has objected to my considerable efforts to
raise public concerns with Microsoft's ISO submission and some on this
TC have lambasted Microsoft for creating interoperability barriers,
why should this TC's members consider themselves exempt from warnings
that they have just fallen into precisely the kind of behavior we
routinely criticize when it's Microsoft that creates the
interoperability barriers. Especially when it's the end users who will
pay the price of the non-interoperability?
This link has been bookmarked by 1 people . It was first bookmarked on 09 Feb 2008, by Gary Edwards.
-
Gary Edwards
marbux at his best.
-
this TC does not have the final word
on what goes into the ODF 1.2 spec. There is still the OASIS vote, the
JTC-1 vote, and the ISO final ballot, with a few other stops along the
way. There is also the market's response to what this TC does. Given
that no one on this TC has objected to my considerable efforts to
raise public concerns with Microsoft's ISO submission and some on this
TC have lambasted Microsoft for creating interoperability barriers,
why should this TC's members consider themselves exempt from warnings
that they have just fallen into precisely the kind of behavior we
routinely criticize when it's Microsoft that creates the
interoperability barriers. Especially when it's the end users who will
pay the price of the non-interoperability?
-
Would you like to comment?
Join Diigo for a free account, or sign in if you are already a member.