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.
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 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: 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)
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.
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...
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.
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.
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.
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 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.
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.
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.
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
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.
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. :)
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)
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.
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)
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.
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.
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.