tantek, tantek-ipod, lgedeon and gp5st joined the channel
#gp5sti'm looking at the schema.org and microformats.org geo definitions, there is not (optional) field for planet or body. what would be the proper way to go about proposing that?
#aaronpk:) I was wondering how long it would take for someone to ask that
#gp5sti run a site about mars and thought that microformats would be useful. i hate the idea of just augmenting the standard on my own site. the other option is just for people to assume that any coordinates are about mars, but in theory they could be for other bodies (planet, moon, asteroid)
kennyluck, teleject and kennyluck_ joined the channel
#columbuswoodallcreated /index.php?title=Mediawiki (+3287) "New page: Look at the Email : You will be informed by the bureaus with their analysis outcomes through mail. They're going to notify you should the product ended up being validated or removed. Cont..." (view diff)
#tantekalso: re: Google and uf2, not yet as far as I know. we don't usually find out until after they start supporting something.
#tantekbtw have you tried using microformats2 yourself with any of your markup to see how easy or hard it is to add to your existing markup?
#tantekbarnabywalters - I was looking at your home page to see how you marked up your stream, and checking out the hAtom, when I noticed this: </p><p>16:22:05</time></p>
#tantekit appears you may have some unbalanced / overlapping open/close p tags!
#tantekand also, for the hAtom, you'll need to put the published updated class names on the actual time element, not on the surrounding div
#tantekonce you've gotten all that taken care of, I have some questions for you about your experience with microformats, and in particular with h-entry (if you've taken a look at it)
#barnabywalterstantek: weird coincidence, I am currently going through all my new markup and applying mf2 to it in a more intelligent way
#tantekmy experience with it so far is that it seems like some of the class names are either redundant with existing microformats2 class names or unnecessary
#tanteknote that I mapped h-entry directly from hAtom hentry as a first attempt
#barnabywaltersgive me a sec, I'll push my latest changes to my test server
#barnabywalterstantek: which h-entry class names have you found to be redundant?
#tantekedited /microformats2 (+575) "/* h-entry */ capturing some issues and opportunities for simplification, fewer overall class names" (view diff)
#tantekthere, finally hit save on a page I was editing last night and fell asleep before saving apparently
#barnabywaltersplus for notes where the content *is* the title, the result is rather ridiculous: entry-content entry-title p-entry-title p-entry-content p-entry-summary
#tantekinitially we mapped the Atom spec's exact semantics for entry title, summary, content to hAtom
#tantekwell, almost - you can omit the *-summary in that case :)
#tantekso with hAtom for notes you have: entry-title entry-content
#tantekfor h-entry, I'm trying to simplify this to: p-name e-content