Given all this, does anybody have an idea why this wasn't implemented
in things like Sandbox, and how to encourage the theme authors to do
it in the next version?
Steph
--
http://climbtothestars.org/
___
microformats-discuss mailing list
Right -- and a uF for expressing that relationship; this gets a little
trickier. As uFs are about codifying existing practices, my
(superficial) look at comment nesting shows that many sites (like
slashdot) using nesting to express relationships, not explicit URI
linking. On the other hand,
If I can then get GMail to dynamically read the hCards from LinkedIn,
I'll be in Web 2.0 e-mail Nirvana.
Regards, etc...
David
On 9/11/06, Chris Messina [EMAIL PROTECTED] wrote:
Check it out... as part of their redesign, LinkedIn will be supporting
hcard and hresume:
This will make the decision for openBC easier I think ;)
___
microformats-discuss mailing list
microformats-discuss@microformats.org
http://microformats.org/mailman/listinfo/microformats-discuss
Grr, forgot to remove my email signature from last post. Being a
jobsworth but must point out that the email and its contents etc are in
no way connected to my employees etc yadayadayada
Sorry
Tony Farndon
Just another guy...
+ The Forestry Commission's computer systems may be monitored
I have a meeting with the Flock folks today (yes, my former employer!)
and I'll drop them a hint -- as I did when I worked there -- about
their opportunity in being the first (and best!) in supporting
microformats natively.
Thanks for the tip!
Chris
On 9/12/06, Farndon, Tony [EMAIL PROTECTED]
Hi Chris
Be sure NOT to show them the extension source code, they will scornfully
frown at the immaturity of it :-). Mind you I knew absolutely nothing
about xul and javascript before june of this year so you can't expect
too much!
Gives an idea of how easily it could fit into the blog editor
Here's teh workflow for you non-Flockers:
http://www.flickr.com/photos/factoryjoe/sets/72157594281137456/
Nice work Tony! I'll definitely show the Flock folks the visuals! ;)
What license is your extension?
Chris
On 9/12/06, Farndon, Tony [EMAIL PROTECTED] wrote:
Hi Chris
Be sure NOT to
damn forgot, will release under the GPL (and if you want to throw a 17
mac book pro my way as a thank you please do so..)
Double damn, just realised I referred to flock as your employees not ers
in my original post!
Good luck, it really isn't too much work for them to incorporate
Where it really gets interesting is in adding mF detection to Lucene.
I'm pushing them to store people and relationships in hcard and xfn,
but so far they've rolled their own RDF.
Grr!
Chris
On 9/12/06, Farndon, Tony [EMAIL PROTECTED] wrote:
damn forgot, will release under the GPL (and
I think that if using hAtom for comments is going to become 'standard'
that we definately need to use class=comments (or something similar)
to identify the nested comments feeds inside the main hfeed. Also,
comments don't really have a 'title'... you could use the original
post title (rarely
would the feeds be nested? I think that in the example I saw, there
were two feeds. One with only the blog post, and a separate one with
the comments. Is it permitted by hAtom to nest feeds? I thought it
wasn't.
Steph
On 9/12/06, Stephen Paul Weber [EMAIL PROTECTED] wrote:
I think that if
Comments are (almost) always right after a post... so yes, the comment
feeds would have to be nested, unless the existed only on item pages.
Having all the data avaliable at once has proved very useful in my
previous applications of related technology (XOXO-based encoding as
seen on
Comments are nested within entries and hfeed elements can be nested
too. Typically, one doesn't see multiple entries with comments on the
same page.
In usage that I've seen, one would probably use this nesting structure:
* hfeed (for the blog, optional)
** hentry (for the one entry on the page)
On 9/12/06, David Janes [EMAIL PROTECTED] wrote:
Comments are nested within entries and hfeed elements can be nested
too. Typically, one doesn't see multiple entries with comments on the
same page.
it can be found in the wild, though. A very famous french-language
blog, for example:
I'd say both points are arguable. From my point of view, tags should be
inside the post content, as otherwise they may be dropped from the
feed.
Likewise, Stephanie's other-language summaries are currently not in her
Atom feed, which makes it less useful, as I find the English summaries
handy
16 matches
Mail list logo
