Thank you Karl for this short, proselytism-free answer.
Guillaume
Karl Dubost wrote:
Guillaume,
Le 22 juil. 06 à 08:35, Guillaume Lebleu a écrit :
why the approach has evolved to become the following class
attribute-approach:
[...]
instead of the following mixed-namespace approach
Looks like there are many others:
There are various common abbreviations to distinguish the Canadian
dollar from others: while the ISO
http://en.wikipedia.org/wiki/International_Organization_for_Standardization
currency code http://en.wikipedia.org/wiki/ISO_4217 *CAD* (a
three-character code
.
Guillaume
Andy Mabbett wrote:
In message [EMAIL PROTECTED], Guillaume Lebleu
[EMAIL PROTECTED] writes
Looks like there are many others:
There are various common abbreviations to distinguish the Canadian
dollar from others: while the ISO http://en.wikipedia.org/wiki/Interna
Should the currency amount mF proposal include support for
representation of currency-qualified values in a table format?
If so, take a look at: http://investor.google.com/fin_data.html
As you can see, it would not make sense to have the currency repeated
for each piece of data. Instead, it
Andy,
My take on the introductory message:
http://microformats.org/wiki/what-are-microformats#Guillaume_Lebleu
Guillaume
Andy Mabbett wrote:
I have just had an e-mail from a friend, to whom I'd recommended uFs:
Just had a quick look at http://microformats.org but they only
A correction to one of my code samples:
span class=pricespan class=currencyamountabbr
class=unitcurrency title=USD$/abbr25/span a abbr class=unit
title=barrelbarrel/abbr/span.
Guillaume
Guillaume Lebleu wrote:
Sorry if I'm only getting up-to-speed on this debate.
I agree that attaching
:
p class=lenght
abbr class=unit title=meterm/abbr span class=value10,5/span
/p
Thanks for your opinion :-)
On 9/27/06, Scott Reynen [EMAIL PROTECTED] wrote:
On Sep 27, 2006, at 2:21 PM, Guillaume Lebleu wrote:
span class=pricespan class=currencyamountabbr
class=unitcurrency title=USD$/abbr25
I don't think Lorenzo is talking of: *currency amount per item/product*
as your title and example imply (that, I agree, is a non-starter)
but of *currency amount per unit of measurement* (which is widely used -
see for instance: http://www.bloomberg.com/energy/, although not in the
context of
One little correction in the text below.
The following rules should be used:
* unit is optional
* if unit is present, then value is optional, and if value not
present, then it is assumed to be 1.
Guillaume
Guillaume Lebleu wrote:
I don't think Lorenzo is talking of: *currency amount
, for instance the domain name
.ca to disambiguate the $ sign.
Once we found more real examples, we can resume discussions here on this
subject.
Let me know what you think.
Guillaume
Scott Reynen wrote:
On Sep 29, 2006, at 5:09 PM, Guillaume Lebleu wrote:
I don't think Lorenzo
I have had a really hard time finding currency examples on the Web using
something else/more than the price class name to qualify currency
amounts (I wish there was a search engine for HTML source code).
Actually, I haven't found any (only one is documented on the
I took a look at the semantics used by XBRL for currency amounts (a
standard for corporate financial reporting pushed among others by the SEC).
I have made an adaptation of them in semantic XHTML:
http://microformats.org/wiki/currency-formats#XBRL (without
incorporating existing thoughts on
microformat.
Peace,
Guillaume
Scott Reynen wrote:
On Sep 29, 2006, at 5:09 PM, Guillaume Lebleu wrote:
I don't think Lorenzo is talking of: *currency amount per
item/product* as your title and example imply (that, I agree, is a
non-starter)
but of *currency amount per unit
Here are some additional examples from the Web of currency mixed with
measures, some of which differ from the $__ per barrel pattern and a
suggested new conceptualization that seems to work with them.
http://microformats.org/wiki/currency-examples#Real-World_Examples
Here is another
Scott Reynen wrote:
I think this is a good example of the benefits of modularization. I
think all of these various measurements would be more useful if they
were more widely published, and I think the best way to get them
widely published is to keep them as separate microformats addressing
Colin wrote:
This proposal is shaping up nicely. Could you think of other client
uses for just the measurement format? Already described in this thread
were some excellent uses for measurement + currency (e.g. searching
job listings).
Thanks Colin. For just the measurement format, of course
Colin wrote:
This proposal is shaping up nicely. Could you think of other client
uses for just the measurement format? Already described in this thread
were some excellent uses for measurement + currency (e.g. searching
job listings).
Thanks Colin. For just the measurement format, of course
Ryan King wrote:
I think it's good practice, not just for hCalendar, but for all web
content to create permalinks which are independent of things like
pagination. If you can do that, then pagination shouldn't be a problem.
Maybe I'm missing something, but instead of a new UID element with a
Please find it at: http://microformats.org/wiki/currency-proposal
Thank you in advance for your feedback.
Guillaume
___
microformats-discuss mailing list
microformats-discuss@microformats.org
King Chung Huang wrote:
Is currency unit intended to be one whole name or two names?
My intention is to have 2 class names, one for the currency (ex. U.S.
currency), and one for the unit within that currency (ex. Dollar, Cent).
unit is optional, b/c most currencies have a default unit
Scott Reynen wrote:
Specifically, I don't think it makes sense to have the first abbr
tag with no title, and the second abbr with no content. It looks
like you're trying to communicate three different pieces of
information when only two are really being published.
Thank you for the
Scott Reynen wrote:
What I'm suggesting is that everything be treated as dollars in USD
and everything be treated as Yen in JPY. Isn't that how most
applications and people deal with money anyway?
I think this will indeed work in most cases.
There are some examples on the Web that make use
Hello,
I thought that to expand feedback on the Currency proposal, a simple
poll would be nice, so here it is:
http://www.vizu.com/poll-vote.html?n=15067
Note: choices are randomly ordered.
Looking forward to your participation.
Guillaume
___
Scott Reynen wrote:
So which of these tasks should we aim to make simple? I'd say the
latter, because it's far more common (well over 80%, I think).
I think we agree here. $99 is more common than 99c, so the former should
be simpler to microformat than the latter. Where it seems we differ in
I thought I'd share these results with you. Voters were asked to select
up to 4 features in a list of 8.
We only had a handful of votes so far, so please cast yours at:
http://www.vizu.com/poll-vote.html?n=15067
Features deemed most important:
1. (100%) Currency used identification (ex.
Scott Reynen wrote:
span class=moneyabbr class=amount title=0./abbrabbr
class=currency title=USD¢/abbr/span
My bad. I had missed the title=0.99 part earlier. This will work for
all currency amounts of recent times, as all currencies are now
officially or de facto decimalized (UK was one
Ted Drake wrote:
I would thin this standard could be adopted quickly via microformats. What
are the thoughts?
I think microformats would probably help adoption with the less
sophisticated (smaller) retailers quickly, but would not satisfy all the
business needs of more sophisticated
Mike Schinkel wrote:
* Currency symbol identification from other part of the text
This means that in $25 dollars, we would mark up $ as the currency
symbol. See
http://microformats.org/wiki/currency-brainstorming#Andy_Mabbett under
symbol bullet for an explanation of this.
* Global
In my previous table example, you should read:
tr
th scope=colpricea href=#u1 class=include/a/th
/tr
tr
td24/td
/tr
Guillaume
___
microformats-discuss mailing list
microformats-discuss@microformats.org
See below the results for What do you think are the [4] most important
features [out of 8] for the currency proposal?
Thank you to all who have participated.
My recommended next step is to edit the current proposal so that it
focuses only on the 3 top features below, with the goal to get a
Mike Schinkel wrote:
My opinion is this sounds like a great idea! Will you be doing the edit on
the current proposal?
yes, I intend to do before the end of this week.
I am surprised however at the number of people who felt Currency
unit/denomination used identification was important and it
Joe Andrieu wrote:
This may be a fact of test bias. The test asked for four answers, so I
selected four answers, and #4 for me was Currency unit/denomination used.
I didn't really have my heart in it, so to speak.
Sorry for this. You're welcome to change your vote, if you want to. See
The thread around invisble microformats reminded me of this example from
the visible Web. Maybe relevant to this discussion, if not relevant to
the include-pattern.
An index page (http://www.eia.doe.gov/emeu/international/oilprice.html)
contains currency information that applies to all pages
Ryan Cannon wrote:
I'm not sure we want to get into the morass of defining values for TYPE,
but if an identifier is for a specific resource, we should allow a way
to tell which resource it's from.
I have been thinking of identifiers in the context of another standard.
I think this could be a
Does this OpenID+hCard deals with selective privacy? i.e. showing
certain information to only some class of people?
I have tried to solve this problem on my own with something I call
hPrivacy.
I know this is more semantic HTML than Microformats, but I think this
may be relevant to this
Duncan Cragg wrote:
- I would like to drop in a field for the ticker code: NASDAQ:MSFT,
etc; also the SEDOL and ISIN codes.
I would think that stock tickers / security identifiers deserve a
microformat of their own before we can think of aggregating it into
other ones.
I have a bit of
Scott Reynen wrote:
See:
http://microformats.org/wiki/stock-symbol-examples
Sorry I missed this one. I did vaguely remember that something had been
done, but couldn't find it on
http://microformats.org/wiki/exploratory-discussions
What category should it be referenced in? Current ?
Glenn Jones wrote:
It has been built from the ground up to take configuration
objects which allow the parsing of different microformats or POSH
patterns.
Great job Glenn,
I was wondering what the configuration objects look like. Do you use a
grammar for each uf expressed?
Thank you,
Guillaume
Thanks Glenn,
I wonder what you and others think about the following idea.
Since one of your output mechanism is XML, I thought an idea might be to
use XML schema (with possibly uf-specific appinfo
annotations/documentation where relevant) to declare each microformat,
instead of serialized C#
Andy Mabbett wrote:
Because they're the most appropriate semantics;
I don't agree with that, but I'm not going to argue about it.
and because people are already using the long-hand version of hCard to
do so.
vCard is an electronic business cards standard; hCard is not merely an
electronic
Andy Mabbett wrote:
The hCard spec says that:
hCard is a simple, open, distributed format for representing
people, companies, organizations, and places, using a 1:1
representation of vCard (RFC2426) properties and values
note that's NOT:
hCard is a 1:1
Tantek Çelik wrote:
Ah ok, this is what Jeremy Keith refers to as natural language hCards,
wherein you simply markup inline references to people accordingly.
I believe Wikipedia calls these inline hCards, which sounds to me like
a good name.
http://en.wikipedia.org/wiki/Template:Hcard-bday
Manu Sporny wrote:
Constructive feedback would be great, as I'll probably be doing the
advanced RDFa tutorial in a month or so, and will need to know what
worked and what didn't in the RDFa Basics video.
I'm relatively new to RDFa and this is a great introduction. I'm
probably going to say
Andy Mabbett wrote:
When did you last see a listing of, say, Pizza restaurants that labelled
each telephone number as work?
When did you last see a listing of, say, Pizza restaurants that included
the managers' home numbers?
In that same vein, we could ask: when did you last see a phone
Tantek Çelik wrote:
On 1/7/08 5:19 PM, Guillaume Lebleu [EMAIL PROTECTED] wrote:
voice in fact is already default value of the type sub-property for tel:
http://microformats.org/wiki/hcard#adr_tel_email_types
Thanks for the pointer. Sorry I missed that.
Perhaps you could document your
Philip Tellis wrote:
On 08/01/2008, Jim O'Donnell [EMAIL PROTECTED] wrote:
I don't understand this. Why can't type=cell be dialled for voice
calls?
I think the problem is that they can, but SMS short numbers can't.
so should there be a way to distinguish voice enabled
Andy Mabbett wrote:
In that same vein, we could ask: when did you last see a phone number
not being a work number when both a person's formatted name and
organization name were present?
Today - and nearly every time I look at a contact page about someone
who does voluntary work.
Andy,
Andy Mabbett wrote:
In message [EMAIL PROTECTED], Guillaume Lebleu
[EMAIL PROTECTED] writes
In that same vein, we could ask: when did you last see a phone
number not being a work number when both a person's formatted name
and organization name were present?
Today - and nearly every time
Andy Mabbett wrote:
While I'm aware that we're discussing possible changes to vcard,
rather than ways of using the current hCard, I think this is a case
where looking at what people actually publish (and allow for in forms)
on the web; and what address-book apps allow for, would be useful
Philip Tellis wrote:
Would you, for example, put down, preferred from 0900-1700IST, except
on weekends and between the 5th and 15th of May, unless you're signed
up with plan foo on provider bar as meta info for the number?
Here is a real-life example of a similar case (opening hours bound to
Andy Mabbett wrote:
A brainstorm of possible alternative methods of using include in
microformats, avoiding the use of the problematic OBJECT or empty-link
variants:
foo id=birminghamid class=localityBirmingham/foo
then:
foo class=adr birminghamid[...]/foo
What about:
Andy Mabbett wrote:
In message [EMAIL PROTECTED], Guillaume Lebleu
[EMAIL PROTECTED] writes
Andy Mabbett wrote:
A brainstorm of possible alternative methods of using include in
microformats, avoiding the use of the problematic OBJECT or empty-link
variants:
What about
Bob Jonkman wrote:
Via Techdirt [1] I found an interesting project called OpenCalais [2]. It seems designed to
take arbitrary text documents and spit out semantic RDF.
There's absolutely no mention of microformats on the OpenCalais web site, but I can see
incorporating microformat markup
Andy Mabbett wrote:
In message [EMAIL PROTECTED], Manu Sporny
[EMAIL PROTECTED] writes
If you really want to make the distinction between a publisher, a
drummer, a singer, a technician, and someone else, you can always use
an hCard and utilize the role property
That presumes that the roles
content with little context. Guillaume Lebleu.
T(W): 415 408 5856 has less context and more structure than My name is
Guillaume Lebleu. My phone number at the office is 408-5856. My area
code is 415.. The first example is a charm to microformat, the second
one is less so. A semantic extractor
Thom Shannon wrote:
Not sure if anyone's mentioned this before but the new version of Apples
Mail has functionality similar to what microformats is trying to enable
(hCard and hCal)
You can mouse over data in an email like addresses, phone numbers and
dates, then add them to your address
Andy Mabbett wrote:
In message [EMAIL PROTECTED], Robert O'Rourke
[EMAIL PROTECTED] writes
And are groups/bands considered to be an organisation?
Yes:
foo class=fn orgPink Floyd/foo
not least because the alternative:
foo class=fnPink Floyd/foo
would be optimised
Andy Mabbett wrote:
In message [EMAIL PROTECTED], Guillaume Lebleu
[EMAIL PROTECTED] writes
not least because the alternative:
foo class=fnPink Floyd/foo
would be optimised (sic) to have a given name of Pink and a family
name of Floyd.
I don't disagree that groups/bands should
Walter Logeman wrote:
Is there some way to get sliced and diced views of that list? An easy
way for me to publish several lists or to have a list generator of
some sort for viewers?
Walt, not sure if the following will address all your requirements, but
it is a start: I would use an HTML table
Toby A Inkster wrote:
Guillaume Lebleu wrote:
What I have been thinking more and more and what this tells me again is
that the same way we talk of POSH and microformats, we could talk of
plain text or plain old english formats, essentially standardizing how
people write dates, addresses
Toby,
Here is an implementation of what I described in my previous post by
Yahoo. http://shortcuts.yahoo.com/
They offer a Wordpress plugin that detects objects from plain old
english patterns as you write your blog post, then asks you for
disambiguation and whether you want to link to it (to
Brian Suda wrote:
The ideal solution would be for somesort of plugin in the CMS so you
can simply highlight areas and push a button and it will add the
microformatted information
Do you or anyone know of any microformats integration work with TinyMCE
or any insight into why it hasn't happened
Thom Shannon wrote:
What is the response to the privacy argument? As a carefree
technophile I'm happy publishing personal info on the web. But when
you're trying to convince a major social network to add semantics that
makes their users personal information easier to harvest and possibly
Belov, Charles wrote:
I feel it is unreasonable to ask a non-technical person to produce
ISO-format dates/times, so microformats do not produce an acceptable
solution at this time for marking up meeting announcements.
I agree that only an editor extension would make writing ISO-format
Toby A Inkster wrote:
Guillaume Lebleu wrote:
span class=dstart lang=en-usOctober 5, 2004/span
Cognition already supports this as a last ditch attempt at parsing
dates -
Thank you for the attempt.
but I wouldn't recommend it get adopted widely. It's too unreliable;
Why
Belov, Charles wrote:
I'd suggest modifying that to not require the computer to parse the
date. Something like:
span class=dstartm lang=en-usOctober/span span
class=dstartd5/span, span class=dstarty2004/span
+1: DRY-, POSH- and humans first-compatible IMO.
Maybe the following may be POSHer
Glenn Jones wrote:
As the exchange between Ben and Jeremy has shown what is human readable
is up for debate. Having spent far too much time looking at the ISO date
formats they are all readable to me, but I know that's not the case for
everyone else.
We need to expand the discussion and ask
FYI. I've summarized/combined some of the ideas suggested by Glenn
Jones, myself and others here [1].
I will elaborate on some of the details (ex. time) later.
Guillaume
[1]
http://microformats.org/wiki/datetime-design-pattern#Plain_Old_English_alternative_to_ISO_date
Jim O'Donnell wrote:
The recent discussion here about dates has made me wonder if such a
web service woud be useful for microformats parsers. What do others
think?
It seems to me that this type of date extraction might present risks if
used by uf parsers to extract date/time from published
69 matches
Mail list logo
