#microformats 2014-11-17

2014-11-17 UTC
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?
#
Loqi
Ok, I'll tell him that when I see him next
#
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.
#
Loqi
Ok, I'll tell him that when I see him next
#
tommorris
edited /gender-examples (+663) "adding OKCupid's new gender and sexuality options"
(view diff)
#
tommorris
ChiefRA: 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
#
tommorris
edited /gender-examples (+190) "/* discussion elsewhere */ adding some basic intro-to-trans links"
(view diff)
#
ChiefRA
tommorris I do that as we speak, I've created a second page non-linked in the main Wiki http://microformats.org/wiki/hlisting-duplicated-for-discussions only for related discussions and to step up to 1.0 version, to drop the "draft"
#
ChiefRA
please have a look if you wish, by comparison with the original hlisting page.
#
tommorris
ChiefRA: -draft might be a better page name. will move in a sec. ;)
#
tommorris
And I'd be less than keen on canonicalising any pre-mf2 specs.
#
ChiefRA
yeah :) the thing is we need to get ourselves a brainstorming discussion to finish this.
#
ChiefRA
can we setup such a thing?
#
ChiefRA
after 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.
#
ChiefRA
to be able to pass it on with the latest changes, to be implemneted in Google.
#
ChiefRA
as for now, there are a few ambiguities on the 1.0 draft which needs to be resolved.
#
tommorris
edited /hlisting (+21) "/* Examples in the Wild */ moving Emurse down"
(view diff)
#
ChiefRA
The 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.
#
tommorris
ChiefRA: do you want to go through the examples in the wild on hlisting to ensure they are up-to-date?
#
ChiefRA
they are not up-to-date anymore.
#
ChiefRA
I tried to open the Match.com example, without success, seems that this website hasn't been updated in a while.
#
ChiefRA
the 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.
#
ChiefRA
so there will be plenty of examples, at least from the Real Estate.
#
ChiefRA
what I need us to do, is to discuss and finish the existing ambiguities.
#
ChiefRA
Can we get toghether me, you tantek and other guys from here to finish this up?
#
ChiefRA
I mean do we have a way of schedule a meeting for this?
#
tommorris
ChiefRA: 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.
#
ChiefRA
tommorris 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.
#
ChiefRA
tommorris 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.
#
tommorris
ChiefRA: will have a look at the issues you've raised and try to devote some mental time to opining
#
ChiefRA
tommorris that's why I've asked you if you know a way to setup an on-line meeting to discuss all these problems.
#
ChiefRA
thanks :)
#
tommorris
ChiefRA: and also see if I can find time to implement hListing -> mf2 shim in mf2py
#
ChiefRA
It would be great, we definitely need a parser for hListing.
#
ChiefRA
tommorris where do you want me to place these issues?
#
ChiefRA
the ones I found so far.
#
tommorris
edited /hlisting (-66) "/* Examples in the Wild */ moving EveryCarListed down"
(view diff)
#
tommorris
ChiefRA: an issues page like hCard etc have.
#
tommorris
-issues is best for issues. -brainstorming is better for crazy ideas
#
ChiefRA
tommorris ok I'll place there the issues.
#
chiefra
edited /hlisting-issues (+482) "/* issues */ adding all the recent issues I've found"
(view diff)
#
tommorris
edited /rel-payment (+25) "/* See also */ rel-payment-issues"
(view diff)
#
tommorris
edited /payment-examples (+684) "adding section on bitcoin URL scheme and QR codes"
(view diff)
charl joined the channel
#
tommorris
edited /rel-payment-issues (+727) "rel deprecation"
(view diff)
#
tommorris
ChiefRA: 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.
#
tommorris
edited /hlisting (+72) "/* See also */ adding redlink to [[microformats-2]]-backed spec"
(view diff)
#
tommorris
edited /microformats2 (+16) "/* v2 vocabularies */ adding [[h-listing]]"
(view diff)
#
tommorris
edited /hlisting-issues (+295) "/* issues */ deprecate version"
(view diff)
#
tommorris
I can't yet seem to find an online microdata parser like there are for both microformats, microformats-2 and RDFa...
#
tommorris
Downloaded Mida, the Ruby microdata parser. Doesn't work.
#
tommorris
edited /listing-examples (+697) "adding Gumtree"
(view diff)
#
tommorris
edited /hlisting (-69) "/* Examples in the Wild */ moving ooyoo to past"
(view diff)
#
tommorris
edited /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)
alanpearce joined the channel
#
tommorris
edited /hlisting (+38) "/* Examples in the Wild */ dealtagger still live"
(view diff)
#
ChiefRA
tommorris ok. I'll add www.sothebysrealty.com as hListing examples.
#
tommorris
ChiefRA: I'm not seeing any hListings on the detail pages
#
tommorris
oh, wait, no on the search results page.
#
tommorris
yep, but the individual detail pages don't seem to have them
#
ChiefRA
it doesn't, I'm working on them :D
#
ChiefRA
so far, I'm perfecting the format. When it's ready, I'll implement it all over.
#
tommorris
edited /hlisting (+171) "/* Examples in the Wild */ adding SothebysRetail.com"
(view diff)
#
ChiefRA
:)
#
chiefra
edited /hlisting (+0) "/* Examples in the Wild */ - corrected the name"
(view diff)
#
tommorris
edited /hlisting-issues (+201) "/* 2014 */ HTML design principles"
(view diff)
#
ChiefRA
and there are a lot of Sothebys affiliates websites which have the same hListing, over 100 of them.
#
ChiefRA
so there are plenty of examples which will go LIVE with the latest format of hListing after we perfect it.
#
ChiefRA
I'll add the Christies Real Estate too, I've been implementing there too. Also, their affiliates have it.
#
tommorris
Good 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.
#
chiefra
edited /hlisting (+174) "/* Examples in the Wild */ - adding Christies Real Estate to examples"
(view diff)
#
ChiefRA
well, it's a lot to write, but I'll add first the problems then I'll go into detail of every one.
#
ChiefRA
tommorris we definitely need a parser/validator for hListing to indicate the possible implementation errors.
#
tommorris
That'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.
#
ChiefRA
tommorris 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...
#
tommorris
ChiefRA: sure, but current best practice with microformats is we define a microformat-2 and define backwards compatibility for it.
#
ChiefRA
and 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.
#
ChiefRA
ok, now I get it.
#
tommorris
the idea is that it makes it easier for parser implementers too.
#
ChiefRA
ok then :) we'll brainstorm that.
pfefferle, elux, TallTed, elux_ and tantek joined the channel
#
tommorris
edited /hlisting (+0) "/* Examples in the Wild */ netinstruments doesn't support hListing anymore"
(view diff)
#
tommorris
edited /hlisting (-209) "/* Examples in the Wild */ moving imovelweb.com.br down to past examples"
(view diff)
#
tommorris
edited /hlisting (-74) "/* Examples in the Wild */ transcontinental site is no more, the site it redirects to doesn't use hListing either"
(view diff)
alanpearce_ and alanpear_ joined the channel
#
tommorris
edited /hlisting (-111) "/* Examples in the Wild */ no more on Kelkoo"
(view diff)
#
tommorris
ChiefRA, 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.
#
tantek
tommorris: 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
#
Loqi
tantek: 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?
#
Loqi
tantek: 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.
#
tommorris
edited /Main_Page (-9) "/* Archived */ fixing link"
(view diff)
#
tantek
do 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
#
tommorris
ChiefRA says that Google are doing something with it, but I'm reasonably sure they aren't using it for rich snippets.
#
ChiefRA
tantek 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.
#
ChiefRA
I have plenty accounts that have this highlighted in Google Webmaster Tools.
#
ChiefRA
this wasn't happening before, so they do something with it for sure. I failed to determine what so far.
#
tommorris
ChiefRA: can you document that? should probably write some test data and reverse engineer Google's parser.
#
tantek
ChiefRA - can you upload screenshots of Google showing it in Google Webmaster Tools?
#
ChiefRA
tommorris I can do something even easier: I can ask one of them what's with it in WMT to get a straight answer.
#
ChiefRA
tantek, I can do that right now, hold on for 1 minute.
#
tantek
perhaps you could add it to microformats.org/wiki/hlisting-implementations ?
#
ChiefRA
no, because this is sensitive client data.
#
ChiefRA
I don't want it publicly listed.
#
ChiefRA
let me see what I can do to trim out any identifiable info and I'll see.
#
tantek
ok sorry
#
tantek
we really need some sort of public example
#
tommorris
if 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.
#
ChiefRA
I 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:
#
tommorris
implementation is a good first start. useful implementation is kinda the next step. ;)
#
ChiefRA
I 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
#
ChiefRA
once 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.
#
tommorris
ChiefRA: "implementation" in the context I was referring to it in my previous msg is parser.
#
tommorris
the cynic in me says that Google is probably pushing schema.org these days. :)
#
tantek
tommorris: it's inconsistent
#
ChiefRA
tommorris 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.
#
tantek
from all evidence there is still conflict inside Google
#
tantek
ChiefRA - independent of clarifying any actual format - the question is of *WHAT* Google supports *TODAY*
#
tantek
not what they *could* support - in terms of hListing
#
ChiefRA
tantek: I'll show you in a second that :)
#
tantek
any clarifications / improvements at this point should go into h-listing with microformats2
#
tantek
patching hListing is probably not worth the time at this point
#
tantek
unless you know of anyone else parsing it
#
ChiefRA
tantek: I politely disagree with you.
#
ChiefRA
that's because we need a format that is used "NOW" for the time being, and then on the future.
#
tommorris
tantek: earlier, I suggested that fixing the issues with hListing is best done by defining it in terms of backcompat with microformats2.
#
tantek
ChiefRA - 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
#
ChiefRA
this format is used now by Google so I wish to take advantage from it now. :)
#
tantek
ChiefRA - the point is that any changes you need are NOT used NOW
#
tantek
thus we might as well make those fixes in h-listing
#
tantek
tommorris: agreed
#
ChiefRA
will be if you help me finish them, as I will pass this on to the Google Team for enhancements of parsing them.
#
tantek
I think tommorris has the right idea
#
tantek
we should make the necessary improvements to h-listing
#
tantek
and then backport those to hListing
#
Loqi
I agree
#
ChiefRA
tantek 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
#
ChiefRA
tantek read please the message I've left through Loqi 15 mins ago here in this channel, to get what I'm saying.
#
Loqi
dude
#
ChiefRA
and that's only one of them.
#
ChiefRA
I 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. :)
#
tantek
ChiefRA it looks like you added them to http://microformats.org/wiki/hlisting-issues#issues is that correct?
#
ChiefRA
tantek correct.
#
tantek
just making sure - best would be if http://microformats.org/wiki/hlisting-issues#issues had the latest
#
tantek
thank you - that's a big help
#
tantek
agreed on timing and taking advantage of this
#
tantek
hopefully we can do a quick turn on h-listing and hListing
#
ChiefRA
yup. I hope that too.
#
tommorris
tantek: happy to set up an experimental branch of mf2py to work on it when I have some spare mental bandwidth.
#
ChiefRA
the 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)
#
ChiefRA
do you get my point now? :)
#
tantek
yes - real life examples are VERY important, for both microformats process and adoption like from Google
#
ChiefRA
tantek tommorris I'll invite you temporary into a new channel, please accept.
#
tantek
ChiefRA - also I'm on another telcon now and can't participate much
#
ChiefRA
no worries.
#
tantek
tommorris: since you have a good understanding of microformats2 - could you start http://microformats.org/wiki/h-listing - perhaps based on http://microformats.org/wiki/h-product ?
#
tantek
I believe they are similar enough that that shouldn't be too difficult, and we really should get something up there
#
tommorris
tantek: might be able to do so later.
#
ChiefRA
tommorris if you want to take a look at how Google sees hlisting let me know.
#
tantek
thanks much tommorris
#
ChiefRA
tantek: 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)
#
tantek
agreed - and that's a good goal - can you add that to hlisting-issues ?
#
ChiefRA
the last sentence?
#
tommorris
ChiefRA: 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.
#
ChiefRA
tantek tommorris ok, I'll add the last ones now on that page to have something to work on.
#
chiefra
edited /hlisting-issues (+1700) "/* issues */ - added more inconsistencies to bring hListing to a definitive form"
(view diff)
#
ChiefRA
tantek tommorris please have a look at the -issue list.
#
tantek
thank you ChiefRA
#
ChiefRA
tantek 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.
#
tommorris
ChiefRA: both me and tantek prefer async communication. :)
#
ChiefRA
tommorris :) 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)
#
tommorris
just edit away to your hearts content - I'm pretty adept at reading wiki-diffs.
#
ChiefRA
ok 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.
#
tommorris
ChiefRA: '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.
#
ChiefRA
tommorris 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.
#
ChiefRA
one 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.
#
ChiefRA
heads-up*
#
tommorris
hmm, that's odd. I'll change the dates back. shouldn't need to refer to them by date.
#
tantek
the dates should reflect when the issues were *first* raised
#
tommorris
if we do, we can give them IDs.
#
tantek
that's important - to know how "old" an issue is
#
tantek
regardless of refinement
#
ChiefRA
I just put 1 day before them, that's it.
#
tantek
can also add (Updated: YYYY-MM-DD) if necessary
#
tantek
but the date first raised should be kept
#
tommorris
edited /hlisting-issues (+0) "all were raised today - correct date"
(view diff)
#
ChiefRA
ok then.
#
tantek
feel free to cite a line in IRC for the date first raised also
#
tantek
since IRC logs are archived by date with # permalinks to statements
#
tantek
see /topic for logs
#
ChiefRA
Thanks. So far we're good with what we have.
#
ChiefRA
tantek 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.
#
tommorris
ChiefRA: yep, just edit it in nice atomic blobs and I'll revert anything I find tough then we can discuss it.
#
ChiefRA
thanks.
#
tommorris
ChiefRA: on wikis, https://en.wikipedia.org/wiki/Wikipedia:BRD works surprisingly well, especially if sane people are applying it. (so should work *better* on microformats.org than on wikipedia)
#
ChiefRA
tommorris interesting concept, I didn't used this before so I'll take a look and hope to manage it :)
#
ChiefRA
from now on, I'll try to perform all the changes within one modification, to be easier to follow.
#
ChiefRA
ok guys GTG, see you in 2 hours. was a nice an productive chat today :)
#
tommorris
ChiefRA: one atomic change - like, if you are doing one thing, do it in one change. :)
#
tommorris
I'll unpick the changes either way, but it makes my life easier.
#
ChiefRA
got it :) waiting for your changes then as mine were depleted so far :D
alanpearce, alanpearce_, uf-wiki-visitor, chiui, kez_, KartikPrabhu, eschnou and tantek joined the channel