Thom Shannon wrote:
Standardisation might be interesting here as well. For instance back
to blog comments. Comments from within aggregators would likely be
simpler where comment form definitions can be established
programmatically.
The problem is that comment spammers would love that too!
Paul Wilkins wrote:
On Dec 4, 2007 10:26 AM, Ben Ward [EMAIL PROTECTED] wrote:
The critical part of the HTML4 spec that causes 'Rayenda, Bangladesh'
*not* to be an abbreviation of '22.31119;+89.86145' is this:
The content of the ABBR and ACRONYM elements specifies the
abbreviated expression
Conor O'Neill wrote:
Just spotted on Blogger Dev Group that Blogger now supports hAtom.
Congrats to whoever evangelised this into Google and to Pete Hopkins and
the crew in there.
http://groups.google.com/group/bloggerDev/browse_thread/thread/69344c5cc35b472e?hl=en
Thanks. Kevin Marks
Chris Messina wrote:
...
I created a simple XFN aggregating application, it occurs to me that
adding email addresses, both for the purpose of rel-me links and for
contact links is actually useful and something that should be
supported in XFN (it's currently not clear whether this is acceptable
Evan Prodromou wrote:
...
I think this microformat would be best defined using the semantics of
the rel attribute of a links. For example, on the how-to-play page
on the microformats wiki, this link:
a href=/wiki?title=how-to-playamp;action=editEdit/a
would be changed to:
a
Arve Bersvendsen wrote:
On Tue, 20 Feb 2007 22:24:00 +0100, Thom Shannon [EMAIL PROTECTED] wrote:
Forgive me if this is going over old ground, I just joined this list and
couldn't find what I was looking for on the wiki. Are there any
particular conventions emerging for embedding an OpenID
Thom Shannon wrote:
Hi,
Forgive me if this is going over old ground, I just joined this list and
couldn't find what I was looking for on the wiki. Are there any
particular conventions emerging for embedding an OpenID into a hCard?
The openid-brainstorming page mentions using
Scott Reynen wrote:
On Feb 20, 2007, at 3:24 PM, Thom Shannon wrote:
Forgive me if this is going over old ground, I just joined this list and
couldn't find what I was looking for on the wiki. Are there any
particular conventions emerging for embedding an OpenID into a hCard?
The
Scott Reynen wrote:
On Feb 20, 2007, at 6:56 PM, John Panzer wrote:
Scott Reynen wrote:
...
Here's the purpose of UID from vCard:
To specify a value that represents a globally unique
identifier corresponding to the individual or resource associated
with the vCard.
So if two hCards
'
href='aim:goim?screenname=panzerjohn'panzerjohn/a/li
/ol
/body
/html
The use case for this is to let a user keep track of parts of their
social network, and specifically the parts that in this case are allowed
access to their blog.
Comments are welcomed.
--
John Panzer
System Architect
http
In our blogging app, we currently use a xoxo list of vcards as one
format for simple friends lists of readers and contributors. Our use
case is a bit more oriented towards personal lists than publishing
(think Rolodex or buddy list), but perhaps it maps well to the contact
groups/category
good to
be semantic to the last drop, but I think Tantek's advice on this
issue would help: how little data can substantiate hcard markup?
Chris
On 5/23/06, John Panzer [EMAIL PROTECTED] wrote:
All,
I have a use case for displaying lists of people (readers of a blog)
which seems reasonable
licensing
implementation).
http://microformats.org/discuss/mail/microformats-discuss/2006-February/003147.html
Anyway, I might be missing the point of your question -- what are you
looking for?
Chris
On 3/22/06, John Panzer [EMAIL PROTECTED] wrote:
I'm starting a discussion about feed licencing w
Angus McIntyre wrote:
What's the best course of action in cases like these? My use-case
doesn't exactly fit hAtom because it doesn't meet the mandatory
'author' and 'content' requirements.
I was under the impression that most of these sorts of requirements
are
Couple of minor notes below...
David Janes -- BlogMatrix wrote:
Angus McIntyre wrote:
These lists of articles - which are essentially 'feeds' - seem like
an obvious match for hAtom, so I've tried to make the library produce
hAtom. However, there are some problems.
First, hAtom demands an
Tantek elik wrote:
Greetings,
I've taken the changes proposed and accepted for hReview 0.3 from the
review-brainstorming page and incorporated them into hReview:
http://microformats.org/wiki/hreview
Question:
If reviewer is absent from the hReview, then
look outside the hReview,
in
___
microformats-discuss mailing list
microformats-discuss@microformats.org
http://microformats.org/mailman/listinfo/microformats-discuss
--
John Panzer
Sr. Technical Manager
http://journals.aol.com/panzerjohn/abstractioneer
Paul Bryson wrote:
John Panzer wrote...
Yep, in the usages I've seen, people tend to use either the name or the
individual ticker symbol interchangeably in text. That is, the
difference between Buy Time Warner now! and Buy TWX now! seems to be
mostly a matter of style;
Microformats
to the Wiki page. Here's the logical structure I
think is needed:
ticker
symbol (required)
exchange (required)
(possibly) country (definitely not required)
All of which can be marked up using abbr if necessary.
OK, off to http://microformats.org/wiki/stock-symbol-examples.
--
John Panzer
Sr
Ryan King wrote on 2/1/2006, 3:49 PM:
On Feb 1, 2006, at 2:27 PM, John Panzer wrote:
...
One goal is to ensure that the human readable content is able to
remain the same as today.
I'm not sure what the significance of this statement is.
In order to evangelize microformats, it's
Tantek Çelik wrote:
On 2/1/06 2:27 PM, John Panzer [EMAIL PROTECTED] wrote:
Would this be acceptable as a structured fn?
a class=item fn href=...abbr title=NYSE:TWXTime Warner,
Inc./abbr/a
Well, you could use that markup, but there are several questionable things
going on here.
...
2. Both
eptable in some cases; it's useful to have a way to declare
up front what the requirements are. Having a way to say "this site is
compatible with hSkin 1.1 (_javascript_ OK)" in a machine readable way
might be useful.
As an aside, of course we're working have this operate smoothly wi
As Tantek suggsted, I started a page documenting some of the potential
examples for aggregate reviews here:
http://microformats.org/wiki/aggregate-review-examples
Please add additional examples if you have any -- I'll look for some
more but have negative spare time right now.
-John
seem appropriate.) Of course I can simply make up a
unique URL per ticker symbol easily enough, but that seems hacky. Any
thoughts?
--
John Panzer
Sr Technical Manager, AOL
http://journals.aol.com/panzerjohn/abstractioneer
___
microformats-discuss
else's work.
--
John Panzer
Sr. Technical Manager
http://journals.aol.com/panzerjohn/abstractioneer
[1]
http://journals.aol.com/hilaryonstocks/hilaryonstocks
___
microformats-discuss mailing list
microformats-discuss@microformats.org
http
25 matches
Mail list logo
