[uf-discuss] RFC: Proposal for general purpose microformat

[Ryan King]

On Dec 2, 2005, at 11:39 AM, Abramo Bagnara wrote:

> Ryan King ha scritto:
>> I think you're missing the part where many of us believe that
>> "arbitrary representation" is desirable. You've recreated the  
>> Tower  of
>> Babel problem in xhtml [http://tantek.com/log/
>> 2005/07.html#towerofbabelproblem].
>
> I've read that, I don't see how it's pertinent: no tags and/or
> attributes are created.

I was just trying to make the point that allowing arbitrary xml  
embedding doesn't solve any semantics problems, just creates new ones.

> Indeed my proposal is simply a simplification/generalization of
> hCalendar and hCard using a very similar approach, but allowing to
> specify in a simple way source and destination of data.
>
> The benefits I see wrt current hCalendar are:
> - generality

This may be in opposition to the way we develop µF's. As the first µF  
principle states: "solved a specific problem."

> - simplicity and readability (without have to know the complex  
> rules of
> hCalendar describing where the data might be located)

IMHO, your rendition is no easier to read than hcalendar. Of course,  
I'm very familiar with hcalendar, so I may be biased.

> - no overlapping with class name in use by consolidated css

True. However, you do realize that using colons in class names will  
not work well with css (with current useragents, at least, I'm not  
sure exactly where the spec is on this)?

>> Why not propose a fix to hcalendar, rather than starting from  
>> scratch?
>
> My proposal is exactly oriented toward this, to improve current
> hCalendar (as you can see the similarity between the two are much many
> than the differences...)

It just seemed that you'd thrown out more than neccesary. Your stated  
objective was to fixed the cases of encoding iCalendar parameters in  
hcalendar (I think. I'm honestly not sure what part of the format  
you're trying to fix.). Why not just focus on that part of the format?

> I've never thought to start from scratch, I've started copying
> hcalendar, analyzing its current shortcomings and I've humbly  
> proposed a
> solution (standing on the giant's shoulder...)
>
> I feel a subtle hostility wrt this improvement attempt, I'm wrong?

Just disagreement.

-ryan
--
Ryan King
ryan at technorati.com