KartikPrabhu, Rastus_Vernon, tantek, kez, ChiefRA, pfefferle, chiui, eschnou and pfefferle_ joined the channel
#ChiefRA!tell tantek I just realized one of the main obstacles for hListing usage is the lack of implementation examples (real in-code implementation) for the 2-words properties. ex. "item info": which tag should encapsulate all the details like (fn || url || photo || geo || adr) | hCard?
#ChiefRA!tell tantek Should it be exactly class="item info" OR class="item-info". This needs to be defined as it has to keep within all the details of the item.
#tommorrisChiefRA: you might want to document that on the wiki. ideally, we'd be able to work out canonical mappings from hListing -> h-listing (mf2) -> json
#ChiefRAafter we finish the 1.0 we can move out to canonicalising it to mf2, but for now, Google started to support the hListing, that's why I'm so keen to finish up this version.
#ChiefRAto be able to pass it on with the latest changes, to be implemneted in Google.
#ChiefRAas for now, there are a few ambiguities on the 1.0 draft which needs to be resolved.
#ChiefRAThe thing is, I will give them not only the 1.0 (definitive version) but also real-life examples of websites which are ALREADY using this version.
#tommorrisChiefRA: do you want to go through the examples in the wild on hlisting to ensure they are up-to-date?
#ChiefRAI tried to open the Match.com example, without success, seems that this website hasn't been updated in a while.
#ChiefRAthe thing is, I'll provide enough examples at the end :) As I'll be implementing it within our websites in a matter of days after we finish.
#ChiefRAso there will be plenty of examples, at least from the Real Estate.
#ChiefRAwhat I need us to do, is to discuss and finish the existing ambiguities.
#ChiefRACan we get toghether me, you tantek and other guys from here to finish this up?
#ChiefRAI mean do we have a way of schedule a meeting for this?
#tommorrisChiefRA: do start documenting examples. I haven't looked at the issues raised in the spec, but if we can see how people are using hListing in practice, that can guide discussions around the issues.
#ChiefRAtommorris I already did that fpr the past 2 years. That's why I'd like to discuss this. I'm one of the users who do use hListing a lot within Real Estate and I'd like to rezolve the aforementioned issues.
#ChiefRAtommorris I kept a close eye on this matter and I've reached several conclusions, one of the is that the specs are ambiguous that's why people refrain from implementing it, this needs to be discussed.
#tommorrisChiefRA: will have a look at the issues you've raised and try to devote some mental time to opining
#ChiefRAtommorris that's why I've asked you if you know a way to setup an on-line meeting to discuss all these problems.
#tommorrisChiefRA: rel-payment-issues now includes an issue suggesting we ought to deprecate rel-payment and replace it with a u-payment class, and suggesting we could integrate this into a future h-listing spec. this may be of interest.
#tommorrisedited /hlisting (-130) "/* Examples in the Wild */ realestate.com (or, specifically, realestate.foreclosures.com which is the only bit of the site that has listings) does not have hListings anymore" (view diff)
#ChiefRAI'll add the Christies Real Estate too, I've been implementing there too. Also, their affiliates have it.
#tommorrisGood work. In the -issues page, it'd help if you could make reference to particular sites and markup examples where you have faced particular issues.
#chiefraedited /hlisting (+174) "/* Examples in the Wild */ - adding Christies Real Estate to examples" (view diff)
#ChiefRAwell, it's a lot to write, but I'll add first the problems then I'll go into detail of every one.
#ChiefRAtommorris we definitely need a parser/validator for hListing to indicate the possible implementation errors.
#tommorrisThat's why I want to build an initial mapping to microformats-2 and a preliminary candidate microformats-2 schema so I can implement both in mf2py.
#ChiefRAtommorris the thing is h-Listing (mf2 version) I don't think it will be supported by Google... as far as I've asked them about the rest of mf2 and they said they didn't add support for any of them...
#tommorrisChiefRA: sure, but current best practice with microformats is we define a microformat-2 and define backwards compatibility for it.
#ChiefRAand they don't have any plans in this regard... so based on this statement, I would only worry about the v.1 of those that are already supported.
pfefferle, elux, TallTed, elux_ and tantek joined the channel
#tommorrisedited /hlisting (+0) "/* Examples in the Wild */ netinstruments doesn't support hListing anymore" (view diff)
#tommorrisedited /hlisting (-209) "/* Examples in the Wild */ moving imovelweb.com.br down to past examples" (view diff)
#tommorrisedited /hlisting (-74) "/* Examples in the Wild */ transcontinental site is no more, the site it redirects to doesn't use hListing either" (view diff)
#tommorrisChiefRA, tantek: there we go, got the Examples in the Wild section tamed. This is rather depressing. I'm almost tempted to say that hListing is a failed microformat.
#tantektommorris: the only reason we'd *not* consider it failed is if there is evidence that there is at least one major consumer out there (Google, or other search engines) that does *something* predictable with it
#Loqitantek: ChiefRA left you a message 5 hours, 49 minutes ago: I just realized one of the main obstacles for hListing usage is the lack of implementation examples (real in-code implementation) for the 2-words properties. ex. "item info": which tag should encapsulate all the details like (fn || url || photo || geo || adr) | hCard?
#Loqitantek: ChiefRA left you a message 5 hours, 47 minutes ago: Should it be exactly class="item info" OR class="item-info". This needs to be defined as it has to keep within all the details of the item.
#tantekdo we have any evidence that any of the hListing examples in the wild are actually showing up with rich snippets in Google?
eschnou joined the channel
#tommorrisChiefRA says that Google are doing something with it, but I'm reasonably sure they aren't using it for rich snippets.
#ChiefRAtantek tommorris they showing it in their Google Webmaster Tools on the Structured Markup Data AND the syntax can be verified in their Rich Snippets Tools.
#ChiefRAI have plenty accounts that have this highlighted in Google Webmaster Tools.
#ChiefRAthis wasn't happening before, so they do something with it for sure. I failed to determine what so far.
#tommorrisChiefRA: can you document that? should probably write some test data and reverse engineer Google's parser.
#tantekChiefRA - can you upload screenshots of Google showing it in Google Webmaster Tools?
#ChiefRAtommorris I can do something even easier: I can ask one of them what's with it in WMT to get a straight answer.
#ChiefRAtantek, I can do that right now, hold on for 1 minute.
#tantekperhaps you could add it to microformats.org/wiki/hlisting-implementations ?
#ChiefRAno, because this is sensitive client data.
#tommorrisif you can make the page less sensitive and put it up on an example site (github etc.) then see how that looks in Google's tools, that'd be useful.
#ChiefRAI have posted public examples but only for implementation... so far, I couldn't identify any USE of it, but what I'm saying is this:
#tommorrisimplementation is a good first start. useful implementation is kinda the next step. ;)
#ChiefRAI have implemented it in big websites like Sothebys and Christies (see the examples I've posted today in the hListing examples). I need to be able to finish this draft to get full benefits from it.
alanpearce joined the channel
#ChiefRAonce we're finished with it and we have all the problems sorted out, I'll be passing this on to Google Team in charge with this, to forther improve their search engine to better recognize this hListing format.
#tommorrisChiefRA: "implementation" in the context I was referring to it in my previous msg is parser.
#tommorristhe cynic in me says that Google is probably pushing schema.org these days. :)
#ChiefRAtommorris I was referring to clarify the actual format a bit, you know what we discussed earlier today, to be able to improve and take full advantage of all properties of the hListing.
#tantekfrom all evidence there is still conflict inside Google
#tantekChiefRA - independent of clarifying any actual format - the question is of *WHAT* Google supports *TODAY*
#tanteknot what they *could* support - in terms of hListing
#ChiefRAthat's because we need a format that is used "NOW" for the time being, and then on the future.
#tommorristantek: earlier, I suggested that fixing the issues with hListing is best done by defining it in terms of backcompat with microformats2.
#tantekChiefRA - the special case rules for specific classic microformats are not worth maintaining - better to freeze them at their *current* level of implementation (parsing), and then put work into h-listing
#ChiefRAthis format is used now by Google so I wish to take advantage from it now. :)
#tantekChiefRA - the point is that any changes you need are NOT used NOW
#tantekthus we might as well make those fixes in h-listing
#ChiefRAtantek there are a few things not clear now with hListing. Agree to improve and create the h-Listing, but let's clear the missing points now for the existing format, BEFORE enhancing it.
mko joined the channel
#ChiefRAtantek read please the message I've left through Loqi 15 mins ago here in this channel, to get what I'm saying.
#ChiefRAI mean I have the capability to improve this microformat and I have the connections now to promote it faster into Google's active search results. All I'm saying is to take advantage of this. :)
#tommorristantek: happy to set up an experimental branch of mf2py to work on it when I have some spare mental bandwidth.
#ChiefRAthe thing is that Google relies also on real life examples, and I can provide hundreds of them as of now (one week to implement the last versions of it)
#ChiefRAtantek: if we're able to fix the missing parts of hlisting as fast as we can (no need of adding new features or smth like this) we will be able to have one more microformat complete and working format to compete the schema.org (beside hCard and the rest)
#tantekagreed - and that's a good goal - can you add that to hlisting-issues ?
#tommorrisChiefRA: pop in as many issues as you can think of with as much documentation/examples as you can. I may try today and draft h-listing tonight so the more issues I have to work with, the better.
#ChiefRAtantek tommorris ok, I'll add the last ones now on that page to have something to work on.
#chiefraedited /hlisting-issues (+1700) "/* issues */ - added more inconsistencies to bring hListing to a definitive form" (view diff)
#ChiefRAtantek tommorris please have a look at the -issue list.
#ChiefRAtantek my pleasure. We should setup a date to talk about all of these and definitivate them. I can do it even today if both of you agree.
#tommorrisChiefRA: both me and tantek prefer async communication. :)
#ChiefRAtommorris :) haha, ok :P we can do it this way then. Do you accept to do that by modifying the temporary page created specifically for this? The http://microformats.org/wiki/hlisting-duplicated-for-discussions (and would it be better to understrike |if possible| the text you wish to remove so for the others to see what has been removed)
#tommorrisjust edit away to your hearts content - I'm pretty adept at reading wiki-diffs.
#ChiefRAok then please tell me where I can find the Wiki Diffs for this particular page. I'll work your way as probably is agreed by tantek also.
#tommorrisChiefRA: 'history' at the top of the page. it shows a list of all the edits. can diff edits against each other. basically, for each issue, if you come up with a solution, try to put that all in one particular edit to the wiki, so we can evaluate each one separately.
#ChiefRAtommorris great thing, thanks. I've added all the problems I came uppon on for it, so now the -issues page is complete from my POV.
#ChiefRAone hads-up, I've modified the date on which these issues were added to be able to differentiate between them if later need to reffer to them in particular.
#ChiefRAThanks. So far we're good with what we have.
#ChiefRAtantek tommorris: what I wish from you guys, beside seeing the issues I've raised, is to parse by comparison the actual and the temporary hlisting page to view all the modifications I've done on the temporary page and make the neccesarry adjustments you see fit.
#tommorrisChiefRA: yep, just edit it in nice atomic blobs and I'll revert anything I find tough then we can discuss it.