Comments for DIS29500 Comments http://www.dis29500.org Help the OOXML BRM concentrate on issues of substance Tue, 09 Feb 2010 04:08:05 +0000 http://wordpress.org/?v=2.5.1 Comment on GB-0250 by Joel Stobart http://www.dis29500.org/gb-0250/#comment-1984 Joel Stobart Fri, 07 Mar 2008 09:09:43 +0000 http://www.dis29500.org/gb-0250/#comment-1984 This says either this or that. It doesnt acturally resolve anything at all. Which is it are we getting rid of VML? or are we deprecating AUTOTEXT. This says either this or that. It doesnt acturally resolve anything at all. Which is it are we getting rid of VML? or are we deprecating AUTOTEXT.

]]> Comment on NZ-0030 by Matt http://www.dis29500.org/nz-0030/#comment-1932 Matt Wed, 27 Feb 2008 23:10:30 +0000 http://www.dis29500.org/nz-0030/#comment-1932 Note that this may have originally come from this MS sponsored sourceforge project: http://odf-converter.sourceforge.net/features.html search down page for "Repeat Heading in a Table" Note that this may have originally come from this MS sponsored sourceforge project:
http://odf-converter.sourceforge.net/features.html search down page for “Repeat Heading in a Table”

]]> Comment on IR-0009 by Matt http://www.dis29500.org/ir-0009/#comment-1931 Matt Wed, 27 Feb 2008 23:09:53 +0000 http://www.dis29500.org/ir-0009/#comment-1931 Note that this may have originally come from this MS sponsored sourceforge project: http://odf-converter.sourceforge.net/features.html search down page for "Repeat Heading in a Table" Note that this may have originally come from this MS sponsored sourceforge project:
http://odf-converter.sourceforge.net/features.html search down page for “Repeat Heading in a Table”

]]> Comment on FR-0087 by The Open Sourcerer http://www.dis29500.org/fr-0087/#comment-1834 The Open Sourcerer Sun, 17 Feb 2008 21:06:56 +0000 http://www.dis29500.org/fr-0087/#comment-1834 What about all the Latin type alphabets that are not 26 characters? In Swedish for example they have 3 different "A"s... What about all the Latin type alphabets that are not 26 characters? In Swedish for example they have 3 different “A”s…

]]> Comment on IN-0002 by Andre http://www.dis29500.org/in-0002/#comment-1782 Andre Thu, 14 Feb 2008 12:42:15 +0000 http://www.dis29500.org/in-0002/#comment-1782 May collide with the global relevance policy, so ECMA should better move. May collide with the global relevance policy, so ECMA should better move.

]]> Comment on SG-0001 by Andre http://www.dis29500.org/sg-0001/#comment-1781 Andre Thu, 14 Feb 2008 12:39:37 +0000 http://www.dis29500.org/sg-0001/#comment-1781 Silly. It does not address the problem and does not specify the algorithm. No documentation at all is provided. The appropriate solution would be to remove the element. Silly. It does not address the problem and does not specify the algorithm. No documentation at all is provided. The appropriate solution would be to remove the element.

]]> Comment on MY-0006 by Yoon-Kit Yong http://www.dis29500.org/my-0006/#comment-1750 Yoon-Kit Yong Wed, 13 Feb 2008 02:24:44 +0000 http://www.dis29500.org/my-0006/#comment-1750 A new tag should be here: "passing the buck" or "sweeping under the carpet". Disposition is to await future maintenance to fix this issue. === There is no "design challenge" in markup languages. HTML has been using % tags for over 15 years now. Browsers can parse it without a problem. XML is a long piece of strings. In the process of reading these string types, they are parsed as whatever internal datatype, and therefore "10.5%" string will be correctly represented as a 10.5 floating point value. A new tag should be here: “passing the buck” or “sweeping under the carpet”.

Disposition is to await future maintenance to fix this issue.

===

There is no “design challenge” in markup languages.

HTML has been using % tags for over 15 years now. Browsers can parse it without a problem.

XML is a long piece of strings. In the process of reading these string types, they are parsed as whatever internal datatype, and therefore “10.5%” string will be correctly represented as a 10.5 floating point value.

]]> Comment on MY-0005 by Yoon-Kit Yong http://www.dis29500.org/my-0005/#comment-1749 Yoon-Kit Yong Wed, 13 Feb 2008 02:19:29 +0000 http://www.dis29500.org/my-0005/#comment-1749 Adding a fifth method to encode dates is ridiculous. It is building complexity on the already complex 4 legacy type dates. Convertors should be used to translate the legacy date-types to ISO 8601 Adding a fifth method to encode dates is ridiculous. It is building complexity on the already complex 4 legacy type dates.

Convertors should be used to translate the legacy date-types to ISO 8601

]]> Comment on MY-0001 by Yoon-Kit Yong http://www.dis29500.org/my-0001/#comment-1748 Yoon-Kit Yong Wed, 13 Feb 2008 02:14:34 +0000 http://www.dis29500.org/my-0001/#comment-1748 The disposition doesnt clarify where all the "each positions" where the VML is replaced with DrawingML. The wholesale rip and replace is a good move, but may require an additional timeframe for verification. We do not know if the Annex is used for normative text, or just informative. The disposition doesnt clarify where all the “each positions” where the VML is replaced with DrawingML.

The wholesale rip and replace is a good move, but may require an additional timeframe for verification.

We do not know if the Annex is used for normative text, or just informative.

]]> Comment on CO-0158 by Alan Bell http://www.dis29500.org/co-0158/#comment-1693 Alan Bell Sat, 09 Feb 2008 13:03:01 +0000 http://www.dis29500.org/co-0158/#comment-1693 err, then again, comparing to the PDF it seems the last bit ", as accurately as possible" should be struck out. err, then again, comparing to the PDF it seems the last bit “, as accurately as possible” should be struck out.

]]> Comment on GB-0634 by hAl http://www.dis29500.org/gb-0634/#comment-1687 hAl Sat, 09 Feb 2008 08:26:03 +0000 http://www.dis29500.org/gb-0634/#comment-1687 New enumeration values are added, old inconsistant values are not removed New enumeration values are added, old inconsistant values are not removed

]]> Comment on CO-0158 by The Open Sourcerer » Get your five a day at dis29500.org http://www.dis29500.org/co-0158/#comment-1685 The Open Sourcerer » Get your five a day at dis29500.org Fri, 08 Feb 2008 22:51:35 +0000 http://www.dis29500.org/co-0158/#comment-1685 [...] As well as being able to comment on the many interesting dispositions (my favorite so far is CO-0158) you can press one of the handy “tag and go” buttons to record your thoughts and move [...] [...] As well as being able to comment on the many interesting dispositions (my favorite so far is CO-0158) you can press one of the handy “tag and go” buttons to record your thoughts and move [...]

]]> Comment on CO-0097 by Alan Bell http://www.dis29500.org/co-0097/#comment-1684 Alan Bell Fri, 08 Feb 2008 22:41:25 +0000 http://www.dis29500.org/co-0097/#comment-1684 I think that there could be a strikeout through one of those words lost in translation from pdf to html. I will check. I think that there could be a strikeout through one of those words lost in translation from pdf to html. I will check.

]]> Comment on FR-0522 by Luc Bollen http://www.dis29500.org/fr-0522/#comment-1683 Luc Bollen Fri, 08 Feb 2008 18:48:35 +0000 http://www.dis29500.org/fr-0522/#comment-1683 The Proposed Disposition text still makes reference to a specific product : the "PowerPoint Presentation file container". This is inappropriate for a normative part of an ISO standard. The Proposed Disposition text still makes reference to a specific product : the “PowerPoint Presentation file container”.

This is inappropriate for a normative part of an ISO standard.

]]> Comment on DK-0092 by Alan Bell http://www.dis29500.org/dk-0092/#comment-1678 Alan Bell Fri, 08 Feb 2008 11:06:38 +0000 http://www.dis29500.org/dk-0092/#comment-1678 Why are they defining namespaces for stuff that Excel, Powerpoint and Word can do that layers on information beyond the baseline? I thought OOXML was intended to capture all the idiosyncrasies of the legacy formats, plus all the idiosyncrasies of new office applications. Why are they defining namespaces for stuff that Excel, Powerpoint and Word can do that layers on information beyond the baseline? I thought OOXML was intended to capture all the idiosyncrasies of the legacy formats, plus all the idiosyncrasies of new office applications.

]]> Comment on NZ-0035 by Luc Bollen http://www.dis29500.org/nz-0035/#comment-1669 Luc Bollen Thu, 07 Feb 2008 19:03:31 +0000 http://www.dis29500.org/nz-0035/#comment-1669 The proposed disposition is not a valid response to the comment. The proposed disposition is not a valid response to the comment.

]]> Comment on GB-0369 by Luc Bollen http://www.dis29500.org/gb-0369/#comment-1667 Luc Bollen Thu, 07 Feb 2008 19:00:51 +0000 http://www.dis29500.org/gb-0369/#comment-1667 In the proposed disposition, "as accurately as possible." is still present. In the proposed disposition, “as accurately as possible.” is still present.

]]> Comment on US-0058 by Luc Bollen http://www.dis29500.org/us-0058/#comment-1666 Luc Bollen Thu, 07 Feb 2008 18:55:57 +0000 http://www.dis29500.org/us-0058/#comment-1666 In the proposed disposition: - "This element specifies whether applications should attempt to detect customize the output the target web browser for any web page produced from this document based on the target web browser, for example, and subsequently disable all user interface andby blocking any output which is not supported by that target web browser." I cannot understand what this means : "to detect customize the output the target web browser" ??? - " doNotRelyOnCSS -  relyOnVML" This is inconsistent : why not "RelyOnCSS" and "RelyOnVML" ? - The proposed determination table must be informative, and not normative. What is important is not the name of the browser, but the capabilities to be taken into account. In the proposed disposition:
- “This element specifies whether applications should attempt to detect customize the output the target web browser for any web page produced from this document based on the target web browser, for example, and subsequently disable all user interface andby blocking any output which is not supported by that target web browser.”
I cannot understand what this means : “to detect customize the output the target web browser” ???
- “ doNotRelyOnCSS -  relyOnVML”
This is inconsistent : why not “RelyOnCSS” and “RelyOnVML” ?
- The proposed determination table must be informative, and not normative. What is important is not the name of the browser, but the capabilities to be taken into account.

]]> Comment on CO-0097 by Luc Bollen http://www.dis29500.org/co-0097/#comment-1665 Luc Bollen Thu, 07 Feb 2008 18:47:17 +0000 http://www.dis29500.org/co-0097/#comment-1665 In the proposed disposition : "These restrictions shall should be enforced by applications" Do the mean SHALL or SHOULD ? In the proposed disposition : “These restrictions shall should be enforced by applications”
Do the mean SHALL or SHOULD ?

]]> Comment on GB-0145 by next_ghost http://www.dis29500.org/gb-0145/#comment-1664 next_ghost Thu, 07 Feb 2008 17:22:16 +0000 http://www.dis29500.org/gb-0145/#comment-1664 Lots of excuses for trivial feature request. Lots of excuses for trivial feature request.

]]> Comment on CO-0158 by Alan Bell http://www.dis29500.org/co-0158/#comment-1647 Alan Bell Wed, 06 Feb 2008 10:49:39 +0000 http://www.dis29500.org/co-0158/#comment-1647 wow, they just added words and said the same thing. wow, they just added words and said the same thing.

]]> Comment on GB-0499 by Alan Bell http://www.dis29500.org/gb-0499/#comment-1646 Alan Bell Wed, 06 Feb 2008 10:43:50 +0000 http://www.dis29500.org/gb-0499/#comment-1646 why is that the default? is it a sensible default? why is that the default? is it a sensible default?

]]> Comment on DK-0033 by Alan Bell http://www.dis29500.org/dk-0033/#comment-1623 Alan Bell Tue, 05 Feb 2008 22:28:29 +0000 http://www.dis29500.org/dk-0033/#comment-1623 so to implement the standard an application is expected to read and write 4 different types of dates. so to implement the standard an application is expected to read and write 4 different types of dates.

]]> Comment on GB-0298 by hAl http://www.dis29500.org/gb-0298/#comment-1488 hAl Fri, 25 Jan 2008 23:01:01 +0000 http://www.dis29500.org/gb-0298/#comment-1488 @Roman Korchagin You should make sure your UFT16 is actually UTF-16LE with no byte order mark. See: http://blogs.msdn.com/brian_jones/archive/2008/01/23/improvements-in-password-hashing.aspx#comments @Roman Korchagin
You should make sure your UFT16 is actually UTF-16LE with no byte order mark.
See:
http://blogs.msdn.com/brian_jones/archive/2008/01/23/improvements-in-password-hashing.aspx#comments

]]> Comment on IT-0002 by hAl http://www.dis29500.org/it-0002/#comment-1487 hAl Fri, 25 Jan 2008 22:55:16 +0000 http://www.dis29500.org/it-0002/#comment-1487 This document describes why the Italian request for a refrence implementation does not fit with ISO directives: http://www.narisa.com/downloads/OpenXML/ReferenceImplementationsInISOStandards.pdf This document describes why the Italian request for a refrence implementation does not fit with ISO directives:
http://www.narisa.com/downloads/OpenXML/ReferenceImplementationsInISOStandards.pdf

]]> Comment on CL-0049 by zoobab http://www.dis29500.org/cl-0049/#comment-1486 zoobab Fri, 25 Jan 2008 17:27:21 +0000 http://www.dis29500.org/cl-0049/#comment-1486 http://www.noooxml.org/forum/t-36122/printer-binary-and-ecma-tries-duck-and-cover Replace XML with Binaries and vice-versa. http://www.noooxml.org/forum/t-36122/printer-binary-and-ecma-tries-duck-and-cover

Replace XML with Binaries and vice-versa.

]]> Comment on FI-0003 by Andre http://www.dis29500.org/fi-0003/#comment-1419 Andre Fri, 18 Jan 2008 19:54:22 +0000 http://www.dis29500.org/fi-0003/#comment-1419 It is enough to decide on the disposition of the comments, then it can be carried out by the project editor who finalizes the text. It is no wrecking amendment but a reasonable proposal that just lacks some details. It is enough to decide on the disposition of the comments, then it can be carried out by the project editor who finalizes the text. It is no wrecking amendment but a reasonable proposal that just lacks some details.

]]> Comment on GB-0298 by Roman Korchagin http://www.dis29500.org/gb-0298/#comment-1397 Roman Korchagin Mon, 14 Jan 2008 09:24:46 +0000 http://www.dis29500.org/gb-0298/#comment-1397 I'm implementing export in DOCX format and trying to generate documentProtection attributes as per the spec. This includes "hash", "salt", spinds, and hash algorithm. Doing all according to the spec I cannot get the correct hash that MS Word will recognize the password. I'm sure the first stage (the legacy hash) I calculate correctly. I have a problem calculating the "new" OOXML hash that is based on the legacy hash with salt and spins etc. Can this be the spec flaw? How can this be verified? I’m implementing export in DOCX format and trying to generate documentProtection attributes as per the spec. This includes “hash”, “salt”, spinds, and hash algorithm. Doing all according to the spec I cannot get the correct hash that MS Word will recognize the password. I’m sure the first stage (the legacy hash) I calculate correctly. I have a problem calculating the “new” OOXML hash that is based on the legacy hash with salt and spins etc. Can this be the spec flaw? How can this be verified?

]]> Comment on GB-0027 by inigo http://www.dis29500.org/gb-0027/#comment-1364 inigo Tue, 08 Jan 2008 22:43:15 +0000 http://www.dis29500.org/gb-0027/#comment-1364 Very similar to DE-0148 Very similar to DE-0148

]]> Comment on DE-0148 by inigo http://www.dis29500.org/de-0148/#comment-1363 inigo Tue, 08 Jan 2008 22:42:59 +0000 http://www.dis29500.org/de-0148/#comment-1363 Very similar to GB-0027 Very similar to GB-0027

]]> Comment on FI-0005 by Boycott Novell » Quick Mention: More OOXML Issues Named and Explained http://www.dis29500.org/fi-0005/#comment-1317 Boycott Novell » Quick Mention: More OOXML Issues Named and Explained Wed, 26 Dec 2007 07:23:11 +0000 http://www.dis29500.org/fi-0005/#comment-1317 [...] careful attention to this insightful comment about Office binaries getting encapsulated in an XML-shaped wrapper. That pretty much sums up the purpose and essence of OOXML. It’s a gown for legacy formats [...] [...] careful attention to this insightful comment about Office binaries getting encapsulated in an XML-shaped wrapper. That pretty much sums up the purpose and essence of OOXML. It’s a gown for legacy formats [...]

]]> Comment on FI-0005 by André http://www.dis29500.org/fi-0005/#comment-1310 André Tue, 25 Dec 2007 13:35:14 +0000 http://www.dis29500.org/fi-0005/#comment-1310 It is possible and easy to add the Biff spec as an annex to the ISO NOOOXML spec. It is no big deal to do so and it helps us to get rid off one Brazilian comment. So please do, Microsoft It is possible and easy to add the Biff spec as an annex to the ISO NOOOXML spec. It is no big deal to do so and it helps us to get rid off one Brazilian comment. So please do, Microsoft

]]> Comment on CL-0049 by Boycott Novell » Open Office XML (OOXML): Software Patents, Briberies, Binaries, O/S-dependent Bits http://www.dis29500.org/cl-0049/#comment-1287 Boycott Novell » Open Office XML (OOXML): Software Patents, Briberies, Binaries, O/S-dependent Bits Sun, 16 Dec 2007 02:06:27 +0000 http://www.dis29500.org/cl-0049/#comment-1287 [...] that are hidden somewhere among 6,000+ pages of poor specifications. For example, have a look at this comment that was posted by Andrew Mason a couple of weeks ago: For OOXML to become a standard it is unacceptable to have OS dependant binary [...] [...] that are hidden somewhere among 6,000+ pages of poor specifications. For example, have a look at this comment that was posted by Andrew Mason a couple of weeks ago: For OOXML to become a standard it is unacceptable to have OS dependant binary [...]

]]> Comment on CA-0043 by hAl http://www.dis29500.org/ca-0043/#comment-1268 hAl Tue, 11 Dec 2007 16:03:35 +0000 http://www.dis29500.org/ca-0043/#comment-1268 Ecma has proposed using ISO/IEC 14977:1996 – Syntactic metalanguage – Extended BNF for formula notations Ecma has proposed using ISO/IEC 14977:1996 – Syntactic metalanguage – Extended BNF for formula notations

]]> Comment on US-0245 by hAl http://www.dis29500.org/us-0245/#comment-1267 hAl Tue, 11 Dec 2007 16:03:03 +0000 http://www.dis29500.org/us-0245/#comment-1267 Ecma has proposed using ISO/IEC 14977:1996 – Syntactic metalanguage – Extended BNF for formula notations Ecma has proposed using ISO/IEC 14977:1996 – Syntactic metalanguage – Extended BNF for formula notations

]]> Comment on GB-0361 by hAl http://www.dis29500.org/gb-0361/#comment-1266 hAl Tue, 11 Dec 2007 16:02:08 +0000 http://www.dis29500.org/gb-0361/#comment-1266 Ecma has proposed using ISO/IEC 14977:1996 – Syntactic metalanguage – Extended BNF for formula notations Ecma has proposed using ISO/IEC 14977:1996 – Syntactic metalanguage – Extended BNF for formula notations

]]> Comment on US-0270 by Adam Borowski http://www.dis29500.org/us-0270/#comment-1264 Adam Borowski Mon, 10 Dec 2007 09:22:19 +0000 http://www.dis29500.org/us-0270/#comment-1264 ISO uses "DIS29500" specifically to allow such renaming. The current label, "OOXML" not only causes confusion, but it does so on a purpose. Purposefully causing confusion may be a legal if sleazy marketing tactic, but it should be avoided at all costs in standards. Doable and justified. Certainly not a Wrecking Amendment -- although unlike Just Fix It it would have to be argued for. ISO uses “DIS29500″ specifically to allow such renaming. The current label, “OOXML” not only causes confusion, but it does so on a purpose. Purposefully causing confusion may be a legal if sleazy marketing tactic, but it should be avoided at all costs in standards.

Doable and justified. Certainly not a Wrecking Amendment — although unlike Just Fix It it would have to be argued for.

]]> Comment on IT-0002 by Steve Loughran http://www.dis29500.org/it-0002/#comment-1263 Steve Loughran Sun, 09 Dec 2007 11:55:52 +0000 http://www.dis29500.org/it-0002/#comment-1263 I think there are other ECMA standards with RIs; probably both JavaScript and C# come into that category, formally or informally. The problem with RIs is that they become the official specification of the system. In OOXML, MSOffice 2007 is the de-facto RI, as it is what everyone has to work with. So it is the effective specification. What would have been a better proposal would have been for MS to publish all their test XML docs, both valid and invalid. I think there are other ECMA standards with RIs; probably both JavaScript and C# come into that category, formally or informally.

The problem with RIs is that they become the official specification of the system. In OOXML, MSOffice 2007 is the de-facto RI, as it is what everyone has to work with. So it is the effective specification.

What would have been a better proposal would have been for MS to publish all their test XML docs, both valid and invalid.

]]> Comment on IR-0058 by Things n’ Stuff » Blog Archive » ובכן, זה מעניין http://www.dis29500.org/ir-0058/#comment-1262 Things n’ Stuff » Blog Archive » ובכן, זה מעניין Sat, 08 Dec 2007 04:03:14 +0000 http://www.dis29500.org/ir-0058/#comment-1262 [...] המעניין - איראן הגישה גם היא 58 הערות בתהליך התקינה, הערה איראנית מספר 58 הולכת כך: הערה: מכיוון שחלקים נרחבים מההגדרת התקן [...] [...] המעניין - איראן הגישה גם היא 58 הערות בתהליך התקינה, הערה איראנית מספר 58 הולכת כך: הערה: מכיוון שחלקים נרחבים מההגדרת התקן [...]

]]> Comment on ZA-0008 by hAl http://www.dis29500.org/za-0008/#comment-1261 hAl Fri, 07 Dec 2007 11:04:47 +0000 http://www.dis29500.org/za-0008/#comment-1261 @Warren Point is that for every technology you use you are bound by existing patents. Micrsoft has given right on their patents for OOXML implementation but that does not in any way dimishing the requirment for anybody implementing technology to verify wheather or not he breaches patents. also notworthy is that the south african comment here reaises questions on the robustness of the open specification promise but the IEC en ISO CEO's have apperantly confirmed that they are satisfied with this licencing (As can be read on Alex Browns FAQ page). http://www.jtc1sc34.org/repository/0932.htm#q4-1 This comment could therefore even be seen as resolved/solved. @Warren
Point is that for every technology you use you are bound by existing patents. Micrsoft has given right on their patents for OOXML implementation but that does not in any way dimishing the requirment for anybody implementing technology to verify wheather or not he breaches patents.
also notworthy is that the south african comment here reaises questions on the robustness of the open specification promise but the IEC en ISO CEO’s have apperantly confirmed that they are satisfied with this licencing (As can be read on Alex Browns FAQ page).
http://www.jtc1sc34.org/repository/0932.htm#q4-1
This comment could therefore even be seen as resolved/solved.

]]> Comment on US-0161 by Steve Loughran http://www.dis29500.org/us-0161/#comment-1260 Steve Loughran Fri, 07 Dec 2007 10:11:15 +0000 http://www.dis29500.org/us-0161/#comment-1260 The fundamental problem is that there are some characters that are allowed in a BSTR (probably even ASCII NUL) that XML flatly forbids. XML is meant to be a text format, after all. Escaping char's using ampersands isn't enough, because the next stage in the processing will reject the illegal character. In COM, BSTR is a length-delimited string (a Basic Str) that can contain anything, more even than a nul-terminated CString. Trying to put it inside XML is not something XML supports. The fundamental problem is that there are some characters that are allowed in a BSTR (probably even ASCII NUL) that XML flatly forbids. XML is meant to be a text format, after all. Escaping char’s using ampersands isn’t enough, because the next stage in the processing will reject the illegal character.

In COM, BSTR is a length-delimited string (a Basic Str) that can contain anything, more even than a nul-terminated CString. Trying to put it inside XML is not something XML supports.

]]> Comment on ZA-0008 by Warren http://www.dis29500.org/za-0008/#comment-1259 Warren Fri, 07 Dec 2007 00:25:29 +0000 http://www.dis29500.org/za-0008/#comment-1259 HAL states that the patents are openly viewable at the patent offices BUT do we know all the patents that apply so you can look them up in the first place. The patent holder SHOULD have to disclose ALL patents and licence or surrender such IP. HAL states that the patents are openly viewable at the patent offices BUT do we know all the patents that apply so you can look them up in the first place.

The patent holder SHOULD have to disclose ALL patents and licence or surrender such IP.

]]> Comment on DE-0148 by hAl http://www.dis29500.org/de-0148/#comment-1258 hAl Thu, 06 Dec 2007 16:24:57 +0000 http://www.dis29500.org/de-0148/#comment-1258 @arebenti Actually OOXML has a fairly usefull conformance clause (compared with ODF) that already allows partial implementations as long as the implemtation and or documentation around it says that it is a partial implementation and states (generally) what it supports or what it doesn't support. . Strangely enough the vague conformance clause in ODF would allow you to call any arbitrary file an Opendocument file. @arebenti
Actually OOXML has a fairly usefull conformance clause (compared with ODF) that already allows partial implementations as long as the implemtation and or documentation around it says that it is a partial implementation and states (generally) what it supports or what it doesn’t support.
.
Strangely enough the vague conformance clause in ODF would allow you to call any arbitrary file an Opendocument file.

]]> Comment on GB-0494 by Alan Bell http://www.dis29500.org/gb-0494/#comment-1257 Alan Bell Thu, 06 Dec 2007 13:10:53 +0000 http://www.dis29500.org/gb-0494/#comment-1257 Hi David, thanks for your comment, I wasn't really expecting quite so much in depth discussion so this is just the vanilla WordPress comment system. I am planning to add some bits to it soon to make it a fully baked comment system. Hi David,
thanks for your comment, I wasn’t really expecting quite so much in depth discussion so this is just the vanilla WordPress comment system. I am planning to add some bits to it soon to make it a fully baked comment system.

]]> Comment on US-0161 by David Carlisle http://www.dis29500.org/us-0161/#comment-1256 David Carlisle Thu, 06 Dec 2007 11:26:09 +0000 http://www.dis29500.org/us-0161/#comment-1256 "Can someone tell me why they don’t use W3C standard for this?" If you refer to #8 via a numeric reference as you suggest then it is a fatal error in XML 1.0, making the document not well formed. It is allowed in XML 1.1 but 1.1 is (to put it mildly) not as well deployed as XML 1.0. “Can someone tell me why they don’t use W3C standard for this?”

If you refer to #8 via a numeric reference as you suggest then it is a fatal error in XML 1.0, making the document not well formed. It is allowed in XML 1.1 but 1.1 is (to put it mildly) not as well deployed as XML 1.0.

]]> Comment on GB-0494 by David Carlisle http://www.dis29500.org/gb-0494/#comment-1255 David Carlisle Thu, 06 Dec 2007 11:21:18 +0000 http://www.dis29500.org/gb-0494/#comment-1255 [grrr half baked comment system on this site ate the end of my comment] .... only recognisable as html as it starts with <html and ends with /html, the whole data is really stuffed into private application specific comments and namespaced attributes and elements. [grrr half baked comment system on this site ate the end of my comment]

…. only recognisable as html as it starts with <html and ends with /html, the whole data is really stuffed into private application specific comments and namespaced attributes and elements.

]]> Comment on GB-0494 by David Carlisle http://www.dis29500.org/gb-0494/#comment-1254 David Carlisle Thu, 06 Dec 2007 11:17:58 +0000 http://www.dis29500.org/gb-0494/#comment-1254 "If MathML isn’t a drop-in replacement, but there’s significant overlap, extensions could be defined here or in an external standard." There is essentially no overlap between mathml and oomml: it isn't just a case of adding some extra attributes or changing some element names, it is structurally completely different. Going from oomml to mathml requires character-by-character parsing of text nodes. Murray would probably disagree with me (in fact I'm sure he would:-) but if you were just starting from scratch and wanted to encode mathematical expressions in XML you'd never end up with oomml. Frankly it's just too weird, but when looked at it context it doesn't look at all weird when embedded in an ooxml document, it just looks just like the rest, which is not unrelated to the fact that the editing interface for mathematics and other text is rather similar. It's perfectly valid to make an argument that said that ISO should just be standardising one thing (ODF/MathML) but if they are going to standardise two things, they may as well be two coherent document formats (ODF/MathML and ooxml/oomml) not force one of the formats to be a shotgun marriage of ooxml with mathml. The worst possible outcome would be that documents were saved with "extended" mathml which would end up being like an MS Office generated "web page" which is only recognisable as html as it starts with “If MathML isn’t a drop-in replacement, but there’s significant overlap, extensions could be defined here or in an external standard.”

There is essentially no overlap between mathml and oomml: it isn’t just a case of adding some extra attributes or changing some element names, it is structurally completely different.

Going from oomml to mathml requires character-by-character parsing of text nodes. Murray would probably disagree with me (in fact I’m sure he would:-) but if you were just starting from scratch and wanted to encode mathematical expressions in XML you’d never end up with oomml. Frankly it’s just too weird, but when looked at it context it doesn’t look at all weird when embedded in an ooxml document, it just looks just like the rest, which is not unrelated to the fact that the editing interface for mathematics and other text is rather similar.

It’s perfectly valid to make an argument that said that ISO should just be standardising one thing (ODF/MathML) but if they are going to standardise two things, they may as well be two coherent document formats (ODF/MathML and ooxml/oomml) not force one of the formats to be a shotgun marriage of ooxml with mathml. The worst possible outcome would be that documents were saved with “extended” mathml
which would end up being like an MS Office generated “web page” which is only recognisable as html as it starts with

]]> Comment on NZ-0009 by Jouko Holopainen http://www.dis29500.org/nz-0009/#comment-1253 Jouko Holopainen Thu, 06 Dec 2007 09:08:38 +0000 http://www.dis29500.org/nz-0009/#comment-1253 Does anybody know the correct links in the New Zealand comment? I think they might be: http://www.openmalaysiablog.com/2007/07/mathematically-.html and http://www.robweir.com/blog/2007/07/formula-for-failure.html but I do not know for sure. Does anybody know the correct links in the New Zealand comment?

I think they might be: http://www.openmalaysiablog.com/2007/07/mathematically-.html and http://www.robweir.com/blog/2007/07/formula-for-failure.html but I do not know for sure.

]]> Comment on US-0161 by Fred http://www.dis29500.org/us-0161/#comment-1252 Fred Thu, 06 Dec 2007 04:30:03 +0000 http://www.dis29500.org/us-0161/#comment-1252 Can someone tell me why they don't use W3C standard for this? There is 1 byte difference in length between: _x0008_ and  or even, &#x8; The difference is that the second will be parsed correctly. http://www.w3.org/TR/unicode-xml/ Can someone tell me why they don’t use W3C standard for this?

There is 1 byte difference in length between:

_x0008_

and



or even,

&#x8;

The difference is that the second will be parsed correctly.

http://www.w3.org/TR/unicode-xml/

]]> Comment on US-0161 by Alan Bell http://www.dis29500.org/us-0161/#comment-1251 Alan Bell Wed, 05 Dec 2007 23:36:00 +0000 http://www.dis29500.org/us-0161/#comment-1251 There are some WordPress preview plugins, I quite like this one http://dev.wp-plugins.org/wiki/LiveCommentPreview but it needs a bit of tweaking. I will probably add it tomorrow. There are some WordPress preview plugins, I quite like this one http://dev.wp-plugins.org/wiki/LiveCommentPreview but it needs a bit of tweaking. I will probably add it tomorrow.

]]>