On Wed, Dec 17, 2008 at 7:20 AM, Toby A Inkster m...@tobyinkster.co.uk wrote:
Which brings me to the point that this is re-inventing something that RDFa
can already deal with very easily:
img src=photo_of_cow.jpeg rel=meta
resource=metadata_about_photo_of_cow /
This is
On Wed, Dec 17, 2008 at 4:01 PM, Scott Reynen sc...@randomchaos.com wrote:
I can use that same URL as my UID on any site, not just blogs and wikis.
Whenever I find myself stating something that seems obvious like that, I
start to suspect there's some larger misunderstanding underlying the
This is a hasLayout bug in IE. Simply giving 'layout' to either the
LIs or the UL will solve the problem. There are many ways to do this
(applying height, setting the zoom property, using display:block) and
each have their own benefits and drawbacks. For a full explanation
and many possible
I agree with Martin that it's sad we are unable to take advantage of
this attribute where possible. The whole idea of completely ignoring
a tiny piece of semantic markup simply because it's often mis-used in
the wild seems misguided to me. If we (as users of web standards, not
the microformat
The premise that publishers will pick any old format is merely an
assertion with no evidence. Please show us an example somewhere else
where this has happened, or perhaps a better argument than merely
insisting on the obvious truth of it.
The way I see it, if they publish in the wrong
On 4/15/08, Dmitry Baranovskiy [EMAIL PROTECTED] wrote:
Very nice. I was working on creating an ACID test for µf for couple of weeks
now, but in different way. I was trying to find all the edge cases in
parsing any µf. Here is a link:
http://microformatique.com/optimus/test.html It is not
On Wed, Mar 12, 2008 at 1:47 AM, Gustavo [EMAIL PROTECTED] wrote:
I may be wrong - in which case, it's probably a good idea if we see if
Microsoft's OpenService stuff gets implemented anywhere outside of
Internet Explorer 8.
Mike Kaply has produced another microformats-related extension
On Wed, Mar 5, 2008 at 1:45 PM, Ryan King [EMAIL PROTECTED] wrote:
On Mar 5, 2008, at 7:30 AM, Tantek Çelik wrote:
On 3/5/08 5:02 AM, Toby A Inkster [EMAIL PROTECTED] wrote:
However, implied headers like this while lowering the barrier to
entry for
authors, would considerably raise the
I realize that the OBJECT element has lost favor in the
include-pattern due to browser issues. But it provides a @data
attribute which, can be used to specify the location of the object's
data, for instance image data for objects defining images, or more
generally, a serialized form of an object
On 9/5/07, André Luís [EMAIL PROTECTED] wrote:
Hello everyone.
- when the user hovers on the margin-mark, the user-agent should
'target' to the (root?) element (like what's done with the #anchor in
urls) and that would allow the publishers to specify the
looks/highlight accordingly. Like:
An additional reason, is that the address element cannot contain
block-level children, so to have block-level children, you would need a
block-level parent.
Jason
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On
Behalf Of Thom Shannon
Sent: Sunday, February
'validators' will flag empty object elements as
errors if no fallback text is supplied.
Should these issues be listed on the wiki under include-pattern issues, or
on a page as special notes about authoring with the include-pattern?
Jason Karns
~~~
The Ohio State University [www.osu.edu]
Computer
an a element instead of an object element. This is
endorsed in the spec for the pattern, I believe.
On 05/02/2007, at 4:00 PM, Jason Karns wrote:
I have two issues with the include-pattern, though they are
less with
the pattern itself and more with simply implementing it.
1) When
about
JasonJason Karns/a
object data=#firm class=include/object
/span
Parsed vCard
FN: Jason Karns 3AM Productions ???
URL: jason.php
ORG-NAME: 3AM Productions
NOTE: web design firm
My proposal would be to allow any extra hcard classes on the including
object override
14 matches
Mail list logo
