This article is a stub. You can help the microformats.org wiki by expanding it.
Issues relating to the overall definition of microformats2.
For parsing issues in particular, see microformats2-parsing-issues
Reserve historically overloaded terms
2015-10-21 raised by Tantek microformats2 should reserve historically overloaded generic terms to discourage vocabulary designers from shooting themselves in the foot in terms of overloading, ambiguity, implied specificity, etc. E.g. these property names should be reserved:
- 'value' - already has special meaning e.g. Value Class Pattern
- ... any other suggestions?
- Normatively reference RFC2119 in microformats2 specs, based on IRC discussion 
- +1 Tantek seems reasonable.