Fol­lo­wing Tho­mas Linard’s advice, I put some micro­for­mats in my résumé (I took advan­tage of the oppor­tu­nity to move to acces­si­bi­lité Or[1]). I’m tal­king about hre­sume, and here I will...

Fol­lo­wing Tho­mas Linard’s advice, I put some micro­for­mats in my résumé (I took advan­tage of the oppor­tu­nity to move to acces­si­bi­lité Or^[1]). I’m tal­king about hre­sume, and here I will point out what poses me pro­blems in this other­wise inter­es­ting initiative.

First of, you shall know hre­sume has only hit the 0.1 miles­tone. Thus, it is nor­mal that a lot of things are missing.

• Inter­na­tio­na­li­sa­tion: should the micro-formats be in plain English (class="type" cell) or loca­li­sed (class="type" mobile). (FR:(téléphone) portable → cell)
• For­mat­ting: I could not find any gui­de­line for for­mat­ting phone num­bers. Should it be man­da­tory to for­mat it in one way (more com­pel­ling, but less of a hassle for date ana­ly­sis) or shall it accept dif­ferent inputs (with all the bur­den of her­me­neu­tics or what did he wan­ted to say? +33662489335, +33 6 62 48 93 35, +33 6 62 48 93 35 (unbreakable spaces), +33.6.62.48.93.35, +33-6-62-48-93-35, 06 62 48 93 35, (0)6 62 48 93 35?
• class and id: it is pos­sible to use id when example give class (pro­vi­ded there is only one occu­rence of the id, of course)? Are micro­for­mats depen­dant on the pro­perty or the value (I hope the latter)?

That is all for now, I will post any other thing I can think about.

1. Save for abbre­via­tions, where some tech­ni­cal pro­blems occur bet­ween Or and XHTML 1.1 rela­tive to abbre­via­tions, but WHATWG is wor­king on it.