In message [EMAIL PROTECTED], Ryan
King [EMAIL PROTECTED] writes
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.
On 10/22/06, Ciaran McNulty [EMAIL PROTECTED] wrote:
Consider a scenario where someone has saved a page locally, or is
viewing it through a cache such as Google's, it'd be a mistake to
infer the URL as C:\Temp\whatever, for instance.
These are edge cases, but worth thinking about.
--- i would
On Oct 21, 2006, at 8:29 AM, Andy Mabbett 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.
Why not
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
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
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
Isn't address supposed to contain contact information for the page itself?
On 10/21/06, Andy Mabbett [EMAIL PROTECTED] wrote:
I seem to remember mentioning this before, but can't find where I did
so, nor any responses.
It seems to me that there should be some way to say that the URL of an
