In message
[EMAIL PROTECTED], Ara
Pehlivanian [EMAIL PROTECTED] writes
I've always had trouble with the idea of using abbr to mark up dates
because semantically, it isn't expressing an abbreviation of any sort.
That's particularly true of:
abbr class=dtend title=2007-04-0130 March/abbr
In message [EMAIL PROTECTED], Bob Jonkman
[EMAIL PROTECTED] writes
Andy Mabbett suggested a class of dtstamp which comes closer to what
I intend, but the iCalendar property DTSTAMP is specifically meant to
indicate when an iCalendar object was created, which is not the case
here.
Fair
In message [EMAIL PROTECTED], Paul Wilkins [EMAIL PROTECTED]
writes
This is for both for screen readers and disabiguation of dates such as
3/2/2006 or 02-03-06.
That's an important consideration.
As I'm to believe, screen readers will read out both parts of the date
information. As such,
In message [EMAIL PROTECTED], Paul Wilkins
[EMAIL PROTECTED] writes
you might write the date as 4/7/76 and force the reader to find and
use the abbreviation, but as someone who cares enough to create a
datetime design pattern, it should be obvious that writing the date as
July 4, 1776 solves
This is all relevant to existing specific-purpose date-time
properties,
[snip]
What exactly would we want
to do with a generic date apart from any specific context?
Well, blog posts and articles online come to mind. They're normally
dated, yet there's no convention that states that this is
Bob Jonkman wrote:
I simply want dates occuring within
prose to be recognized as machine-readable dates.
Why do you want them to eb recognised as machine readable dates? What
problem will it solve for the machines?
This is for both for screen readers and
disabiguation of dates such as
On 3/8/07, Bob Jonkman [EMAIL PROTECTED] wrote:
snip
These are arbitrary dates, NOT related to the publishing date of the document
it appears in,
not related to any resources such as a software release. I simply want dates
occuring within
prose to be recognized as machine-readable dates.
On Mar 9, 2007, at 9:10 AM, Ara Pehlivanian wrote:
I've always had trouble with the idea of using abbr to mark up dates
because semantically, it isn't expressing an abbreviation of any sort.
I think the confusion here is that we're actually using
abbreviation more semantically than
On 3/9/07, Scott Reynen [EMAIL PROTECTED] wrote:
On Mar 9, 2007, at 9:10 AM, Ara Pehlivanian wrote:
I think the confusion here is that we're actually using
abbreviation more semantically than literally. That is, it's not
the character count that's abbreviated; it's the meaning.
All of the
This is what microformats-discuss@microformats.org said
about Re: [uf-discuss] Formatting arbitra on 7 Mar 2007 at 14:39
From: James Craig
In this case, I think what you are looking for is the 'datetime'
attribute on INS and DEL elements.
ins datetime=2007-03-055 March 2007/ins
On 07.03.2007, at 00:37, Tantek Çelik wrote:
Question: would the community be ok with a draft approximate
property list
for hCalendar sooner than a comprehensive precise property list later?
Personally I'd prefer a draft list that can be gradually improved
until it becomes
the final,
http://microformats.org/wiki/to-do#hCalendar_2
Question: would the community be ok with a draft approximate
property list
for hCalendar sooner than a comprehensive precise property list later?
Apologizing in advance for not following any (possibly) existing
volunteer procedure, I've done
On 07/03/07, Alexander Graf [EMAIL PROTECTED] wrote:
On 07.03.2007, at 00:37, Tantek Çelik wrote:
Question: would the community be ok with a draft approximate
property list
for hCalendar sooner than a comprehensive precise property list later?
Personally I'd prefer a draft list that can be
Bob Jonkman wrote:
Hi all: Today I had the urge to mark up an arbitrary date, not one
that is part of
an hCalendar event, eg.
Use version 7.0.2 from abbr title=2007-03-055 March 2007/span
This is to provide some standarization in presenting dates, but
keep them human-
readable in
In message [EMAIL PROTECTED], Bob Jonkman
[EMAIL PROTECTED] writes
Today I had the urge to mark up an arbitrary date, not one that is part
of an hCalendar event, eg.
Use version 7.0.2 from abbr title=2007-03-055 March 2007/span
This is to provide some standarization in presenting dates,
In message [EMAIL PROTECTED], Bob Jonkman
[EMAIL PROTECTED] writes
dtstart and dtend aren't appropriate semantic classes in this example.
Is there a proper microformat for arbitrary dates?
P.S.
What about class=dtstamp ?
Which, I notice is missing from:
On 3/6/07 12:32 PM, Andy Mabbett [EMAIL PROTECTED] wrote:
Which, I notice is missing from:
http://microformats.org/wiki/hcalendar-cheatsheet
What properties should it have there?
This is an excellent question, and one that has been raised before (by Andy
and others, i.e. where is
From: James Craig [EMAIL PROTECTED]
In this case, I think what you are looking for is the 'datetime'
attribute on INS and DEL elements.
ins datetime=2007-03-055 March 2007/ins
This has nothing to do with microformats; it's just semantic HTML. It
specifies the time of the insertion or
Paul Wilkins wrote:
While it specifies the time of insertion or deletion, the semantics
of that don't match up with what we're wanting to do here.
Unless you and Bob are working on that project together, the
semantics of the use can only be determined by Bob.
The INS and DEL elements are
From: James Craig [EMAIL PROTECTED]
While it specifies the time of insertion or deletion, the semantics of
that don't match up with what we're wanting to do here.
Unless you and Bob are working on that project together, the semantics of
the use can only be determined by Bob.
The semantics
From: James Craig [EMAIL PROTECTED]
Given that, you might also want to specify the URI for version changes.
ins cite=/whatsnew/7.0.2/ datetime=2007-03-05Use version 7.0.2
from 5 March 2007./ins
My apologies James, I see that we're both approaching the same answer from
different
Question: would the community be ok with a draft approximate property list
for hCalendar sooner than a comprehensive precise property list later?
My standards/implementation instincts had biased me towards the latter, but
I realize that in many ways, ironically, that's actually contrary to much
Bob Jonkman wrote:
Hi all: Today I had the urge to mark up an arbitrary date, not one that is part of
an hCalendar event, eg.
Use version 7.0.2 from abbr title=2007-03-055 March 2007/span
This is to provide some standarization in presenting dates, but keep them human-
readable in arbitrary
23 matches
Mail list logo
