On 5/8/06, Chris Casciano <[EMAIL PROTECTED]> wrote:
- i'd name the file something different.. maybe mf-cheatsheet.pdf or
something.. don't want to lose it among the 2043820 other cheat sheets
people have been creating.
Good idea, but maybe call it uf-cheatsheet, to match the subject label
([uf
On May 8, 2006, at 3:28 PM, brian suda wrote:
Please have a look and let me know your feedback, i'm open to
suggestions - it is still a very early iteration so if you find
mistakes
let me know and i'll correct them. (There have been requests to make
this an HTML document, and i probably will
brian suda wrote:
One of the common questions when people are implementing microformats is
that they are not sure what properties are available and/or which are
required. The specs are pretty good about explaining what properties are
REQUIRED, OPTIONAL and their cardinality (0-1, 0-*, 1-*, once).
On 8 May 2006, at 21:10, brian suda wrote:
According to the hAtom spec:
Feed
a Feed element is identified by the class name hfeed
a Feed element represents the concept of an Atom feed
the Feed element is optional and, if missing, is assumed to be the
page
hAtom documents MAY have multiple Fee
Ah, very exciting, very nice. The only suggestion I have off the top of
my head is to make it more obvious where the uFs join together. Instead
of "(hCard)" maybe "+ hCard", with hCard being bold or something?
I like the fact to that you show the nesting of the elements of the
right hand side.
Thanks for the input, the faint grey boxes will probably disappear in
the next iteration. The grey boxes surround the adr property and
children, and the geo property and children. These are both their own
compound microformats... so if you have an address, you can use those
properties - same for ge
On 8 May 2006, at 20:28, brian suda wrote:
I have tried to combine both the specs and the chart to a single
'cheat
sheet' for all the common microformats. This is a single page document
that describes both elemental microformats (XFN, RelTag, etc) and
compound microformats.
Couple of quick o
One of the common questions when people are implementing microformats is
that they are not sure what properties are available and/or which are
required. The specs are pretty good about explaining what properties are
REQUIRED, OPTIONAL and their cardinality (0-1, 0-*, 1-*, once).
I know the Wiki al
