jacquelinecreated /User:Jacqueline (+382) "New page: I would like to introduce myself to you, I am Darron but I do not like when folks use my whole identify.<br><br>What I appreciate performing is astronomy but I have been getting on new det..." (view diff)
gjonesThere is some interesting result for the h-entry where its picking up the value-pattern for u-url and u-uid, but I think that's, right u-x properties look for value-pattern first
tantekThere is no "hfeed" in the backward compat vocabs: http://microformats.org/wiki/uf2#v2_vocabularies because we don't know of any (significant?) consumers of "hfeed" in particular (lots of "hentry", but not "hfeed" itself)
tantekyou're not turning all "h***" into "h-***" are you? that would be bad as we don't want it to be arbitrary, just a short list of what's been well adopted.
tantekJonathanNeal - schema.org is a confusing mess. at least with data-vocabulary.org Google stuck with a few small vocabularies that it actually supports. whereas with #schema, it's a massive pile of crap with a few useful things buried in it.
tantekI'd say the spirit of Mark's book is a quick and useful overview, instead of pointing off into massive piles of crap (in fact, he makes fun of such massive piles of crap)
tantekso if anything, I'd say the best "future-proofing" for the microdata chapter is to add parallel microformats markup examples to each microdata example
JonathanNealWell, I'm up for the challenge, but I'm somewhat of a micro formats newbie. So I can branch it, make those additions, then have someone here review them for sanity.
tantekin contrast to GoogleBase, introduced in 2005, long abandoned (but got A LOT more press / popular shouting / blog posts at the time because, hey, it's GOOGLE, they can't possibly be wrong, right?)
JonathanNealThanks. How involved would you like to be? I'm still unsure how to respond to the ticket, but that's because of a lack of knowledge on my part.
tantekso that's the key I think, to doing a good job in maintaining this text - keep it simple, straightforward, purely useful - as that seems like Mark's intent, and to the reader's benefit.
tantekI'm happy to help with editing to see if there's a way to add parallel microformats markup examples to each microdata example while still keeping it short and useful.
Harzileintantek: well, currently i have no problem paying for my hosting. it's more what i'd like to recommend to people who say they have to choose between an unattractive ad and paying the publishing infrastructure out of their own pockets
Harzileinbut as an example, let's pretend my instance of killbills gets more popular than that of the author and i want to add ads: http://killbills.harzilein.eu.org
tantekit's tough to come up with good patterns for markup based on "let's pretend" examples, because in practice, the actual content + markup tends to differ A LOT from any theoretical / let's pretend examples.
Harzileinyeah, but the problem starts with _costs_. i would not like to use, say, goodrelations, because i'm not selling a product of "hiding ads", but just informing visitors about the costs i have, my visitor count, and the fact that certain parts of the page are "ad payload" and not content
Harzileinso let's concentrate on the fuzziest thing, the first ones are basically about making a 90's style hit counter and a "donation goal" like they have on wikipedia computer readable
Harzileintantek: so i guess it would be enough to add rel-payment indicating a page where i whine in prose about my server costs and tell people which html markup they should add to each page if they want to have ads shown ;)