Re: [uf-discuss] ANN: hCard Tutorial
On 12/19/06, Ciaran McNulty [EMAIL PROTECTED] wrote: Where you say Why isn't it hCard? Apparently there are some historical reasons for it, but I do not know the reasons. in slide 3, the simple answer is that in vCard, the root property is VCARD, as in: I should have added 'so because hCard gets all its fieldnames from vCard, this is carried across'. -Ciaran McNulty ___ microformats-discuss mailing list microformats-discuss@microformats.org http://microformats.org/mailman/listinfo/microformats-discuss
Re: [uf-discuss] Scripts for hCard - .vcf
On 12/18/06, Andy Mabbett [EMAIL PROTECTED] wrote: Are there scripts, available freely, which can be run locally? I'm interested in both pp for my own, small-scale projects, and something more roust, for very large companies which might use them in their high-traffic sites; as part of our advocacy work. --- sure, there is some Ruby code out there which can be run locally, also hg.microformats.org has all the free scripts that can be freely downloaded and run locally from the command line and/or via a variety of different programming languages. The best place to look is of each microformats wiki page, there should be an implementations section where folks have added their code - you'll have to check each license accordingly. -brian -- brian suda http://suda.co.uk ___ microformats-discuss mailing list microformats-discuss@microformats.org http://microformats.org/mailman/listinfo/microformats-discuss
[uf-discuss] A microformat for relationship availability and preference?
Hi all. It's my first post, and I'll just dive right in. I'm interested in using microformats to represent an individual's relationship availability and preferences. This is part of an experiment in pushing relationship-seeking to the *cough* edges of the network, if you will. I'm hardly ready to propose a format, but at a minimum I see implementors providing their gender and their gender preference. Ideal location, age ranges, and other preferences would be optional. Given that this format is intended for those seeking a relationship I'm not sure if including their present relationship status is relevant; looking is implicit, else they should not be publishing this data. Of course, extending an existing microformat may make more sense than establishing a new one. hCard seems the most applicable of existing microformats, as XFN is intended to represent existing relationships and not potential relationships. That said, I picture scenarios in which one would want to publish their relationship availability outside of the context of the kind of contact information hCard is meant for. Your thoughts are much appreciated. -- Alex Payne http://www.al3x.net ___ microformats-discuss mailing list microformats-discuss@microformats.org http://microformats.org/mailman/listinfo/microformats-discuss
Re: [uf-discuss] A microformat for relationship availability and preference?
On 12/20/06, Chris Messina [EMAIL PROTECTED] wrote: You could also use the absense of certain XFN values as a stopgap... At least you know that the folks without sweatheart or spouse haven't removed themselves from the pool! What if one's sweetheart doesn't have a URL (insane as that sounds in this day and age)? :-) -Ciaran McNulty ___ microformats-discuss mailing list microformats-discuss@microformats.org http://microformats.org/mailman/listinfo/microformats-discuss
