W3C home > Mailing lists > Public > whatwg@whatwg.org > December 2006

[whatwg] microformats incompatible with WebApps 1.0 ?

From: Michel Fortin <michel.fortin@michelf.com>
Date: Mon, 11 Dec 2006 21:18:29 -0500
Message-ID: <E8B32273-F840-45F7-BDD6-B08C1EE09B06@michelf.com>
Le 11 d?c. 2006 ? 20:37, Ian Hickson a ?crit :

> On Mon, 11 Dec 2006, Michel Fortin wrote:
>
>> I think we should keep both systems. Things worth registering in the
>> global namespace because they're common and not very likely to be
>> misused (like class names currently listed in the spec: example,  
>> issue,
>> note, warning, error, search, copyright), could be registered  
>> globally,
>> things which are more specialized would be registered more  
>> restrictively
>> under a profile.
>
> But we know that "profile" doesn't work.

Maybe we could arrange profiles so that they work better instead of  
scraping the concept altogether. Suggestion: we could allow the  
profile attribute on any element? The profile would apply only to the  
concerned element and its descendants. So this:

     <head profile="http://microformats.org/wiki/hcard-profile">
     ...
     <div class="vcard">
      <a class="url fn" href="http://tantek.com/">Tantek ?elik</a>
      <div class="org">Technorati</div>
     </div>

could become this:

     <div profile="http://microformats.org/wiki/hcard-profile"  
class="vcard">
      <a class="url fn" href="http://tantek.com/">Tantek ?elik</a>
      <div class="org">Technorati</div>
     </div>

That would solve the problem of having the profile far away from the  
actual data, which makes it difficult to copy paste and harder to see  
the link.

In addition, we could maintain a global registry of short names for  
profiles, so that we could write this as a shortcut:

     <div profile="hcard" class="vcard">
      <a class="url fn" href="http://tantek.com/">Tantek ?elik</a>
      <div class="org">Technorati</div>
     </div>

And since profiles can now be applied on individual elements, there's  
no real need to keep the redundant "vcard" class name since it could  
easily be implied by the profile being specified on that element:

     <div profile="hcard">
      <a class="url fn" href="http://tantek.com/">Tantek ?elik</a>
      <div class="org">Technorati</div>
     </div>

How is that?


>> What worries me most about the Wiki idea is that it'll make  
>> conformance
>> to HTML5 a moving target that would need to be reevaluated each  
>> time a
>> new class is added on the Wiki.
>
> How is this different from conformance to HTML5 + profile-specified
> extensions?

What's different is that you have to care about conformance only to  
the profile you're using, and no other. When new profiles are  
created, adding new classes and link types, you know they won't  
bother you.


Michel Fortin
michel.fortin at michelf.com
http://www.michelf.com/
Received on Monday, 11 December 2006 18:18:29 UTC

This archive was generated by hypermail 2.3.1 : Monday, 13 April 2015 23:08:31 UTC