Re: [uf-discuss] Hatom or hcalendar?

2007-03-23 Thread Jeremy Keith

Chris asked:

Question: would you mark up Twitter statuses with hatom or hcalendar?

The reason I ask is that Jeremy Keith's lifestream uses hcalendar --
and that statuses have either a title or content, but not both --
whereas the status itself could be consider the hcalendar summary...


This is a really good question. My first thought was Yeah, why  
*didn't* I use hAtom? After all, there's nothing to stop me using  
both hCalendar and hAtom...


So I started editing the template and I hit a snag: I don't have an  
author listed for each entry. Author is required for hAtom. Now, I  
could just put a single hCard somewhere within the hAtom feed and  
that would solve the problem:


From http://microformats.org/wiki/hatom:
If the Entry Author is missing, find the Nearest In Parent address  
element(s) with class name author and that is/are a valid hCard


But I'm not publishing an address already and isn't the whole idea  
of microformats that we don't change *what* we're publishing, just  
add more meaning to what we're already publishing?


Of course, I can go ahead and add the hAtom classes anyway:
http://lifestream.adactio.com/

But that's not a valid hAtom feed.

I have to say that I find it a little weird that author is required  
but entry-title is not. Looking at the Atom spec, title is a  
required feed element and author is recommended. For hAtom, that's  
been inverted:


http://atomenabled.org/developers/syndication/#requiredFeedElements

This has probably been discussed before, right? If anybody has some  
URLs pointing to previous discussions of this issue, that'd be much  
appreciated.


Bye,

Jeremy

--
Jeremy Keith

a d a c t i o

http://adactio.com/


___
microformats-discuss mailing list
microformats-discuss@microformats.org
http://microformats.org/mailman/listinfo/microformats-discuss


Re: [uf-discuss] Hatom or hcalendar?

2007-03-23 Thread David Janes

On 3/23/07, Jeremy Keith [EMAIL PROTECTED] wrote:

This is a really good question. My first thought was Yeah, why
*didn't* I use hAtom? After all, there's nothing to stop me using
both hCalendar and hAtom...

So I started editing the template and I hit a snag: I don't have an
author listed for each entry. Author is required for hAtom. Now, I
could just put a single hCard somewhere within the hAtom feed and
that would solve the problem:

 From http://microformats.org/wiki/hatom:
If the Entry Author is missing, find the Nearest In Parent address
element(s) with class name author and that is/are a valid hCard

But I'm not publishing an address already and isn't the whole idea
of microformats that we don't change *what* we're publishing, just
add more meaning to what we're already publishing?

Of course, I can go ahead and add the hAtom classes anyway:
http://lifestream.adactio.com/

But that's not a valid hAtom feed.


My belief now is that hAtom 0.2 should provide a better set of
defaulting rules, especially for author. It's crazy that hAtom
brings you 95% of the way to marking up microcontent and then lets
down what seems to be a fairly common use case. What this default
should be is a mystery, perhaps something like page or anonymous
with the url to be that of the page.


I have to say that I find it a little weird that author is required
but entry-title is not. Looking at the Atom spec, title is a
required feed element and author is recommended. For hAtom, that's
been inverted:

http://atomenabled.org/developers/syndication/#requiredFeedElements


No, this [1] is what you want to be looking at.

Regards, etc...
David

[1] http://atomenabled.org/developers/syndication/#recommendedEntryElements

--
David Janes
Founder, BlogMatrix
http://www.blogmatrix.com
http://blogmatrix.blogmatrix.com
___
microformats-discuss mailing list
microformats-discuss@microformats.org
http://microformats.org/mailman/listinfo/microformats-discuss


Re: [uf-discuss] Hatom or hcalendar?

2007-03-23 Thread Chris Casciano


On Mar 23, 2007, at 8:09 AM, Jeremy Keith wrote:



But I'm not publishing an address already and isn't the whole  
idea of microformats that we don't change *what* we're publishing,  
just add more meaning to what we're already publishing?


Of course, I can go ahead and add the hAtom classes anyway:
http://lifestream.adactio.com/

But that's not a valid hAtom feed.

I have to say that I find it a little weird that author is required  
but entry-title is not. Looking at the Atom spec, title is a  
required feed element and author is recommended. For hAtom,  
that's been inverted:


http://atomenabled.org/developers/syndication/#requiredFeedElements

This has probably been discussed before, right? If anybody has some  
URLs pointing to previous discussions of this issue, that'd be much  
appreciated.



without touching on the core issues [way to early to think my way  
through the docs] looking at the page, though sparse, it does strike  
me that you are already posting URL, nick and potentially logo/photo  
[if you consider it such] in the following markup:


h1a href=http://adactio.com/; accesskey=1 title=Home (access  
key: 1)img src=images/logo.gif alt=adactio //a/h1


i'll leave you to decide how to best turn that into a vcard that that  
can be associated with the hatom feed [but expanding the scope of the  
hatom root node would avoid need for some things like use of the  
nearest in parent fallback.


--
[ Chris Casciano ]
[ [EMAIL PROTECTED] ] [ http://placenamehere.com ]

___
microformats-discuss mailing list
microformats-discuss@microformats.org
http://microformats.org/mailman/listinfo/microformats-discuss


Re: [uf-discuss] Hatom or hcalendar?

2007-03-23 Thread Jeremy Keith

David wrote:

No, this [1] is what you want to be looking at.
[1] http://atomenabled.org/developers/syndication/ 
#recommendedEntryElements


Ah, I stand corrected. I didn't read closely enough:

Names one author of the entry. An entry may have multiple authors.  
An entry must contain at least one author element unless there is an  
author element in the enclosing feed, or there is an author element  
in the enclosed source element.


Thanks for the correction.

Chris C. wrote:
without touching on the core issues [way to early to think my way  
through the docs] looking at the page, though sparse, it does  
strike me that you are already posting URL, nick and potentially  
logo/photo [if you consider it such] in the following markup:


h1a href=http://adactio.com/; accesskey=1 title=Home (access  
key: 1)img src=images/logo.gif alt=adactio //a/h1


Good point. I'll get on that. Thanks.

Bye,

Jeremy

--
Jeremy Keith

a d a c t i o

http://adactio.com/


___
microformats-discuss mailing list
microformats-discuss@microformats.org
http://microformats.org/mailman/listinfo/microformats-discuss


Re: [uf-discuss] Hatom or hcalendar?

2007-03-23 Thread Andy Mabbett
In message [EMAIL PROTECTED], Jeremy
Keith [EMAIL PROTECTED] writes

So I started editing the template and I hit a snag: I don't have an
author listed for each entry. Author is required for hAtom. Now, I
could just put a single hCard somewhere within the hAtom feed and  that
would solve the problem:

From http://microformats.org/wiki/hatom:
If the Entry Author is missing, find the Nearest In Parent address
element(s) with class name author and that is/are a valid hCard

But I'm not publishing an address already and isn't the whole idea
of microformats that we don't change *what* we're publishing, just  add
more meaning to what we're already publishing?

I can add a +1 to that. When I came to add hAtom to several pages, for
example:

http://www.westmidlandbirdclub.com/new.htm

I had no author on the page. It prompted me to include a footer, with an
hCard, in every age, which itself was a good thing, but that may have
been either desirable nor possible.

Furthermore, if people subscribe to the resultant feed, they don't even
get to see the author details!

-- 
Andy Mabbett
 http://www.pigsonthewing.org.uk/uFsig/

Welcome to the world's longest week!
___
microformats-discuss mailing list
microformats-discuss@microformats.org
http://microformats.org/mailman/listinfo/microformats-discuss