From info at csarven.ca Tue Apr 6 14:23:16 2010 From: info at csarven.ca (Sarven Capadisli) Date: Tue Apr 6 15:16:45 2010 Subject: [uf-discuss] Level of rel=contact Message-ID: <1270588996.2680.152.camel@csarven-laptop> A little bit of semantics. http://gmpg.org/xfn/11#contact says "contact: Someone you know how to get in touch with. Often symmetric." I'm thinking that rel="contact" is generally attributed to someone that we have at least a "lowest form of friendship" with. It would also be someone that we don't dislike e.g., blackhat SEO expert. Additionally, if the user doesn't have control over the declaration of such relationship, wouldn't it be more meaningful and safer to exclude this bit of information in the output? The example I had in mind was 'Subscribers list' at http://identi.ca/csarven What do you think? I've found http://microformats.org/wiki/xfn-clarifications#is_contact_a_better_lowest_common_denominator but is this better documented elsewhere? -Sarven From singpolyma at singpolyma.net Tue Apr 6 15:47:19 2010 From: singpolyma at singpolyma.net (Stephen Paul Weber) Date: Tue Apr 6 15:46:44 2010 Subject: [uf-discuss] Level of rel=contact In-Reply-To: <1270588996.2680.152.camel@csarven-laptop> References: <1270588996.2680.152.camel@csarven-laptop> Message-ID: <20100406224719.GA12151@mediacentre> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 Somebody claiming to be Sarven Capadisli wrote: > The example I had in mind was 'Subscribers list' at > http://identi.ca/csarven As I said in IRC, I think followers are rev=contact I know some people don't like rev. Those people can be crazy and use rel=has-me-as-contact... I think rev is fine. - -- Stephen Paul Weber, @singpolyma Please see for how I prefer to be contacted. edition right joseph -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.9 (GNU/Linux) iQIcBAEBCAAGBQJLu7n2AAoJENEcKRHOUZzeF2YQAK2f/L6Jux/G04O/emJNHGoH WK+N1jiMhzQBlRlYrzQBrKnpCShwyV/JhVTmIOn36qCqfhQyeHBlRhTToZP97C5/ 9n0R+PssBbdrMMWycQgiJnmtEulqrWcipnoIFaXtBhkSQcjtD79U9NpDSfwPS/8S 5fcIXKPOxUaECDjHwKtKyZ03nHxPFECzJLl0h93axWu1u0qNPGV3oo6z+3/eK+1E Nv+o8i/fEpvPnziZDsvVmw+SziU29IybvqxKk3CAvQPUadePd9WTJAi5bOsCPqms XMIm1gxAUcENvJCkYJqCmy/Dh7p7OgeHKzfqWYglewGwr8N+ihMR1WwN1Wz0Fih6 uJph6z8YgAyGZCh4505k2NEXlcteM+O7CSfjfLSK0iLoFzLAeMDzP6SM4CpbifKK AluVu6mxvcnkpJAGyX1h/zbUCcxiWQmpRSH9Us3zz2GevjNdxD5kDBVA2iVNG6RG ueoeSUoHqQCbNclF8WL9MCVo9pH+++mcahvmoStQsxke/JA2GqSdG+Hld1PzfbKp vvQv+cOjWz1Dc9SUZERSzxjsq2LFAO6IPAUxxtPUgBGVmDMt7NwwAEB+zKjXEb5m 2ne+O/nwNnEq99oK2AOfuyTEX1JtilFsldPrdmqvZ/Xebwy7sibcPQ0XSKsSL6X6 RPUgs6bQRR/jsJCAeD7R =SSLk -----END PGP SIGNATURE----- From brian.suda at gmail.com Tue Apr 6 15:48:12 2010 From: brian.suda at gmail.com (Brian Suda) Date: Tue Apr 6 15:48:16 2010 Subject: [uf-discuss] Level of rel=contact In-Reply-To: <1270588996.2680.152.camel@csarven-laptop> References: <1270588996.2680.152.camel@csarven-laptop> Message-ID: On Tue, Apr 6, 2010 at 9:23 PM, Sarven Capadisli wrote: > I'm thinking that rel="contact" is generally attributed to someone that > we have at least a "lowest form of friendship" with. [...] > Additionally, > if the user doesn't have control over the declaration of such > relationship, wouldn't it be more meaningful and safer to exclude this > bit of information in the output? --- You lost me on "exclude this", exclude what exactly? rel=contact isn't symmetrical, so you might be my contact, but i'm not yours. I can't control what you declare about me. > The example I had in mind was 'Subscribers list' at > http://identi.ca/csarven --- if you are subscribing to someone, then it probably at minimum meets the definition of: someone that we have at least a "lowest form of friendship" Are you suggesting it isn't and we should exclude it? -brian -- brian suda http://suda.co.uk From info at csarven.ca Tue Apr 6 17:02:29 2010 From: info at csarven.ca (Sarven Capadisli) Date: Tue Apr 6 17:02:38 2010 Subject: [uf-discuss] Level of rel=contact In-Reply-To: References: <1270588996.2680.152.camel@csarven-laptop> Message-ID: <1270598549.2680.173.camel@csarven-laptop> On Tue, 2010-04-06 at 22:48 +0000, Brian Suda wrote: > On Tue, Apr 6, 2010 at 9:23 PM, Sarven Capadisli wrote: > > I'm thinking that rel="contact" is generally attributed to someone that > > we have at least a "lowest form of friendship" with. [...] > > Additionally, > > if the user doesn't have control over the declaration of such > > relationship, wouldn't it be more meaningful and safer to exclude this > > bit of information in the output? > > --- You lost me on "exclude this", exclude what exactly? My bad. My reference was to the example. > rel=contact > isn't symmetrical, so you might be my contact, but i'm not yours. I > can't control what you declare about me. That's exactly the case I was working with. > > The example I had in mind was 'Subscribers list' at > > http://identi.ca/csarven > > --- if you are subscribing to someone, then it probably at minimum > meets the definition of: someone that we have at least a "lowest form > of friendship" > > Are you suggesting it isn't and we should exclude it? No, I'll clarify. What I was trying to say was that, if I have a profile page where it lists a bunch of people that are subscribed to me, I wouldn't necessarily call them my contact since I don't really know them. Hence, in my example at http://identi.ca/csarven , rel=contact should be removed from Subscribers list. I agree that rev="contact" makes more sense here, but, I'm focused on the incorrect use of rel="contact". rel=contact is/should be reserved for people that meets the basic requirement of that "lowest form of friendship". In loose terms, it would be someone that I acknowledge or okay with. Do you agree with this general definition? I was looking for clarification on the "someone you know" bit. Thanks. -Sarven From tantek at cs.stanford.edu Tue Apr 6 18:01:26 2010 From: tantek at cs.stanford.edu (=?UTF-8?Q?Tantek_=C3=87elik?=) Date: Tue Apr 6 18:01:50 2010 Subject: [uf-discuss] Level of rel=contact In-Reply-To: <1270598549.2680.173.camel@csarven-laptop> References: <1270588996.2680.152.camel@csarven-laptop> <1270598549.2680.173.camel@csarven-laptop> Message-ID: On Tue, Apr 6, 2010 at 5:02 PM, Sarven Capadisli wrote: > On Tue, 2010-04-06 at 22:48 +0000, Brian Suda wrote: >> On Tue, Apr 6, 2010 at 9:23 PM, Sarven Capadisli wrote: >> > I'm thinking that rel="contact" is generally attributed to someone that >> > we have at least a "lowest form of friendship" with. ?[...] It is not. The reason we added "contact" in XFN 1.1 was to indicate literally just what it says - that you have some sort of contact info about the person - this could be just a URL or email address for example. You can't assume any other semantics. It doesn't imply anything positive or negative. Thus you cannot conclude at least a "lowest form of friendship" - you cannot conclude anything about friendship from rel="contact". If you want to imply a "lowest form of friendship", then rel="acquaintance" is what you're looking for: http://gmpg.org/xfn/11#acquaintance acquaintance Someone who you have exchanged greetings and not much (if any) more ? maybe a short conversation or two. Often symmetric. >> > Additionally, >> > if the user doesn't have control over the declaration of such >> > relationship, wouldn't it be more meaningful and safer to exclude this >> > bit of information in the output? >> >> --- You lost me on "exclude this", exclude what exactly? > > My bad. My reference was to the example. Again, this is precisely one of the reasons why "contact" does not imply anything about friendship, so that you don't have to worry about "excluding" it due to an imagined implication. >> > The example I had in mind was 'Subscribers list' at >> > http://identi.ca/csarven >> >> --- if you are subscribing to someone, then it probably at minimum >> meets the definition of: someone that we have at least a "lowest form >> of friendship" I don't think you can make that assumption. subscription != friendship. You might be subscribing to an automated summary aggregate feed for example. For things like "subscribing" e.g. Identi.ca or Twitter followers or followings, there's been quite a bit of brainstorming over the past few years: http://microformats.org/wiki/xfn-brainstorming#fans_and_followers which appears to have converged on: rel="follower" (for indicating someone who is a follower of yours) rel="following" (for indicating someone who you are following) On such services that also permit "direct messaging" - these URLs also serve as a form of contact information, and thus rel="contact" could also be used: rel="follower contact" rel="following contact" Since direct messaging is not necessarily symmetric (neither is rel contact), it might make sense for such a service to label a link to another profile as a contact only if you do actually have the ability to contact (dm) them - though that might also be asking too much of the semantic of "contact" (since "has contact info" and "can contact" are two different things.) >> Are you suggesting it isn't and we should exclude it? > > No, I'll clarify. What I was trying to say was that, if I have a profile > page where it lists a bunch of people that are subscribed to me, I > wouldn't necessarily call them my contact since I don't really know > them. Hence, in my example at http://identi.ca/csarven , rel=contact > should be removed from Subscribers list. I agree that rev="contact" > makes more sense here, but, I'm focused on the incorrect use of > rel="contact". Why is it incorrect? It's only incorrect based on the assumptions you've presented about what rel="contact" means - which is basically a straw-man. > rel=contact is/should be reserved for people that meets the basic > requirement of that "lowest form of friendship". Why? We already have rel="acquaintance" for that semantic. Would it help to add any of this discussion to the FAQ? http://microformats.org/wiki/xfn-faq Tantek -- http://tantek.com/ From martin.lemburg at gmx.net Wed Apr 7 03:34:02 2010 From: martin.lemburg at gmx.net (Martin Lemburg) Date: Wed Apr 7 03:34:11 2010 Subject: [uf-discuss] hcalendar and its attendees Message-ID: <20100407103402.59990@gmx.com> Hello, I just experimented with the hcalender microformat and tried to add attendees to the hcalender. Sincerely most of the validate/extraction Web services don't care for the attendees. X2V cares for, but the results makes me wonder. Currently I use the hcalendar and attendee pattern this way (complex excerpt from the web page (under construction)):
  • Chorkonzert der "Petite Messe Solennelle" von Gioaccino Rossini

  • Is the usage of the anchor tag with the rel-tag semantics inside the attendee pattern done in the right way? Are really only mailto URLs allowed inside the attendee structures? Is the following better (because of the vcards role usage), than the version right above with the try to use the attendees role:
  • (Pianist)
  • Is the attendees role really only one of the iCalender definitions or even free text like in a vcard? Does it really make sense to use the attendee pattern, because the only content seem to be a mailto URL, if converted via X2V. I hope, I'm mailing to the right mailing list for such questions! Currently I don't know where to ask such questions! Best regards and thanks in advance for any comment, Martin Lemburg - 10551 Berlin - Germany - martin.lemburg@gmx.net From martin.lemburg at gmx.net Wed Apr 7 03:38:07 2010 From: martin.lemburg at gmx.net (Martin Lemburg) Date: Wed Apr 7 03:38:15 2010 Subject: [uf-discuss] hcalendar and its attendees Message-ID: <20100407103808.59950@gmx.com> Hello, sorry to say ... now I see, that all the leading whitespaces, all the "layout" format of the text is gone. I apologize for this not good to read text! Best regards, Martin > ----- Urspr?ngliche Nachricht ----- > Von: Martin Lemburg > Gesendet: 07.04.10 12:34 Uhr > An: microformats-discuss > Betreff: [uf-discuss] hcalendar and its attendees > Hello, I just experimented with the hcalender microformat and tried to add attendees to the hcalender. Sincerely most of the validate/extraction Web services don't care for the attendees. X2V cares for, but the results makes me wonder. Currently I use the hcalendar and attendee pattern this way (complex excerpt from the web page (under construction)):
  • Chorkonzert der "Petite Messe Solennelle" von Gioaccino Rossini

  • Is the usage of the anchor tag with the rel-tag semantics inside the attendee pattern done in the right way? Are really only mailto URLs allowed inside the attendee structures? Is the following better (because of the vcards role usage), than the version right above with the try to use the attendees role:
  • (Pianist)
  • Is the attendees role really only one of the iCalender definitions or even free text like in a vcard? Does it really make sense to use the attendee pattern, because the only content seem to be a mailto URL, if converted via X2V. I hope, I'm mailing to the right mailing list for such questions! Currently I don't know where to ask such questions! Best regards and thanks in advance for any comment, Martin Lemburg - 10551 Berlin - Germany - martin.lemburg@gmx.net _______________________________________________ microformats-discuss mailing list microformats-discuss@microformats.org http://microformats.org/mailman/listinfo/microformats-discuss From david at visitnorthwest.com Tue Apr 13 08:43:57 2010 From: david at visitnorthwest.com (Visit North West) Date: Tue Apr 13 08:44:21 2010 Subject: [uf-discuss] microformats implementation - i'd value your opinions Message-ID: <36E4BEE4876246B2B0F956218166AB27@DavidPC> Hi I'm new to microformats and would sincerely appreciate if somebody could spare a couple of minutes to give me their valuable opinion on a proposed implementation of microformats. I wouldn't even call myself a programmer so please forgive any errors. I've done a test page and obvious want to make sure everything is ok before I implement microformats sitewide: http://www.visitnorthwest.com/manchester/abc.htm It's a review of a hotel/booking page. My main points are: 1. Hreview - Because of the way the page is already structured I've had to wrap hreview around columns 2 and 3. This takes in some superfluous information (i.e Popular hotels in Manchester) but I can't see a way around it without changing the structure of the page - which is pretty undesirable for this site as its about 4000 pages 2. All the address info, review info is contained within the info box in column 3
    , the 'description' itself is before this in column 2. 3. Address info - I've not put the country in as it's a UK site and fairly obvious to readers. Is country info necessary, especially with regard to search engines? 4. Photos - I've assigned image class 'photo' to each photo. Is anything else necessary? Google's rich snippet tool seems to like it, although it doesn't pick up any image info http://www.google.com/webmasters/tools/richsnippets Please let me know if there is anything different you would do. Thanks in advance for your help. Kind regards David Mottershead | Visit North West From george.brocklehurst at gmail.com Fri Apr 16 04:57:08 2010 From: george.brocklehurst at gmail.com (George Brocklehurst) Date: Fri Apr 16 04:57:14 2010 Subject: [uf-discuss] hProduct/hReview issue Message-ID: Hi all, There is an issue with using hProduct and hReview together: An hProduct can include one or more hReviews. Each hReview requires an item, which should be the hProduct. The include-pattern prohibits references to an ancestor. Therefore it is not clear how to include a valid hReview in an hProduct. It has been suggested that this could be resolved by reusing the item-url property from item-license to specify the hReview's item. This is documented on the hProduct issues page, with links to the relevant parts of the wiki and IRC logs: http://microformats.org/wiki/hproduct-issues#HP8_-_No_clear_way_of_including_a_valid_hReview_that_refers_back_to_the_hProduct_as_its_item Are there any objections to using item-url? If not, I'm happy to mark the issue as resolved and update the hReview and hProduct specifications. Thanks, George From mail at tobyinkster.co.uk Fri Apr 16 05:49:45 2010 From: mail at tobyinkster.co.uk (Toby Inkster) Date: Fri Apr 16 05:49:54 2010 Subject: [uf-discuss] hProduct/hReview issue In-Reply-To: References: Message-ID: <1271422185.15832.64.camel@ophelia2.g5n.co.uk> On Fri, 2010-04-16 at 12:57 +0100, George Brocklehurst wrote: > There is an issue with using hProduct and hReview together: An > hProduct can include one or more hReviews. Each hReview requires an > item, which should be the hProduct. The include-pattern prohibits > references to an ancestor. Therefore it is not clear how to include a > valid hReview in an hProduct. The other possibility would be to relax the requirement for hReview to contain an item when it's obvious from context; the context in this case being that the hReview is within an hProduct. There is a similar concern re hProduct and hListing IIRC. > Are there any objections to using item-url? It seems to introduce extra markup that's likely to be extraneous from an end-user point-of-view, and thus set to display:none by authors. -- Toby A Inkster From lists at ben-ward.co.uk Fri Apr 16 11:18:55 2010 From: lists at ben-ward.co.uk (Ben Ward) Date: Fri Apr 16 11:19:00 2010 Subject: [uf-discuss] hProduct/hReview issue In-Reply-To: <1271422185.15832.64.camel@ophelia2.g5n.co.uk> References: <1271422185.15832.64.camel@ophelia2.g5n.co.uk> Message-ID: <732EB404-07D3-4C9F-A740-1A8C38CC7D29@ben-ward.co.uk> On 16 Apr 2010, at 05:49, Toby Inkster wrote: > On Fri, 2010-04-16 at 12:57 +0100, George Brocklehurst wrote: >> There is an issue with using hProduct and hReview together: An >> hProduct can include one or more hReviews. Each hReview requires an >> item, which should be the hProduct. The include-pattern prohibits >> references to an ancestor. Therefore it is not clear how to include a >> valid hReview in an hProduct. > > The other possibility would be to relax the requirement for hReview to > contain an item when it's obvious from context; the context in this case > being that the hReview is within an hProduct. > > There is a similar concern re hProduct and hListing IIRC. This ties closely to some work I started documenting last year on ?containers? in general. That being, the pattern where you have a number of microformats in a page applied to the same ?item?, or more generally, where properties of the main subject of a page are shared by multiple microformat objects (such as, a TV listings page contains many `vevents`, they all share the same `location` (the channel name).) Could be worth adding to that documentation the `hProduct contains hReviews` pattern with that. As ever, further thoughts on the modelling are appreciated. http://microformats.org/wiki/container-brainstorming Ben From george.brocklehurst at gmail.com Sat Apr 17 06:48:23 2010 From: george.brocklehurst at gmail.com (George Brocklehurst) Date: Sat Apr 17 06:56:19 2010 Subject: [uf-discuss] hProduct/hReview issue In-Reply-To: <732EB404-07D3-4C9F-A740-1A8C38CC7D29@ben-ward.co.uk> References: <1271422185.15832.64.camel@ophelia2.g5n.co.uk> <732EB404-07D3-4C9F-A740-1A8C38CC7D29@ben-ward.co.uk> Message-ID: On Fri, Apr 16, 2010 at 7:18 PM, Ben Ward wrote: > > This ties closely to some work I started documenting last year on ?containers? in general. That being, the pattern where you have a number of microformats in a page applied to the same ?item?, or more generally, where properties of the main subject of a page are shared by multiple microformat objects (such as, a TV listings page contains many `vevents`, they all share the same `location` (the channel name).) > > Could be worth adding to that documentation the `hProduct contains hReviews` pattern with that. As ever, further thoughts on the modelling are appreciated. I've added "hProduct contains hReviews" to the list of existing containers, as well as an additional suggestion of how containers could be marked up [1]. Given the containers work it would make sense to remove the `review` property from hProduct altogether, and instead use a more generic container structure to mark up multiple reviews that share the same item. This would allow all review items (hProducts, hCards, hCalendar events etc.) to be shared between multiple reviews, instead of defining a special case which was only applicable to product reviews. [1] http://microformats.org/wiki/container-brainstorming#Prefixes_to_indicate_shared_properties From ehs at pobox.com Wed Apr 21 11:16:23 2010 From: ehs at pobox.com (Ed Summers) Date: Wed Apr 21 11:16:30 2010 Subject: [uf-discuss] xfn use on librarything.com petition Message-ID: Just a quick note to let you know about a modest petition I put together to get rel="me" use on librarything.com, which is a popular social media site for personal book collections: http://www.petitiononline.com/lt09/petition.html If you have the time to sign I would appreciate your support. //Ed From sahuguet at google.com Thu Apr 22 13:45:09 2010 From: sahuguet at google.com (Arnaud Sahuguet) Date: Thu Apr 22 14:16:58 2010 Subject: [uf-discuss] best practices to represent business hierarchies Message-ID: Hi, Say I want to represent the Google offices, as all being part of the same entity Google. e.g. http://www.google.com/corporate/address.html Or say I want to represent a Mc Donald's restaurant and want to express the fact they are all franchises from the same "brand". How would I represent that? Should I use fn for the name of the name of the office/branch and org for the global entity they belong to? Should I use rel-group? Suggestions are welcome. regards, -- Arnaud -- Arnaud From sahuguet at google.com Thu Apr 22 13:44:38 2010 From: sahuguet at google.com (Arnaud Sahuguet) Date: Thu Apr 22 14:18:11 2010 Subject: [uf-discuss] best practices to represent "person working at" Message-ID: Hi, say I want to represent a doctor working at a hospital. What's the preferred way to represent that?
    Perry Cox, MD
    Sacred Heart hospital
    1 Hospital Avenue
    San Diego, CA 92101
    619) 555-5020 x 1234
    VS
    Perry Cox, MD
    1 Hospital Avenue
    San Diego, CA 92101
    619) 555-5020 x 1234
    But the use of rel-org assumes that the containing page represents Dr Perry Cox (representative hcard). regards, -- Arnaud -- Arnaud From brian.suda at gmail.com Thu Apr 22 16:36:10 2010 From: brian.suda at gmail.com (Brian Suda) Date: Thu Apr 22 16:36:19 2010 Subject: [uf-discuss] best practices to represent "person working at" In-Reply-To: References: Message-ID: On Thu, Apr 22, 2010 at 8:44 PM, Arnaud Sahuguet wrote: > say I want to represent a doctor working at a hospital. > What's the preferred way to represent that? > >
    > ?Perry Cox, MD > ?
    Sacred Heart hospital
    > ?
    > ?
    1 Hospital Avenue
    > ?San Diego, > ?CA > ?92101 > ?
    > ?
    619) 555-5020 x 1234
    >
    --- this certainly represents a person who has a job at a place called "Sacred Heart Hospital" we don't know more about that entity. The address is for the person, but it can be set to TYPE WORK so people know this is the Doctor's work address. >
    > ?Perry Cox, MD > ? > ?
    > ?
    1 Hospital Avenue
    > ?San Diego, > ?CA > ?92101 > ?
    > ?
    619) 555-5020 x 1234
    >
    > But the use of rel-org assumes that the containing page represents Dr > Perry Cox (representative hcard). --- this isn't any different. To an hCard parse you'd get the same result. Adding a class="card" won't do anything and rel="group" won't get you anything connected to the representative hcard. Maybe i'm just not following you. Do you have an example page in mind? -brian -- brian suda http://suda.co.uk From brian.suda at gmail.com Thu Apr 22 16:50:10 2010 From: brian.suda at gmail.com (Brian Suda) Date: Thu Apr 22 16:50:14 2010 Subject: [uf-discuss] best practices to represent business hierarchies In-Reply-To: References: Message-ID: On Thu, Apr 22, 2010 at 8:45 PM, Arnaud Sahuguet wrote: > Say I want to represent the Google offices, as all being part of the > same entity Google. > e.g. http://www.google.com/corporate/address.html > > How would I represent that? --- there have been discussions in the past about using XOXO, but that is just a specific type of LIST
      /
        > Should I use fn for the name of the name of the office/branch and org > for the global entity they belong to? --- each office can be an entity in itself, so you can logically mark each of those up with an hCard. That makes sense. > Should I use rel-group? --- I guess it all depends on what your intention is. There could be some heuristics that say if all the URLs are the same, it is probably part of the same group. There are also different sub-sections to ORG, such as org-unit, maybe it is worth saying ORG: - org-name: XYZ co. - org-unit: washington branch Maybe that's overloading the ORG maybe not. Groups haven't really been discussed in a long time. I'm not sure if anyone is actively publishing much with rel-group. Does anyone know more? -brian -- brian suda http://suda.co.uk From mail at tobyinkster.co.uk Fri Apr 23 03:54:20 2010 From: mail at tobyinkster.co.uk (Toby Inkster) Date: Fri Apr 23 03:54:27 2010 Subject: [uf-discuss] best practices to represent "person working at" In-Reply-To: References: Message-ID: <68efebd9e7ca5ad4cc1d6dbce2ea8803.squirrel@goddamn.co.uk> > say I want to represent a doctor working at a hospital. > What's the preferred way to represent that? > >
        > Perry Cox, MD >
        Sacred Heart hospital
        >
        >
        1 Hospital Avenue
        > San Diego, > CA > 92101 >
        >
        619) 555-5020 x 1234
        >
        The other way to do it would be to invert it and create an hCard for the organisation, listing the doctor (or doctors) as an agent:

        Sacred Heart hospital

        1 Hospital Avenue
        San Diego, CA 92101

        Staff

        • Perry Cox, MD
          (619) 555-5020 x 1234
        • John "J.D." Dorian
          (619) 555-5020 x 4321
        -Toby From fberriman at gmail.com Mon Apr 26 03:33:53 2010 From: fberriman at gmail.com (Frances Berriman) Date: Mon Apr 26 03:34:33 2010 Subject: [uf-discuss] Species in BBC wildlife finder Message-ID: Friend and colleague, Alistair Duggin, has just added some nice finishing touches to the BBC's Wildlife finder and added the species draft microformat to the mark-up. Would be great if those who are/have been involved with the format could take a critical look at it. He noted that he used wikipedia as a reference point. http://www.bbc.co.uk/nature/species/Cougar -F -- Frances Berriman http://fberriman.com From sahuguet at google.com Mon Apr 26 14:05:35 2010 From: sahuguet at google.com (Arnaud Sahuguet) Date: Mon Apr 26 14:06:01 2010 Subject: [uf-discuss] best practices to represent "person working at" In-Reply-To: <68efebd9e7ca5ad4cc1d6dbce2ea8803.squirrel@goddamn.co.uk> References: <68efebd9e7ca5ad4cc1d6dbce2ea8803.squirrel@goddamn.co.uk> Message-ID: How would you cope with this kind of information, a doctor working for multiple hospitals. e.g. http://www.healthgrades.com/directory_search/physician/profiles/dr-md-reports/Dr-Joseph-Castrejon-MD-208D4271/hospital-affiliations/?cid=prt_google_physician_affilh_20100228 Is there an agreed upon way to represent this structure using hCards? regards, Arnaud On Fri, Apr 23, 2010 at 6:54 AM, Toby Inkster wrote: > > > say I want to represent a doctor working at a hospital. > > What's the preferred way to represent that? > > > >
        > > ?Perry Cox, MD > > ?
        Sacred Heart hospital
        > > ?
        > > ?
        1 Hospital Avenue
        > > ? San Diego, > > ? CA > > ? 92101 > > ?
        > > ?
        619) 555-5020 x 1234
        > >
        > > The other way to do it would be to invert it and create an hCard for the > organisation, listing the doctor (or doctors) as an agent: > >
        > ?

        Sacred Heart hospital

        > ?
        > ?
        1 Hospital Avenue
        > ?San Diego, > ?CA > ?92101 > ?
        > ?

        Staff

        > ?
          > ?
        • > ? ? Perry Cox, MD > ? ?
          (619) 555-5020 x 1234
          > ?
        • > ?
        • > ? ? John "J.D." Dorian > ? ?
          (619) 555-5020 x 4321
          > ?
        • > ? > ?
        >
        > > -Toby > _______________________________________________ > microformats-discuss mailing list > microformats-discuss@microformats.org > http://microformats.org/mailman/listinfo/microformats-discuss -- Arnaud Sahuguet Geo Infrastructure PM, New York office -- competing with God to build the world in less than 6 days -- -- and propagate updates to maps.google.com in less than 15 minutes (2010 OKR) From sahuguet at google.com Wed Apr 28 08:59:41 2010 From: sahuguet at google.com (Arnaud Sahuguet) Date: Wed Apr 28 09:00:15 2010 Subject: [uf-discuss] best practices to represent "person working at" In-Reply-To: References: <68efebd9e7ca5ad4cc1d6dbce2ea8803.squirrel@goddamn.co.uk> Message-ID: anybody? If there is a killer app for microformats, it will probably be related to Local data. If there is no good proposed solution based on hCards, the industry might be moving to something else, e.g. OpenGraph Protocol. I think the page of a doctor working at multiple hospital is a very strong use case. Is there a rich and meaningful solution based on hCard? regards, Arnaud From brian.suda at gmail.com Wed Apr 28 10:58:25 2010 From: brian.suda at gmail.com (Brian Suda) Date: Wed Apr 28 10:58:30 2010 Subject: [uf-discuss] best practices to represent "person working at" In-Reply-To: References: <68efebd9e7ca5ad4cc1d6dbce2ea8803.squirrel@goddamn.co.uk> Message-ID: On Wed, Apr 28, 2010 at 3:59 PM, Arnaud Sahuguet wrote: > I think the page of a doctor working at multiple hospital is a very > strong use case. --- this is simply an hCard with multiple work addresses. > Is there a rich and meaningful solution based on hCard? --- I think what you are lookinng for is something much larger like groups and relationships. Since hCard is modeled off of vCard, if you aren't seeing this sort of information inside an address book, you probably won't see it in hCard either. There might be larger solutions that use hCard to represent a person, such as xoxo. That's a list of items, which could be an hCard. -brian -- brian suda http://suda.co.uk From sahuguet at google.com Wed Apr 28 12:54:44 2010 From: sahuguet at google.com (Arnaud Sahuguet) Date: Wed Apr 28 12:55:11 2010 Subject: [uf-discuss] best practices to represent "person working at" In-Reply-To: References: <68efebd9e7ca5ad4cc1d6dbce2ea8803.squirrel@goddamn.co.uk> Message-ID: I have found a solution based on RDF-a using xmlns:v="http://rdf.data-vocabulary.org/#"> as suggested in Google Webmaster web pages at http://www.google.com/support/webmasters/bin/answer.py?hl=en&answer=146898
        Dr. Raneth Y Heng, MD
        is working at the following locations:
        • Scripps Green Hospital 10666 North Torrey Pines Road La Jolla,CA
        • Scripps Memorial Hospital Encinitas 354 Santa Fe Drive, Encinitas, CA
        • Scripps Memorial Hospital La Jolla 9888 Genesee Avenue, La Jolla, CA
        • Scripps Mercy Hospital 4077 5th Avenue, San Diego, CA
        • Scripps Mercy Hospital - Chula Vista 435 H Street, Chula Vista, CA
        Original content = http://www.healthgrades.com/directory_search/physician/profiles/dr-md-reports/Dr-Raneth-Heng-MD-ADD63715/hospital-affiliations/?cid=prt_google_physician_affilh_20100228 Comments, suggestions are welcome. Arnaud On Wed, Apr 28, 2010 at 1:58 PM, Brian Suda wrote: > On Wed, Apr 28, 2010 at 3:59 PM, Arnaud Sahuguet wrote: >> I think the page of a doctor working at multiple hospital is a very >> strong use case. > > --- this is simply an hCard with multiple work addresses. > >> Is there a rich and meaningful solution based on hCard? > > --- I think what you are lookinng for is something much larger like > groups and relationships. Since hCard is modeled off of vCard, if you > aren't seeing this sort of information inside an address book, you > probably won't see it in hCard either. > > There might be larger solutions that use hCard to represent a person, > such as xoxo. That's a list of items, which could be an hCard. > > -brian > > -- > brian suda > http://suda.co.uk > _______________________________________________ > microformats-discuss mailing list > microformats-discuss@microformats.org > http://microformats.org/mailman/listinfo/microformats-discuss >