W3C home > Mailing lists > Public > public-html-bugzilla@w3.org > August 2011

[Bug 13465] Implement datatyping in Microdata

From: <bugzilla@jessica.w3.org>
Date: Sun, 21 Aug 2011 23:00:42 +0000
To: public-html-bugzilla@w3.org
Message-Id: <E1QvH0U-0006pe-5P@jessica.w3.org>

--- Comment #7 from Aryeh Gregor <ayg@aryeh.name> 2011-08-21 23:00:41 UTC ---
(In reply to comment #6)
> This requirement places an unnecessary burden on Web authors, e.g. forcing
> those that author in imperial or metric units to the opposite method, as well
> as forcing how they express units of measurement counter to common cultural
> practices.

The vocabulary can define units itself by requiring that particular pieces of
information adhere to some format that includes a unit.  For instance, a piece
of information whose meaning is a length could be required to be a valid
floating-point number followed by optional whitespace followed by either "m" or
"ft", and be interpreted accordingly.

Since this is a common need, it would make sense for different vocabularies to
share parsing infrastructure.  For instance, someone might write a spec that
would define a syntax for lengths including units, with a specific set of
supported units, and an algorithm for converting any of these lengths to a
number of (say) meters.  Then different vocabularies that need a length unit
could refer to that spec for syntax and parsing requirements.

None of this requires support for units at the syntax level.  Syntactic support
just means that providing units is more cumbersome: instead of making them part
of the string where you give the quantity, as people are accustomed to, you
force authors to specify them separately.  You can solve the same problem more
simply by just allowing the vocabulary to define how to interpret the values.

> The resolution does not address my concern. The editor has responded in the
> same way in the past and there is no reason to believe that he will change his
> mind now. I do not plan to escalate this issue, but note that this is a bad
> design decision, IMHO.

You can add the keyword Disagree if you don't agree with the resolution but
don't want to escalate.

Configure bugmail: http://www.w3.org/Bugs/Public/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug.
Received on Sunday, 21 August 2011 23:00:43 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 20:02:01 UTC