[microformats-discuss] Re: Blog post format challenge - content vs summary

Sat Aug 13 20:33:40 PDT 2005

On Aug 13, 2005, at 4:31 PM, David Janes -- BlogMatrix wrote:
> Hi Ryan and Geof,
>> In Atom ... which seems to me to provide a reasonable definition 
> for blogable content ... you'd probably want to call your enclosure 
> element "entry". The permalink is a little more problematic ... I 
> decided that "entrylink" seemed to make as more sense than the 
> alternatives.

IMHO, any HTML practices should trump Atom (which is why I suggested 
using rel="self bookmark") because it will minimize disruption for 
people who want to adopt this microformat.
> Did you try the Greasemonkey script I mailed out this morning?

Not yet.
-ryan
> You should be able to tweak it to quickly identify the posts (I'm 
> using "xentry" for the top level item, but that's certainly subject 
> to change). In either case, you can see the argument for settling 
> this out.
>> "summary" is very nice, and also part of the Atom standard; it then 
> differentiates between the full content ("content") and a part of it.
>> Regards, etc...
> David
> http://www.blogmatrix.com
>> Ryan King wrote:
>>> On Aug 13, 2005, at 3:37 PM, Geoffrey Glass wrote:
>>>>> I've started marking up my blog [1] as a blog microformat 
>>> experiment. I'm using the same classes as in my annotation 
>>> code, which is not to say I think they're the best that have 
>>> been proposed (I don't).
>>>>> Awesome.
>> A little (hopefully constructive) criticism...
>>>>> <div class="post">
>>>>> Not bad, class="item" would be another option.
>>>>> <h3 class="title">
>>> <a rel="link" href="http://www.geof.net/blog/2005/08/11/indiana- 
>>> jones-school-of-management" title="Permanent link to this 
>>> article">Indiana Jones School of Management</a></h3>
>>>>> Why not rel="self permalink" ?
>> This is already in use for a lot of blogging platforms, I'm not 
>> sure if there's a normative definition anywhere, but I think the 
>> semantics are pretty well established.
>>>>> <div class="summary">
>>>>> +1
>>>>> <p>I was quite shocked a few weeks back when Google for 
>>> inscrutable reasons decided to bump me to the #1 search result 
>>> for &#8220;geof&#8221;. Sometimes it dumps me on the second 
>>> page, now I&#8217;m #1. Huh. Anyway, I thought this this link 
>>> from <a href="http://ijsm.org/archives/2005/08/07/2-geof/">Geof 
>>> Morris&#8217; Indiana Jones School of Management</a> was 
>>> downright neighborly. ...</p>
>>> </div>
>>> One thing came up immediately: the distinction between index 
>>> pages (with posts summaries) and full content pages.
>>>>> I think this is a minority of blogs (though I may be wrong) and 
>> probably troublesome. Also, this method of posting has too many 
>> problems for us to solve here.
>> -ryan
>>>>> I marked up both, using a class of "summary" for excerpts and 
>>> "content" for full content. On the one hand, I don't like the 
>>> added complexity; on the other, I suspect there are legitimate 
>>> use cases for marking up index pages (come to think of it, my 
>>> contextual copy implementation [2] may be one of them).
>>>>>> Geof
>>>>>> [1] http://www.geof.net/blog/
>>> [2] http://www.geof.net/code/annotation/demo/ (Smart Copy at the 
>>> bottom)
>>>>> _______________________________________________
>> microformats-discuss mailing list
>> microformats-discuss at microformats.org
>> http://microformats.org/mailman/listinfo/microformats-discuss
>>>> _______________________________________________
> microformats-discuss mailing list
> microformats-discuss at microformats.org
> http://microformats.org/mailman/listinfo/microformats-discuss
>