In message [EMAIL PROTECTED], Tantek Çelik
[EMAIL PROTECTED] writes
Subject: Re: XFN usage stats and Re: [uf-discuss] rel=muse
implies romantic relationship?
Did you perhaps forget to change that?
microformats do not try to alter people's publishing behavior in an
unnatural way - and ask of
In message
[EMAIL PROTECTED], Frances
Berriman [EMAIL PROTECTED] writes
On 07/12/06, Andy Mabbett [EMAIL PROTECTED] wrote:
Both Mars and the Moon have been in the news this week:
Where are we, with the 'Mars':
http://microformats.org/wiki/mars
and 'Luna':
This policy makes it easier to have a page header without piling up
everything under section 1.. It gets ugly if it's done more than
once on a page though.
Regards, etc
David
On 12/11/06, Andy Mabbett [EMAIL PROTECTED] wrote:
The problem of misaligned section-edit links is caused by
using
In message [EMAIL PROTECTED],
David Janes [EMAIL PROTECTED] writes
On 12/11/06, Andy Mabbett [EMAIL PROTECTED] wrote:
The problem of misaligned section-edit links is caused by
using h[n] tags for headers, instead of the proper wiki markup (=,
== etc.).
[Please don't top-post]
This policy
Hello,
Why not use __NOTOC__ ?
See ya
On 12/11/06, David Janes [EMAIL PROTECTED] wrote:
This policy makes it easier to have a page header without piling up
everything under section 1.. It gets ugly if it's done more than
once on a page though.
Regards, etc
David
On 12/11/06, Andy
On 12/11/06, Charles Iliya Krempeaux [EMAIL PROTECTED] wrote:
Hello,
Why not use __NOTOC__ ?
Start a wiki page, keep it in edit mode (i.e. don't save) and play
with it. The current practice has its downfalls but seems to work
esthetically well, with the downside that you have to click one
On 12/11/06 12:27 PM, Charles Iliya Krempeaux [EMAIL PROTECTED]
wrote:
Hello,
Why not use __NOTOC__ ?
I believe __NOTOC__ simply blocks the TOC from appearing at all, unless I'm
mistaken.
Charles, could you elaborate on how you would use __NOTOC__ to solve this
problem of heading noise in
Hello Tantek,
You're correct, __NOTOC__ just blocks the TOC from appearing.
Re-reading what was originally posted I can see that it won't help
with this particular problem.
See ya
On 12/11/06, Tantek Çelik [EMAIL PROTECTED] wrote:
On 12/11/06 12:27 PM, Charles Iliya Krempeaux [EMAIL
On Dec 11, 2006, at 2:33 PM, David Janes wrote:
Start a wiki page, keep it in edit mode (i.e. don't save) and play
with it. The current practice has its downfalls but seems to work
esthetically well, with the downside that you have to click one down
to edit.
I just realized that this thread
In message [EMAIL PROTECTED], Tim
White [EMAIL PROTECTED] writes
Perhaps you missed this comment:
http://microformats.org/wiki?title=hresume-feedbackcurid=1777diff=0oldid=11198rcid=20574
in which a poster describes how he rejected hResume because it sought to
change his publishing
On Dec 11, 2006, at 11:46 AM, Tim White wrote:
Just notice that the How-to-edit help page [1] has some, um,
colorful content at the moment. Someone want to revert that?
[1] http://en.wikipedia.org/wiki/Wikipedia:How_to_edit_a_page
This isn't a wikipedia mailing list.
-ryan
Sorry that I'm coming in a bit late on this, but in looking at rel=muse
it's the only thing in the Microformat that is even close to applicable in a
wide variety of cases yet I am completely uncomfortable using it except for
in a few rare cases.
OTOH, I could use any of the following if attached
Chris Messina wrote:
The goal of this community is not to necessary act as a
filter, but to adhere to a process for coming to some kind of
consensus on a small number of formats that can be embedded
in ordinary web pages. We look at widespread existing
behavior and help massage that
On 12/11/06, Mike Schinkel [EMAIL PROTECTED] wrote:
Chris, are you aware that Ian Hickson and Lachan Hunt on the WHATWG list are
prescribing microformats as the generalized extension mechanism for HTML
(whenever anyone asks for a more generic extension mechanism?)
Mike, this isn't quite true.
Benjamin West wrote:
Mike, this isn't quite true. What's being prescribed are the
techniques. Techniques using mechanisms already available in HTML.
These are the same techniques that Microformateers apply to
well defined problems to create a microformat. But just
because microformats
Benjamin West wrote:
I'm not quite sure what you mean here. Is there a difference
between lowercase microformats and uppercase microformats?
lowercase microformats = unofficial semantic markup embedded in HTML
uppercase microformats = Official Microformat
--
-Mike Schinkel
Bruce D'Arcus wrote:
In a world in which one CAN consider adding alternative
attributes (HTML 5, etc.), it makes no sense to me one would
simply say no.
[I'm cross posting to uf-discuss and whatwg because Bruce's comment was made
on uf-discuss but I've made the same point on WHATWG.]
Bruce,
Tantek Çelik wrote:
3. Prefixing (e.g. vcard-) has already been considered and
rejected for microformats in general. There have been
deliberate exceptions made for one microformat (hAtom). I'm
not going to spend the time re-arguing this now - I have
added an item to my to-do list on the
On 12/11/06, Mike Schinkel [EMAIL PROTECTED] wrote:
Benjamin West wrote:
I'm not quite sure what you mean here. Is there a difference
between lowercase microformats and uppercase microformats?
lowercase microformats = unofficial semantic markup embedded in HTML
uppercase microformats =
On Dec 11, 2006, at 11:43 PM, [EMAIL PROTECTED] wrote:
Brian Suda wrote:
Microformats are meant as building blocks and they should be
able to be using independantly and together...
If that is true, how can it be achieved without a disambiguation
conventions
to keep official Microformats
Benjamin West wrote:
That's the first I've heard of this usage. I think what I'm
hearing (and agree with) is a need for a term that describes
the product of semantic markup techniques in a general way.
It's my usage. It seemed natural as I've heard the term uppercase/lowercase
used to
Ryan Cannon wrote:
If the community is slow to develop a format that makes
sense, we often encourage authors to develop their own
systems, which then can inform how a format will function in
the wild. This is where documentation and the oft-belabored
process becomes powerful. Although it
Also sprach Mike Schinkel:
I'm not quite sure what you mean here. Is there a difference
between lowercase microformats and uppercase microformats?
lowercase microformats = unofficial semantic markup embedded in HTML
uppercase microformats = Official Microformat
This makes sense to
23 matches
Mail list logo
