On 11/2/06, Costello, Roger L. [EMAIL PROTECTED] wrote:
A thought occurred to me with regards to the Design #3 approach. Can I
add information that didn't exist in the original HTML text?
Suppose that this is the original HTML text:
John will be our speaker. Mr. Public will talk about
On 11/1/06, Ryan King [EMAIL PROTECTED] wrote:
1. http://microformats.org/wiki/hcard-faq#nesting-properties (though
that page is for hcard, it applies to everything)
That sounds like something begging to me moved to a more central
location. Should it be in the FAQ, or is there a more general
On 11/1/06, Scott Reynen [EMAIL PROTECTED] wrote:
There is already an established meaning for rev=vote-for, and the
reverse of that doesn't really communicate anything useful.
I don't know about that; I could certainly imagine, say, a proposal
asking people to vote by making blog posts and
Someone can mark up a form as an hCard anyway, regardless of whether
it's in the spec or not. I imagine at least one person has already
tried it after reading this thread, to see what it looks like. Thus,
parsers could be subjected to this construct regardless of whether
it's in the spec.
On 9/25/06, Michael McCracken [EMAIL PROTECTED] wrote:
So suppose I wanted to apply a different style to different types of
vcard properties - for instance to highlight all 'home' phones. Is
there a good way to do that in CSS?
You can always add your own styling hooks to the page to do
On 9/26/06, Andy Mabbett [EMAIL PROTECTED] wrote:
there instead of quot; would
be perfectly legal and solve the problem, the escaped ampersand is my
code escaping out your HTML entities, which the validator then finds
bad because there should be no enitities in a title).
it seems reasonable to
On 8/30/06, Andy Mabbett [EMAIL PROTECTED] wrote:
finnaly, the reviewer hCard is also incorrect:
p id=creditspan class=reviewer vcard fnAndy Mabbett/spanbr
span class=dtreviewed title=200603March 2006/span/p
you need to nest the class=fn inside the class=vcard
p id=credit class=reviewer
On 8/16/06, Michael McCracken [EMAIL PROTECTED] wrote:
Yes, I missed that, it does. I think we'd have to use it as a child
element on the link:
a href=link-to-fulltext class=identifierabbr class=format
title=application/pdfPDF/abbr full text link/a
I think it would be better to mark that up
On 8/17/06, Ciaran McNulty [EMAIL PROTECTED] wrote:
I believe the markup looks something like:
div class=vcard
span class=fnJohn Smith/span can be reached via his secretary
span class=agent vcard
span class=fnJohn Doe/span on
span class=tel020 /span
/span
/div
See
If we're looking for a use case for being able to construct a
hierarchy of vevents, I could imagine it would be useful in a calendar
with a fancy interface: if you're viewing a month at a time, it could
collapse all the presentations down into one event labeled ABC
Conference, but if you zoom in
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. But at the same time, it looks
as if hAtom fits better than anything else.
I was under the impression that most of these sorts
On 3/8/06, Paul Kinlan [EMAIL PROTECTED] wrote:
Hi,
I am quite new to this list, so please excuse me if I am talking nonsense or
if this has been discussed [I have trawled the archives, although only
briefly].
Has a microformat been proposed around Questions and Answers.
There has been
On 2/14/06, Michael McCracken [EMAIL PROTECTED] wrote:
Speaking from my own viewpoint and that of the BibDesk users I've talked to
(generally academics, not librarians - it is a bibtex editor), I think that
a complete resource description framework would be welcome, but probably
overkill.
The
On 2/2/06, Dr. Ernie Prabhakar [EMAIL PROTECTED] wrote:
Review/revise desired pathways for:
New users learning about microformats
Microformat lifecycle
Indeed, it does seem that people new to microformats are often either
entirely unaware of or somewhat confused about the
On 2/2/06, Tantek Çelik [EMAIL PROTECTED] wrote:
I'm a little unclear what you mean by languishing. It seems that not a
day goes by when we (even myself personally) must reference the process to
someone either on the list or in IRC.
I was hunting for the right word there anyways.
They should lean towards plain English, but the results just seem very
dissatisfying. This is why I pointed to the date-principle where the
visible text is human readable and the Title attribute contained information
that was more machine readable than human. As the Title/Alt attribute is
On 12/12/05, C. Hudley [EMAIL PROTECTED] wrote:
On 12/9/05, David Osolkowski [EMAIL PROTECTED] wrote: The tag: URI scheme[1] provides a fairly effective way to generate unique ID's.I believe it is the recommended way to generate GUIDs for Atom[2].
Thus, it seems likely it could be re-used here
/28/howto-atom-id- David Osolkowski
___
microformats-discuss mailing list
microformats-discuss@microformats.org
http://microformats.org/mailman/listinfo/microformats-discuss
On 12/6/05, Andreas Haugstrup [EMAIL PROTECTED] wrote:
On Tue, 06 Dec 2005 14:11:27 +0100, David Janes -- BlogMatrix[EMAIL PROTECTED] wrote: Danny Ayers wrote: On 12/6/05, Andreas Haugstrup
[EMAIL PROTECTED] wrote: Sorry, that was a typo. rel=start gets shown as a home button in the browser.
19 matches
Mail list logo
