[microformats-discuss] xFolk 0.4
bud at thecommunityengine.com
Mon Jul 11 05:18:24 PDT 2005
On Jul 11, 2005, at 2:56, Tantek Çelik wrote:
> This also means that microformat spec authors MUST be up front
> about the
> iterative and evolutionary nature of this process, and thus we have
> wording about a "work in progress" on the various microformat specs
> that are
> still be iterated on, *including* xFolk.
And I think we are doing just this with xFolk. You'll note that this
iteration brought to the fore the idea of adding the <img> element to
the spec which seems like it should happen. Sounds like rapid
iteration to me.
I am less thrilled by the idea of changing attribute values. Only
infrequently is there a real value-add from that. People all have
their view on what an attribute value should be. If you changed
every time, you would have as many attribute values as potential
So, the bottom line for right now is this:
1. The image element is going to come into a soon to be updated
element of the spec. Assume you can use it now with the same
semantics as the <a> element.
2. Eran, let me suggest that you and I chat in real time about the
comment issue. Usually, there is some html representation of the
content as well as the RSS feed, and it might help to consider that.
What would help here is a detailed use case. We could get on IRC
late in the day today or we could make another attempt by email.
3. I think we agree that the "taggedlink" issue can be tabled (left
as is) for now. Something that I would find compelling is the idea
that there is already a lot of usage, perhaps in a related community
around another value.
More information about the microformats-discuss