In message [EMAIL PROTECTED], Joe Andrieu
[EMAIL PROTECTED] writes
Andy,
Your political bias is
...in your imagination.
--
Andy Mabbett
Say NO! to compulsory ID Cards: http://www.no2id.net/
Free Our Data: http://www.freeourdata.org.uk
In message [EMAIL PROTECTED],
Chris Casciano [EMAIL PROTECTED] writes
How about this as a model:
date is an optional component of the currency microformat.
When date is present, parsers may disregard it.
When parsers understand date, and none is present, they may
On Sep 24, 2006, at 10:01 PM, Andy Mabbett wrote:
In message [EMAIL PROTECTED], Joe Andrieu
[EMAIL PROTECTED] writes
Andy,
Your political bias is
...in your imagination.
Andy, it seems to me that you've come increasingly more hostile to
members of this list in the past few days. Maybe
should be fixed :)
On 9/22/06, Andy Mabbett [EMAIL PROTECTED] wrote:
In message [EMAIL PROTECTED],
Stephen Paul Weber [EMAIL PROTECTED] writes
The first http://xoxotools.ning.com/hatom2rss.php is my site, I will
look into making your requested tweak to the script :)
No charge ;-)
(Seriously
Ah, with class=tag I think I'm beginning to see the light ;) Still
not #1 on parsability, but microformats never are, it should be doable
though :)
On 9/23/06, Chris Messina [EMAIL PROTECTED] wrote:
I was using class=tagcloud on the containing ul.
I also was using class=tag on each tag link,
In current Safari, object data=20050125January 25/object works
just fine as expected.
Yes, but abbr just makes more sense
1) because it's a better match to what the XHTML actually means
2) because abbr data is visible to users without viewing the code,
object is not (usually)
Those with microformat use experiance are more likely to understand uF
in general, and better at it, so I would definately agree with this
idea.
On 9/24/06, Andy Mabbett [EMAIL PROTECTED] wrote:
In message [EMAIL PROTECTED], Tantek Çelik
[EMAIL PROTECTED] writes
I came here some months ago,
As most folks have some sort of Blogroll (hopefully marked-up with XFN
and XOXO[1]). I have begun to look into easily converting those into
OPML. I've only worked with OPML for a day now and it has left a sour
taste in my mouth!!! So i never want to write OPML again, instead i
want to write happy
you might want to check out http://xoxotools.ning.com/outlineconvert.php
On 9/25/06, Brian Suda [EMAIL PROTECTED] wrote:
As most folks have some sort of Blogroll (hopefully marked-up with XFN
and XOXO[1]). I have begun to look into easily converting those into
OPML. I've only worked with OPML
Hi,
I've hCal'd a website that contains with this kind of dtend :
abbr class=dtend title=2006-09-24T02:00:00+02:00.../abbr
and feeds.technorati.com/events/ convert it to
DTEND:20060924T000Z
with se7en 0 instead of six.
Test it from there :
Good catch! i had a look at the issue and the problem was that all our
test cases added the time from the timezone up to 24, in your
case you were subtracting to get '0' which was not being checked for
so things were going padded then that '0' was being added so we got
'7' instead of '6'.
Hi List,
On Sep 24, 2006, at 10:45 PM, Tantek Çelik wrote:
Another thought is that the space of historical data is probably
a more
relevant way to discuss this than just currency. People assert all
kinds of
facts about the past (not just currency), and rather than having
something
that is
In current Safari, object data=20050125January 25/object works
just fine as expected.
Yes, but abbr just makes more sense
1) because it's a better match to what the XHTML actually means
2) because abbr data is visible to users without viewing the code,
object is not (usually)
Hi, so the
I wrote this a few months ago, but haven't had time to look at since. YMMV :)
http://dietrich.ganx4.com/microformats/xoxo2opml.xsl
On 9/25/06, Brian Suda [EMAIL PROTECTED] wrote:
As most folks have some sort of Blogroll (hopefully marked-up with XFN
and XOXO[1]). I have begun to look into
Hi List,
On Sep 24, 2006, at 10:45 PM, Tantek Çelik wrote:
Another thought is that the space of historical data is probably
a more
relevant way to discuss this than just currency. People assert all
kinds of
facts about the past (not just currency), and rather than having
something
that
excellent! looking at the code, we pretty much arrived at the same
thing - what license do you plan on releasing this as? and when you
finish you should add it to the Implementations list on the Wiki.
what i'd really like is to find out, via Lazy Web, what and if any,
New Readers can accept XOXO
In message
[EMAIL PROTECTED], Stephen
Paul Weber [EMAIL PROTECTED] writes
On 9/22/06, Andy Mabbett [EMAIL PROTECTED] wrote:
In message [EMAIL PROTECTED],
Stephen Paul Weber [EMAIL PROTECTED] writes
The first http://xoxotools.ning.com/hatom2rss.php is my site, I will
look into making your
In message [EMAIL PROTECTED], Colin
Barrett [EMAIL PROTECTED] writes
In message [EMAIL PROTECTED], Joe Andrieu
[EMAIL PROTECTED] writes
Andy,
Your political bias is
...in your imagination.
Andy, it seems to me that you've come increasingly more hostile to
members of this list in the past
In message [EMAIL PROTECTED], Andy Mabbett
[EMAIL PROTECTED] writes
The first http://xoxotools.ning.com/hatom2rss.php is my site, I will
look into making your requested tweak to the script :)
should be fixed :)
Thank you. Viewing the feed for:
I've just been looking over the IRC logs. One of my recent edits to the
Wiki shows as:
[10:12:07] mfbot [[species-examples]]
http://microformats.org/wiki?title=species-examplesdiff=0oldid=8949
* AndyMabbett * (+391) Quantitative evidence - Wikispecies
To what does +391
Andy Mabbett a écrit :
I've just been looking over the IRC logs. One of my recent edits to the
Wiki shows as:
[10:12:07] mfbot [[species-examples]]
http://microformats.org/wiki?title=species-examplesdiff=0oldid=8949
* AndyMabbett * (+391) Quantitative evidence -
that is the number of characters you added (or subtracted) in this case +391.
We use this alot to see of SPAM comes through, if we get a +/- 40,000
that is probably not an edit by a person.
-brian
On 9/25/06, Andy Mabbett [EMAIL PROTECTED] wrote:
I've just been looking over the IRC logs. One
At 04:29 PM 2006-09-19, Ryan King wrote:
Sounds like a use case for URIs [1]
Life would be better if URI's were used in more places.
I do not want to invent a new URI Scheme (bad idea per W3C TAG [1]).
[1] http://tinyurl.com/roao2
and/or UIDs [2].
It also sounds like a very specific use
At 04:29 PM 2006-09-19, Ryan King wrote:
Create your own
standard markup
If I create my own, then it may be my standard, but its a far cry
from being a widespread or universal standard.
I am not in the group in my company that develops the applications
that use employee numbers. I am a
In message [EMAIL PROTECTED], Frederic de Villamil
[EMAIL PROTECTED] writes
To what does +391 refer?
The amount of chars you've added on the page.
Thank you, both.
--
Andy Mabbett
Say NO! to compulsory ID Cards: http://www.no2id.net/
Free Our Data:
I just took a look through the citation-brainstorming page to see
what's next, and saw Brian (Suda?)'s list of outstanding issues from a
while ago. I thought I'd start a thread of discussion for each, to see
if we can resolve them.
Issue one is how to mark up UIDs because there are so many
continuing the series... Brian's second outstanding issue with citation:
2) I keep mis-using format, format is the medium - hardback,
softback. The TYPE (there probably is a better word - container?) is
book, article, conference, manifesto, etc. Much like the identifers we
can make an enumerated
Michael McCracken mumbled the following on 25/09/2006 23:05:
I do agree that using an element with type class instead of a huge
number of type classes is the way to go here, to avoid class namespace
pollution.
Comments?
I agree. It follows one of the principles of Minimising Vocabulary, and
Nesting microformats - there are two questions here.
First, about the statement that other uf's don't handle nesting
explicitly. Is this a design decision or just a result of it not being
necessary yet?
Second - the two options listed don't seem like enough.
option 1: requires class names for
This has already been done twice by Les Orchard:
http://decafbad.com/trac/wiki/XoxoOutliner
http://decafbad.com/blog/2005/12/01/feedrolls-in-xoxo-from-opml-via-xslt-and-url-line-magic
http://decafbad.com/2005/11/gopher-ng/xoxo-to-hyperscope.xsl
I don't think my code always does a flat OPML... only if the original
XOXO was flat... I'll look into processing XOXO that has relative
URLs
On 9/25/06, Brian Suda [EMAIL PROTECTED] wrote:
excellent! looking at the code, we pretty much arrived at the same
thing - what license do you plan on
For the first item, it didn't help that your page was not quite valid
http://validator.w3.org/check?uri=http%3A%2F%2Fwww.westmidlandbirdclub.com%2Fnew.htm,
however I think I have fixed it now anyway and got around that :)
The url must have the xn_auth=no in it (ning hosting), but I have
removed
On 9/25/06, Michael McCracken [EMAIL PROTECTED] wrote:
I do agree that using an element with type class instead of a huge
number of type classes is the way to go here, to avoid class namespace
pollution.
I actually don't like using the separate element, in part because this
information is
First, a URL for the wiki page you are referring to would be helpful ;-)
On 9/25/06, Michael McCracken [EMAIL PROTECTED] wrote:
option 1: requires class names for every reference type. I don't like
this option either.
option 2: uses type class, but makes it confusing IMO - what if you
want to
Sorry, it was hinted at in the first email- I should have included it in each:
http://microformats.org/wiki/citation-brainstorming#Outstanding_Issues
On 9/25/06, Bruce D'Arcus [EMAIL PROTECTED] wrote:
First, a URL for the wiki page you are referring to would be helpful ;-)
On 9/25/06, Michael
Hello,
I was wondering if there had every been any serious thought to
giving individual microformats logos (for widgets and buttons and
such, etc). I created an XOXO logo back when I started the XOXO Blog
http://photos1.blogger.com/blogger/6537/1341/1600/XOXObadge.png. An
aquaintance recently
Just about this part:
I have no opinion about citation vs. hcite.
-mike
http://microformats.org/wiki/naming-principles#h_word
That page suggests that hcite for the root element is the way to go.
-mike
--
Michael McCracken
UCSD CSE PhD Candidate
research: http://www.cse.ucsd.edu/~mmccrack/
On 9/25/06, Bruce D'Arcus [EMAIL PROTECTED] wrote:
On 9/25/06, Michael McCracken [EMAIL PROTECTED] wrote:
I do agree that using an element with type class instead of a huge
number of type classes is the way to go here, to avoid class namespace
pollution.
I actually don't like using the
On Sep 25, 2006, at 4:58 PM, Michael McCracken wrote:
I like Brian's suggestion to use a type class to denote what type of
UID it is while avoiding a huge list of new class names.
span class=uidspan class=typeDOI/span: a class=value
href=http://dx.doi.org/stuff;.../a/span
It seems like this
On 9/25/06, Scott Reynen [EMAIL PROTECTED] wrote:
On Sep 25, 2006, at 4:58 PM, Michael McCracken wrote:
I like Brian's suggestion to use a type class to denote what type of
UID it is while avoiding a huge list of new class names.
span class=uidspan class=typeDOI/span: a class=value
On Sep 25, 2006, at 7:35 PM, Michael McCracken wrote:
I know what you mean - the type matters in how you format the
reference, but it isn't usually displayed. This is something we'll
have to hammer out. Right now it looks like a tradeoff between
flexibility and elegance, but I'm hoping for a
On 9/25/06, Scott Reynen [EMAIL PROTECTED] wrote:
On Sep 25, 2006, at 7:35 PM, Michael McCracken wrote:
I know what you mean - the type matters in how you format the
reference, but it isn't usually displayed. This is something we'll
have to hammer out. Right now it looks like a tradeoff
On 9/25/06, Michael McCracken [EMAIL PROTECTED] wrote:
The option of just ignoring types altogether - not including a type
property at all - is certainly possible - it would make human-reading
and publishing easier but automatic parsing somewhat harder. This
might be a worthwhile tradeoff.
I
On 9/25/06, Ross Singer [EMAIL PROTECTED] wrote:
On 9/25/06, Michael McCracken [EMAIL PROTECTED] wrote:
The option of just ignoring types altogether - not including a type
property at all - is certainly possible - it would make human-reading
and publishing easier but automatic parsing
44 matches
Mail list logo
