- From: <bugzilla@wiggum.w3.org>
- Date: Wed, 17 May 2006 01:59:23 +0000
- To: public-i18n-its@w3.org
- CC:
http://www.w3.org/Bugs/Public/show_bug.cgi?id=3290
Summary: Introduction too "positive" and not enough informative
:)
Product: ITS
Version: LastCall
Platform: All
URL: http://www.w3.org/TR/2006/WD-its-20060414/#introduction
OS/Version: All
Status: NEW
Severity: normal
Priority: P2
Component: ITS tagset
AssignedTo: fsasaki@w3.org
ReportedBy: karl@w3.org
QAContact: public-i18n-its@w3.org
ITS says
[[[
This document defines a standard for high-quality, cost efficient
internationalization and localization of schemas and XML instances (both
existing ones and new ones).
]]]
We understand that it is the desires of the group but it doesn't mean that it
will be true. (We wish it will be). Just define what is it but do not emphasize
on the foreseen qualities ;)
Same comment than the abstract as well. Tend to avoid "This document", "The
document", just write about the topic, it will be lighter to read.
Again remove the reference to feedback, this is the status section not part of
the introduction which is about the technology itself.
Reading the first paragraph of Introduction, I still don't know what is it used
for. Is there a possibility of writing in one or two sentences what is it used
for in general use case? It is explained in 1.1 but could you make it one
sentence in the first paragraph that will be then developed further in 1.1
Example: "The ITS specification aims to provide different types of users with
information about what markup should be supported to enable worldwide use and
effective localization of content. "
Is very informatique and should be in the abstract and/or Introduction.
nitpicking: use "…" and not "..."
Received on Wednesday, 17 May 2006 01:59:44 UTC