PROPOSAL:
TRACK can be either plain text or marked up using HAUDIO.
This approach would make the following markup valid:
div class=haudio
...
span class=albumAlbum Title/span
...
span class=trackSong Name/span
...
/div
I love this!
It shouldn't work differently from hCalendar, and I
Andy,
At 12:44 05/10/2007, you wrote:
On Fri, October 5, 2007 11:20, Chris Newell wrote:
a new measurement microformat straw-man on the wiki:
http://microformats.org/wiki/measure-brainstorming#Straw_man
I guess you may have been through this but my first thought is why not
separate unit-code
Andy,
At 15:03 05/10/2007, you wrote:
On Fri, October 5, 2007 14:57, Chris Newell wrote:
Microformats put the burden, where possible, on parsers, not
publishers, in order to make life as easy as possible for publishers.
Agreed, but this is a balance. If it's hard to parse you'll get buggy
On Fri, October 5, 2007 15:31, Chris Newell wrote:
That would be:
abbr class=hmeasure title=2m22msup2/sup/abbr
using m2, or whatever is that standard for representing
square-metres.
Given that parsers must accept the formats includes [unit-code][number]
would:
span
On Fri, October 5, 2007 15:38, Chris Newell wrote:
If we applied a similar restriction to the measure strawman proposal
There is a separate thread for discussion of that proposal.
e.g.
[number][space][unit-code]
I would withdraw my concerns about the potential parsing problems.
People
Andy,
At 15:49 05/10/2007, you wrote:
On Fri, October 5, 2007 15:31, Chris Newell wrote:
That would be:
abbr class=hmeasure title=2m22msup2/sup/abbr
using m2, or whatever is that standard for representing
square-metres.
Given that parsers must accept the formats includes
Chris Newell wrote:
Note that I said or whatever is [the] standard for representing
square-metres.
I'm not sure there is a standard for representing the superscripts
used within SI units using plain text.
We may have to specify something.
These are all good discussions, but I'm afraid
Andy,
At 16:47 05/10/2007, you wrote:
I have put up Straw Man 2 on the
wiki in an attempt to outline basic markup that hmeasure could support:
http://microformats.org/wiki/measure-brainstorming#Straw_man_2
The Strawman includes the following new concepts:
- The proposal only uses abbr to avoid
On Fri, 2007-10-05 at 09:44 +0100, Julian Stahnke wrote:
PROPOSAL:
TRACK can be either plain text or marked up using HAUDIO.
This approach would make the following markup valid:
div class=haudio
...
span class=albumAlbum Title/span
...
span class=trackSong Name/span
...
Chris Newell wrote:
The Strawman includes the following new concepts:
- The proposal only uses abbr to avoid the but the parsers are going to
be so complicated! argument. Let's focus on what we can represent
using abbr - what we can support in span will naturally come out
of that
Martin McEvoy wrote:
On Fri, 2007-10-05 at 09:44 +0100, Julian Stahnke wrote:
So this simpler proposal makes perfect sense to me.
at least someone on the list Is starting to make sense.
Criticize the ideas, not the people, please. :)
I have been wrestling with the current proposal of
11 matches
Mail list logo
