On 10/19/06, Andy Mabbett [EMAIL PROTECTED] wrote:
It appears that, nowhere on the Wiki, is the concept of a
design-pattern defined or explained.
Design Patterns aren't a uF-specific concept.
Maybe rather than trying to write a definition, a link out to
Wikipedia or somewhere similar would
Scott Reynen wrote:
Who is publishing 10 columns and 100 rows of prices or something
similar? It would be helpful to look at some real-world markup so we
can come up with practical ways to address this concern. If it's in
rows and columns, I would assume each price to be in a td, so span
Mike Schinkel wrote:
Has there been any thought to try and survey the web development community
at large on these types of issues? I could see the value of having a lot of
these types of questions answered if we were do present surveys (of course
hopefully we could find a surveying expert to
The point I am trying to make is this: file size *is* an issue, but it is
not an insurmountable problem and can be solved through technology and good
design; file size shouldn't compromise the semantics and design of a
microformat.
Since I was the one that originally called the question I want
Andy Mabbett wrote:
Is is considered better to have longer, easier-to-read, more
descriptive, more semantically correct attribute values over shorter,
more concise, bandwidth-saving ones?
Its not the length, its what you do with it ;-)
As in all things, it's a matter of balance.
Yes, I
Okay... Did I just make more work for myself? :)
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Charles
Roper
Sent: Thursday, October 19, 2006 3:45 AM
To: Microformats Discuss
Subject: Re: [uf-discuss] Size considerations
Mike Schinkel wrote:
Has
On Oct 18, 2006, at 6:09 PM, Andy Mabbett wrote:
That's 399 characters increased to 860 (excluding indentation); over
double.
when gzipped (with indentation) I get 308 bytes vs 498 ration 1.62
Stripping out the indentation and CRs and using more compact forms of
the mf markup I get
tr
On 10/18/06, Mike Schinkel [EMAIL PROTECTED] wrote:
However, at the risk of being shot for heresy, has anyone considered allowing
this?
abbr class=currency usd$5.99/abbr
abbr class=currency dkk35.66 kr/abbr
--- one of the main goals of microformats is to make data Human
On 10/19/06, Brian Suda [EMAIL PROTECTED] wrote:
I personally like this idea:
span class=moneyabbr class=currency title=USD$/abbrspan
class=amount5.99/span/span
It has worked well for ADR, TEL, EMAIL in hCard and is also being
explored for UIDs.
I like that idea too, there've been a few
On Oct 18, 2006, at 6:18 AM, Jeremy Boggs wrote:
...
My concern stems from the idea that there's a difference between
simply listing or referring to a work, and citing it as an
authority. If I'm writing a blog post critiquing Holocaust deniers,
I may, say, reference a book arguing that
In message
[EMAIL PROTECTED], Ciaran
McNulty [EMAIL PROTECTED] writes
Andy Mabbett wrote:
As I noted on the Wiki a few hours ago, it's not clear, either from the
main Wiki page or include-pattern, whether the latter is an agreed
standard, a draft, or just a proposal.
It is currently
The initial design-patterns ... and I know because I wrote them ...
were distillations of existing practices. Include breaks this pattern
only slightly, but was a reasonable isolation of a unit of work from
hResume (I believe)
Regards, etc...
David
On 10/19/06, Andy Mabbett [EMAIL PROTECTED]
On 10/19/06 11:29 AM, Ryan King [EMAIL PROTECTED] wrote:
On Oct 18, 2006, at 6:29 AM, Ciaran McNulty wrote:
In iCal (and therefore presumably hCal), the following rule applies
for events that lack a DTEND or DURATION:
For
cases where a VEVENT calendar component specifies a DTSTART
In message [EMAIL PROTECTED], Kevin
Marks [EMAIL PROTECTED] writes
using more compact forms of the mf markup I get
Other than the 20061103T213000Z format for dates, what did you change?
gzipped I get 293 vs 451 ratio 1.51
So - still an increase of over 50%.
That's not insignificant.
--
Andy
In message [EMAIL PROTECTED], Charles Roper
[EMAIL PROTECTED] writes
I raised the point, as you no doubt know, in response to the Species
brainstorming on the wiki [1]; specifically this:
Should bin, var, cult, etc., be written in full? (I think not, to
save bloating file sizes)
These
On Oct 19, 2006, at 11:58 AM, Andy Mabbett wrote:
In message [EMAIL PROTECTED], Kevin
Marks [EMAIL PROTECTED] writes
using more compact forms of the mf markup I get
Other than the 20061103T213000Z format for dates, what did you
change?
I removed a redundant 'title'.
gzipped I get 293
In message
[EMAIL PROTECTED], David
Janes [EMAIL PROTECTED] writes
The initial design-patterns ... and I know because I wrote them ...
were distillations of existing practices. Include breaks this pattern
only slightly, but was a reasonable isolation of a unit of work from
hResume (I believe)
I responded to your immediately previous message by giving the list
the history of how the existing design patterns came into existence.
IMHO, I'm not sure if it's something crying out for, or would be
benefit from, more formality or process.
Regards, etc...
David
On 10/19/06, Andy Mabbett
In message [EMAIL PROTECTED], Kevin
Marks [EMAIL PROTECTED] writes
Other than the 20061103T213000Z format for dates, what did you
change?
I removed a redundant 'title'.
You removed the title from:
a href=../solihull/indoor.htm
title=Solihull Branch indoor meetings
In message [EMAIL PROTECTED], Mike Schinkel
[EMAIL PROTECTED] writes
I'm coming to believe that there are some very different assumed goals
use-cases among the people in discussions (not because of anything
specific, just a feeling I have.) Without clarifying these, I think
we'll be at cross
Hey guys,
If I was trying to mark up some events with hCalendar, the date was in the h2,
and there were multiple events under the h2, how would I mark it up?
Like here:
http://www.loc.gov/loc/events/index.php
How do I get the one date to point to multiple events?
Cheers,
Justin Thorp
In message [EMAIL PROTECTED],
Lucas Gonze [EMAIL PROTECTED] writes
I was inspired by your project to do this write up:
http://gonze.com/weblog/story/prettyuri
At work, we refer to them as human friendly URLs. 'Nuff said!
--
Andy Mabbett
Say NO! to compulsory ID Cards:
On Oct 19, 2006, at 12:43 PM, Andy Mabbett wrote:
In itself, it's not significant, as it is well under a packet size, as
I said, and so will not affect download time.
Why is packet size relevant? The page concerned has many - and some
have
dozens - of table rows in similar format.
Good!
Unfortunately I don't think ISO8061 has a way of representing 'now' -
the only thing I could suggest would be that you set it equal to the
document's publication date, maybe using PHP as you suggest.
Thanks Ciaran!
It seems, though, that setting the dtend date to the document's
publication
Agreed, for now, this is an excellent point to start:
http://microformats.org/wiki/hresume-issues
Thanks for setting this up, Tantek. So, if we want to discuss further
issues with this problem, should we post them there, on that wiki
page, or continue making comments through email? A
In message [EMAIL PROTECTED], Kevin
Marks [EMAIL PROTECTED] writes
Good! Do you have before and after versions?
Sadly not - I took the opportunity to re-write and restructure the pages
at the same time as I applied uFs.
I could retroactively manufacture some, but the would just be a number
of
On 10/19/06 3:27 PM, Jeremy Boggs [EMAIL PROTECTED] wrote:
Agreed, for now, this is an excellent point to start:
http://microformats.org/wiki/hresume-issues
Thanks for setting this up, Tantek. So, if we want to discuss further
issues with this problem, should we post them there, on that
IMO it implies that you were employed during those times, I'm not
sure whether it implies you're *not* employed after the DTEND...
This, IMO, seems problematic. From a human point of view, people
would probably understand that abbr title=20061017
class=dtendpresent/abbr mean that I'm still
In message [EMAIL PROTECTED] Charles Roper
[EMAIL PROTECTED] in addition to other things said:
Should bin, var, cult, etc., be written in full? (I think not, to
save bloating file sizes)
These abbreviations are absolutely fine within the very narrow domain of
biological nomenclature and
The point I am trying to make is abbreviations can be very dangerous and
are very easy to mis-interpret so I think we need to think long and hard
before choosing and implementing them. I am not arguing against them in
specific cases but very well thought out cases.
I have a question about
Hi all:
I was just emailing with someone who's company offers software as a service
and I was encouraging him to adopt Microformats including hCard and
hCalendar. His response to me was:
The good news is Apple in on our board, which means CalDAV would be the
standard we'd employ.
CalDEV:
I was just emailing with someone who's company offers software as a
service
and I was encouraging him to adopt Microformats including hCard and
hCalendar. His response to me was:
The good news is Apple in on our board, which means CalDAV would be
the
standard we'd employ.
CalDEV:
On Oct 19, 2006, at 8:18 PM, Mike Schinkel wrote:
The good news is Apple in on our board, which means CalDAV would
be the
standard we'd employ.
CalDEV: http://ietf.osafoundation.org/caldav/
Now, it's my understanding that one of the benefits of Microformats is
that
it co-exists nicely
Hi, I've been following this discussion and I would like to add that
you might even get more characters than commas and periods inside an
ammount (which would make the regexp even more complex).. according to
this guide http://www.thefinancials.com/vortex/CurrencyFormats.html
you might have: '
This gives me a chance to ask in a different way, why can we not assume
type=USD, amount=5.99, and symbol=$ from the following?
The book costs span class=currency title=USD$5.99/span
That example in particular might not be a problem but consider the following:
span class=currency
--- one of the main goals of microformats is to make data Human Readable.
Which means visible. In your examples the USD and DKK values are no longer
human readable values
FYI, my examples were meant in the case where USD wasn't part of the visible
HTML prior to Microformat markup. If it was
Hey Mike,
This is an very good/interesting example...
In my opinion amount is a really difficult one to abbreviate (or any measure
for that matter) as it can be used to describe a lot of other things for
which there is not yet a microformat but cur (for currency) is interesting
as just off the
37 matches
Mail list logo
