csarven, tlr, adactio, stereoket and Amorphous joined the channel
#auxif anybody needs a google+ account let me know. we get people invited from a loophole while invites are off..
sandbags, chiui, danbri, scor, nonge_, pere, ChiefRA and Askarii joined the channel
#ChiefRAguys, I need a little insight from you. Question is: how can I transform into microformats the "coverage area" for Real Estate business.
#ChiefRAOn international Real Estate offices, some offices can provide assistance in multiple languages: e.g. english, french, etc. and their coverage area (their area of Real Estate expertise) which usually is limited to several counties only, where they have properties for sale. For example: http://goo.gl/XhzrX this Real Estate Office is one of them.
#ChiefRAI've managed to adjust the spoken languages into microformats with the help of "value-title" subproperty of "note" (and placed the "lang" too, for browsers which do not support "value-title"), see the 1st highlighted line from here: http://pastebin.com/Vmf7Ubnh
#ChiefRAThe 2nd highlighted line is the coverage area I wish also to transform it into microformats, but I wish to have a meaning for search engines, not a simple note (which however, I cannot place it in the same way, because this violates the rule which sais that the parser should look only on the first non-whitespace child of the property element: http://microformats.org/wiki/value-class-pattern#Parsing_machine-data_value-title
#ChiefRAthe 2 available checking methods - Optimus: http://goo.gl/cDLW5 it shows both note subproperties: lang AND value-title
#ChiefRAGoogle Rich Snippets Tools: http://goo.gl/rtLjY interprets the correct "note" subproperty, on the footer, but it doesn't list it within the main extracted rich snippet data from the page
#ChiefRAHowever, I wish all these to have a true meaning within microfomats. I need to implement the microformats somehow on the coverage area. How do you suggest to do it? Thank you.
#singpolymaI'm not sure there is anything nearly specific to what you want
#singpolymayou could use rel-tag/"category" or something like that, but that's not quite right for this case maybe
#singpolymaofc you can use "note", but as you say that's not very semantic
#ChiefRAI've searched a lot through microformats.org website and I couldn't find anything like this.
#ChiefRAmaybe we need to suggest a new subproperty for this cases?
#ChiefRAas I'm sure there are a lot of offices not only in Real Estate businesses, which speak more than 1 lang, and have a more wide coverage area
#singpolymaright. you're looking for metadata about the office itself, which is a bit out of the scope of pure hCard
#ChiefRAyeah, has to be implemented within the hlisting in my case.
#ChiefRAbut ofc, the org hCard could include this as a subproperty and that will fix this issue.
#ChiefRAmaybe for languages spoken within a company we could create a subproperty named let's say languages-used
#ChiefRAand for the coverage areas, as well coverage-area
#ChiefRAtantek what do you say about my proposal? does it make any sense?
#singpolymawell, actually, lanugages *does* apply to all hCards, since both persons and orgs have lanugages they speak
#tantekthat is, links to real world websites which publish "languages spoken" information about a person or organization
#tantekby gathering those examples on a wiki page it makes it much easier to analyze them to figure out what if anything to add to existing microformats
#ChiefRAI've tried to cover tha languages spoken in this way:
#ChiefRAsingpolyma not with full power unfortunately
#ChiefRA"lang" class does not support the new 3 letter chars code to define languages (ISO 639-3), so the different langs should be abbreviated by using the 2 letter chars code ISO 639-1.
#ChiefRAI have documented myself a lot about it when I have to do some modifications on a website.
#ChiefRAas I can put one "note" subproperty for the description and the next one for languages as we speak. And when (if) we will add a new subproperty specifically designed to represent lang, I can change it.
#tantekChiefRA, you said "lots of websites are using HTML4 and they won't upgrade to HTML5" - do you have specific examples or at least some citations of that? That would be very interesting to document.
#ChiefRAto fix at least major problems that appear, and only then, we might think to upgrade.
#ChiefRAin the mean time, we have to work with HTML4 and to make things batter from this level e.g. adding microformats to become better strutured is an important step.
#tantekI was simply wondering if you had specific examples of websites that you work with or you've read about that said they have to stick with HTML4 for now.
#tantekThat would be very interesting to document.
#singpolymaChiefRA: all it normally takes to "switch to HTML5" is changing the doctype, since it's almost backwards compatible
#singpolymaalmost means I'm not confident enough to bother saying 100%. I've never seen an issue, since browsers just ignore the doctype in practise anyway
#singpolymahober: between 2 modes? right. sorry. "ignore" was strong
#singpolymaI have actually started using HTML5 tags (<section>, <aside>, <header>) on some client sites that declare as some other doctype, because their sites are hopelessly malformed anyway
#singpolymano. I just said, I do it on sites that are just tag soup anyway :P
iwaim joined the channel
#ChiefRA:) then it doesn't matter. I am trying to be as close as possible to 100 % validation. I myself swhich from HTML to XHTML sometimes as it is required
#ChiefRAOK I've put 3 "note" subproperties to have all the info in there, Optimus validates it with no problem http://goo.gl/cDLW5 Google as well http://goo.gl/rtLjY :)
#tantekedited /html5 (+224) "Issue: Some websites are not ready to upgrade to HTML5 - noted example by ChiefRA in IRC" (view diff)
#tantekChiefRA - not sure what you mean by coverage area - would need to see an example URL
#tantekChiefRA - btw, in general we've been getting away from subproperties in microformats
#tantekit turns out they're harder to use/understand
#tantekand most of the time unnecessary (to be sub)
#tantekin the case of language preferences or speaking - those could just be direct properties of an hCard
#tantekyou can include them inside the "note" if you wish no problem
#tantekbut that doesn't make them into subproperties - they can just be normal properties
#ChiefRAa Real Estate Office have a coverage area, a "doing business" area
#ChiefRAthey sell Real Estate properties only in those designated areas.
#ChiefRAthat's for real estate. But discussing this on a more general approach, almost every business company has a specific area in which it's doing business.
#tantekChiefRA - take a look at how the languages-spoken pages were written up very minimally and quickly - and do the same thing for coverage-area and coverage-area-examples
#chiefracreated /coverage-area-examples (+264) "New page: This page arised from the need of marking up with microformats the coverage areas in which Organizations (and not only) are doing business. They have a designated specific place or a numbe..." (view diff)
#tantekit will only take you a few minutes - just like what singpolyma and I just did for languages-spoken (see above)
#ChiefRAI'll add examples as soon as I get them, because I must search for specific businesses in Google Places to add them there. In the mean time, I'll ad my site as an example for spoken languages.
#tantekedited /xfn-brainstorming (+351) "/* fans and followers */ we're ready for rel=follower and rel=following - invitation for people to start writing these up" (view diff)