microformats2-issues: Difference between revisions
Jump to navigation
Jump to search
(subheads, Reserve historically overloaded terms) |
(-) |
||
| Line 18: | Line 18: | ||
</div> | </div> | ||
=== | === RFC2119 === | ||
2015-03-09: | 2015-03-09: | ||
* Normatively reference RFC2119 in microformats2 specs, based on IRC discussion [http://logs.glob.uno/?c=freenode%23microformats&s=today#c78043] | * Normatively reference RFC2119 in microformats2 specs, based on IRC discussion [http://logs.glob.uno/?c=freenode%23microformats&s=today#c78043] | ||
Revision as of 16:23, 21 October 2015
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
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:
- 'type'
- 'id'
- ... any other suggestions?
Thoughts?
- ...
RFC2119
2015-03-09:
- Normatively reference RFC2119 in microformats2 specs, based on IRC discussion [1]
- in microformats2
- in microformats2-parsing
- in microformats2 vocabularies (if necessary), e.g. h-card, h-entry, h-event, etc.
Thoughts?
- +1 Tantek seems reasonable.
- ...