From jacob at bigroom.ca Mon May 12 22:15:38 2008 From: jacob at bigroom.ca (Jacob Malthouse) Date: Mon May 12 22:15:46 2008 Subject: [uf-new] standard text for new proposals to this list Message-ID: Hello, Is there a standard text for introducing new microformat proposals? I have read and prepared the appropriate information in accordance with http://microformats.org/wiki/process best regards, Jacob Jacob Malthouse | Big Room Inc +1 604 217 6106 From msporny at digitalbazaar.com Tue May 13 05:14:30 2008 From: msporny at digitalbazaar.com (Manu Sporny) Date: Tue May 13 05:15:38 2008 Subject: [uf-new] standard text for new proposals to this list In-Reply-To: References: Message-ID: <48298626.503@digitalbazaar.com> Jacob Malthouse wrote: > Is there a standard text for introducing new microformat proposals? Not really - just post what you're thinking and why you think it's needed. The most important thing is that you show that there are enough examples out there to warrant further discussion. If the proposal is interesting enough, it'll be met with furious debate as to whether we need a microformat to cover it or not. :) > I have read and prepared the appropriate information in accordance with > http://microformats.org/wiki/process Good, then you've done the basics if you're following the process document. Post away... -- manu -- Manu Sporny President/CEO - Digital Bazaar, Inc. blog: DB Launches Medical Record Sales Service with Shepherd Medical http://blog.digitalbazaar.com/2008/02/24/health2trade/ From goldberg.dieter at gmail.com Thu May 15 20:31:36 2008 From: goldberg.dieter at gmail.com (Dieter Goldberg) Date: Thu May 15 20:31:40 2008 Subject: [uf-new] New uf proposal: privacy policy. Message-ID: Hello, I would like to open up discussion on a privacy policy microformat, similar to the rel-license microformat. Below is a rudimentary XMDP profile.
rel

HTML4 definition of the 'rel' attribute. Here is an additional value.

license
Indicates that the referred resource is a privacy policy for the referring website.
Please comment. --Dieter From a.b.harrison at cs.cardiff.ac.uk Fri May 16 01:44:59 2008 From: a.b.harrison at cs.cardiff.ac.uk (Andrew Harrison) Date: Fri May 16 01:45:29 2008 Subject: [uf-new] resource access methods Message-ID: Hi, I'm pretty new to microformats so please forgive any dumb questions or assumptions. I have been looking for a while for some way of describing how you might access a resource other than the typically implied GET. It seems to me a pretty general requirement but one which is not well supported. In particular I want to model a process, or graph, that might involve a number of steps including posting, putting, getting and deleting resources. But I don't want to get bogged down in WADLesque description documents, not least because the graph should be able to change as you move through it. I can imagine it could be achieved through something as simple as a link relation: (my understanding is that href attributes only imply an HTTP GET, as opposed to specifying it.) Or through something more complex, i.e. an hxxx. So I'm wondering if there has been any work or thoughts on this. Is there some obvious trap I have missed? Would microformats be a suitable way forward? cheers, Andrew From mail at tobyinkster.co.uk Sat May 17 15:51:24 2008 From: mail at tobyinkster.co.uk (Toby A Inkster) Date: Sat May 17 15:51:35 2008 Subject: [uf-new] New uf proposal: privacy policy. Message-ID: <48AEBCFD-CD67-4F91-A88B-2F64394D96D8@tobyinkster.co.uk> > I would like to open up discussion on a privacy policy microformat, > similar to the rel-license microformat. I wonder if rel="p3pv1" could be repurposed? -- Toby A Inkster From a.b.harrison at cs.cardiff.ac.uk Sun May 18 09:27:07 2008 From: a.b.harrison at cs.cardiff.ac.uk (Andrew Harrison) Date: Sun May 18 09:27:14 2008 Subject: [uf-new] resource access methods In-Reply-To: References: Message-ID: <7C8DE2ED-706C-4BFB-A7D5-EFAF21A50E6E@cs.cf.ac.uk> I think what I'm imagining is something more akin to:

GET /user/{user- name}

This would allow online API descriptions to use common class attributes as well as expressing relationships between resources. cheers, Andrew On 16 May 2008, at 09:44, Andrew Harrison wrote: > Hi, > > I'm pretty new to microformats so please forgive any dumb questions > or assumptions. > > I have been looking for a while for some way of describing how you > might access a resource other than the typically implied GET. It > seems to me a pretty general requirement but one which is not well > supported. > > In particular I want to model a process, or graph, that might > involve a number of steps including posting, putting, getting and > deleting resources. But I don't want to get bogged down in WADLesque > description documents, not least because the graph should be able to > change as you move through it. > > I can imagine it could be achieved through something as simple as a > link relation: > > > > (my understanding is that href attributes only imply an HTTP GET, as > opposed to specifying it.) > > Or through something more complex, i.e. an hxxx. > > So I'm wondering if there has been any work or thoughts on this. Is > there some obvious trap I have missed? Would microformats be a > suitable way forward? > > cheers, > > Andrew > _______________________________________________ > microformats-new mailing list > microformats-new@microformats.org > http://microformats.org/mailman/listinfo/microformats-new School of Computer Science, Cardiff University, Queen's Buildings, Newport Road, Cardiff CF24 3AA, Wales, UK tel: 02920 879184 email: a.b.harrison@cs.cf.ac.uk From mail at ciaranmcnulty.com Mon May 19 01:29:59 2008 From: mail at ciaranmcnulty.com (Ciaran McNulty) Date: Mon May 19 01:30:03 2008 Subject: [uf-new] resource access methods In-Reply-To: <7C8DE2ED-706C-4BFB-A7D5-EFAF21A50E6E@cs.cf.ac.uk> References: <7C8DE2ED-706C-4BFB-A7D5-EFAF21A50E6E@cs.cf.ac.uk> Message-ID: > I think what I'm imagining is something more akin to: > >

> GET class="url">/user/{user-name} >

You mean not inside an a href? What sort of use cases do you envision? Specifically, can you point to some online resources that are doing this sort of thing where semantic markup could be added? -Ciaran From a.b.harrison at cs.cardiff.ac.uk Mon May 19 02:05:16 2008 From: a.b.harrison at cs.cardiff.ac.uk (Andrew Harrison) Date: Mon May 19 02:05:26 2008 Subject: [uf-new] resource access methods In-Reply-To: References: <7C8DE2ED-706C-4BFB-A7D5-EFAF21A50E6E@cs.cf.ac.uk> Message-ID: <4EB3EC33-1E85-4EC8-89AC-9EAD030032A3@cs.cf.ac.uk> Hi, I'm thinking of API docs such as: http://apidoc.digg.com/ http://groups.google.com/group/twitter-development-talk/web/api-documentation http://del.icio.us/help/api/ http://wiki.developers.facebook.com/index.php/API there are many more... Creating a session in the Facebook API is an example of requests that have dependencies/relationships. cheers, Andrew On 19 May 2008, at 09:29, Ciaran McNulty wrote: >> I think what I'm imagining is something more akin to: >> >>

>> GET > class="url">/user/{user-name} >>

> > You mean not inside an a href? > > What sort of use cases do you envision? Specifically, can you point > to some online resources that are doing this sort of thing where > semantic markup could be added? > > -Ciaran > _______________________________________________ > microformats-new mailing list > microformats-new@microformats.org > http://microformats.org/mailman/listinfo/microformats-new From asaberdahl at gmail.com Sat May 31 06:21:54 2008 From: asaberdahl at gmail.com (Asa Berdahl) Date: Sat May 31 06:21:58 2008 Subject: [uf-new] Possible Use for rel-tag for links. Message-ID: I have wasted hours try fruitlessly to develop a site and use microformats at the same time. I wanted to add some of the microformats use early on, in the design stage, but I couldn't find anything that wouldn't require me filling in information I don't already know. I kept thinking about what the rel-tag is for, "to describe the relation between the current page and the linked document", and then it struck me, why not try something there. We have maybe four other rel-tag attributes for a link now, one more couldn't hurt. I started to use what I like to call the rel-location. I got bored and thought that it might not just be good for the server to know, but the user as well, that they may be traveling away from the native server. The links could use a rel-tag to tell that. The possible values would be, "internal", or "external". They could be used in numerous ways, but I digress. The idea would give whether or not the page is hosted by the server, or a different server. This is how I ended up seeing it used: That was just one excerpt. The idea is to direct the user to a page located on the local server. It may be needless, but it could help with preventing theft of user information. It is simple and only needs to be added once. It makes it easy to understand. This could help. I may just be jumping off the deep end, but I thought it was a good idea.