In message [EMAIL PROTECTED],
Benjamin West [EMAIL PROTECTED] writes
I noticed a page for plants at
http://microformats.org/wiki/plant. This was a little confusing to
me. Is species insufficient?
Insufficient for what?
Has any work been done on the plant proposal, since March? Was there
any
On IRC recently, in
http://rbach.priv.at/Microformats-IRC/2006-10-22#T000157 Tantek wrote:
one of the big question (sic) for species in my mind is what should
the microformats approach be in general to the publishing and sharing
of scientific knowledge?
and, shortly afterwards, in
On 10/21/06, Andy Mabbett [EMAIL PROTECTED] wrote:
It seems to me that there should be some way to say that the URL of an
hCard or hCalendar event is the URL of the page itself, without having
to include a redundant, and accessibility-damaging link to that page, on
the page itself.
Or has
Hi Folks,
I sent this message a couple days ago and got no response, so I am
resending. Does anyone have thoughts on the issue I raised? /Roger
-Original Message-
From: Costello, Roger L.
Sent: Friday, October 20, 2006 12:02 PM
To: microformats-discuss@microformats.org
Subject:
On 22/10/06, Andy Mabbett [EMAIL PROTECTED] wrote:
All plants are species, and can be scientifically classified as such.
Not all species are plants-for-sale, requiring a cultivation regime.
A classic example of one of the differences between plants and species
is that of the Potato (Solanum
On Oct 21, 2006, at 8:46 PM, Bruce D'Arcus wrote:
Well, actually, title is not going to be included, because of the
no-namespace problem. E.g. it would conflict with hCard title,
which is different. But fn is essentially used to achieve the same
thing (if really awkwardly).
Thanks for
On 10/22/06, Costello, Roger L. [EMAIL PROTECTED] wrote:
Hi Folks,
I am reading the vCard specification (RFC 2426) and there seems to be
some disconnects between it and the hCard specification.
Terminology
RFC 2426 uses the terminology type, e.g., FN Type
hCard uses the terminology
On 10/22/06, Jeremy Boggs [EMAIL PROTECTED] wrote:
One issue that comes up: When citing art, the life span of the
creator is given. I notice that vCard/hCard does not have a way to
mark up date of death, but does have date of birth. Are there
thoughts on how to account for this? I've used
Hi all,
I'm giving a presentation on Microformats as they relate to mashups and
DOM scripting at The AJAX Experience on Tuesday and would love it if
some folks could take a look at my presentation and give me some
feedback/suggestions - Especially if I've missed:
1. Existing
In message [EMAIL PROTECTED],
Brian Suda [EMAIL PROTECTED] writes
On 10/21/06, Andy Mabbett [EMAIL PROTECTED] wrote:
It seems to me that there should be some way to say that the URL of an
hCard or hCalendar event is the URL of the page itself, without having
to include a redundant, and
In message
[EMAIL PROTECTED], Charles
Roper [EMAIL PROTECTED] writes
A classic example of one of the differences between plants and species
is that of the Potato (Solanum tuberosum). Now, Solanum tuberosum is a
species. Most of the potatos you buy in shops are Solanum tuberosum.
All are, surely
On 10/22/06, Andy Mabbett [EMAIL PROTECTED] wrote:
Thank you. That's probably the best fix for the situation I describe;
but it does require a change to the page, which is not supposed to be
required by uFs.
One of the key factors in microformats is to keep the data visible
URL-of-current-page
On 10/21/06, Charles Roper [EMAIL PROTECTED] wrote:
Can anyone give any real *disadvantages* to using output compression?
The choice to use compression is one of bandwidth vs. processing time.
I have personally had a bad experience with a cut-rate ISP who had
some sort of CPU-usage throttling
On 22/10/06, Andy Mabbett [EMAIL PROTECTED] wrote:
A classic example of one of the differences between plants and species
is that of the Potato (Solanum tuberosum). Now, Solanum tuberosum is a
species. Most of the potatos you buy in shops are Solanum tuberosum.
All are, surely (unless you're
I've updated the straw-man proposal for species [1], to reflect the
consensus not to use these abbreviations:
sci
var (variety)
bin (binominal)
cult(cultivar)
cname (common name; common used, instead)
but what about these:
subsp
On 22/10/06, Andy Mabbett [EMAIL PROTECTED] wrote:
bin (binominal)
Binominal or binomial? A discussion on the subject here:
http://tinyurl.com/tptsh
cname (common name; common used, instead)
Common seems like a very common term. How about vernacular instead?
but
In message
[EMAIL PROTECTED], Charles
Roper [EMAIL PROTECTED] writes
span class=biota [1]
abbr class=binominal title=Solanum tuberosum
span class=variety [2]
Maris Piper
/span
/abbr
/span
I'm not at all
In message
[EMAIL PROTECTED], Benjamin
West [EMAIL PROTECTED] writes
My main concern is that none of
the examples (that I've looked through so far), with the exception of
Andy's site, use any markup that looks anything like this.
I'm not clear what you're asking for - pages that already use a
In message
[EMAIL PROTECTED], Charles
Roper [EMAIL PROTECTED] writes
bin (binominal)
Binominal or binomial? A discussion on the subject here:
http://tinyurl.com/tptsh
I'm ambivalent; but another taxonomist advised me, in e-mail, to avoid
binomial, as that is also used in
This is catered for, in the current proposal, thus:
span class=biota [1]
abbr class=binominal title=Solanum tuberosum
span class=variety [2]
Maris Piper
/span
/abbr
/span
Allow me to simplify my earlier post.
On Oct 22, 2006, at 10:46 AM, Brian Suda wrote:
there was a long thread about it last April, you can read through
the archives:
http://microformats.org/discuss/mail/microformats-discuss/2006-
April/003703.html
i don't think much was agreed upon, but ideas were certainly floated.
Ah,
Andy,
Perhaps you could be more clear about what it is you want to know.
...
What do you mean by authoring practices?
...
What do you mean by the structure of the markup?
...
I don't know how to be any more clear. I've assumed up until now that
everyone had a relatively shared meaning of
I've just been reading up on the include-pattern, with a view to using
it in one of my events pages.
This section on the i-p page says:
http://microformats.org/wiki/include-pattern#Specifications_Using
says that hCalendar is only considering using it; and the linked FAQ
page doesn't exist.
In message
[EMAIL PROTECTED], Benjamin
West [EMAIL PROTECTED] writes
It reflects current publishing practice as precisely and completely as
possible ...
I'm still wondering how it does so.
I'm not sure what else I can tell you.
Have you find a reference to a living thing, in the context of
It reflects current publishing practice as precisely and completely as
possible ...
I'm still wondering how it does so.
I'm not sure what else I can tell you.
Perhaps we have different understandings of some words? We must not
be sharing some crucial foundational concepts. Allow me to
In message
[EMAIL PROTECTED], Benjamin
West [EMAIL PROTECTED] writes
It reflects current publishing practice as precisely and completely as
possible ...
I'm still wondering how it does so.
I'm not sure what else I can tell you.
Perhaps we have different understandings of some words? We
Wanted to suggest an idea to promote learning-over-time and adding
value to the list and IRC archives (I'd have created a few examples to
demonstrate, but copy-paste and linking isn't convenient on the
Blackberry yet).
Anyway, at key decision points or to illuminate certain seemingly
arbitrary
Yes, I was thinking of something like this. We can think of a given
microformat as being at some place along a spectrum that ranges from:
not thought of, interesting/compelling, rejected, needs work,
documenting examples, brainstorming, official, drafts, iterations...
and so on. I agree that we
28 matches
Mail list logo
