Am Donnerstag, 21. Dezember 2006 01:57 schrieb Mike Schinkel:
Thanks for the comment, but I wasn't able to figure out what point you were
trying to make.
Were you saying that Microformats will develop to be a standard? If that
was your point, I don't debate it; I expect it. But w/o
Am Samstag, 16. Dezember 2006 08:31 schrieb Mike Schinkel:
You are making an invalid assumption which is that I'm concerned about my
markup. No, I'm not. I've concerned about the need for a standard to be
created so that a body of knowledge and tools can be developed around that
body of
Siegfried Gipp wrote:
Am Samstag, 16. Dezember 2006 08:31 schrieb Mike Schinkel:
You are making an invalid assumption which is that
I'm concerned about my markup. No, I'm not. I've
concerned about the need for a standard to be
created so that a body of knowledge and tools can
be
Siegfried Gipp wrote:
You don't need the custom: prefix. Anyone can define
his/her own relationships. BTW, there are more relationships
than between persons. Think of rel=prev, rel=next,
rel=contents, ...
So if you need your own relations for whatever, simply use
them. It's just it is no
Am Mittwoch, 13. Dezember 2006 22:22 schrieb Mike Schinkel:
As an aside, at the risk of starting a firestorm, it would be nice if there
were a way to let the user decide his one relationship, i.e. maybe
a rel=custom: href=...John Smith/a
Where is of course the person's one
On 12/12/06, Angus McIntyre [EMAIL PROTECTED] wrote:
On Tue, December 12, 2006 5:05 pm, Andy Mabbett wrote:
In message [EMAIL PROTECTED], Mike Schinkel
[EMAIL PROTECTED] writes
OTOH, I could use any of the following if attached to professional:
Respect, admire, impressed by,awed, revere,
On 12/11/06, Tim White [EMAIL PROTECTED] wrote:
To address the poster's concerns, address is a block-level element, not
inline,
This would seem to contradict that?
http://www.w3.org/TR/html4/struct/global.html#h-7.5.6
I've stayed away from using address on some of my pages precisely
because
Am Mittwoch, 13. Dezember 2006 10:11 schrieb Ciaran McNulty:
On 12/11/06, Tim White [EMAIL PROTECTED] wrote:
To address the poster's concerns, address is a block-level element, not
inline,
This would seem to contradict that?
http://www.w3.org/TR/html4/struct/global.html#h-7.5.6
I've
On 12/13/06, Siegfried Gipp [EMAIL PROTECTED] wrote:
address is an element designed to contain contact information. So if you
want to include contact information use address. That is indepenent of
using hCard or not. address is a html element, specified by the w3c, hCard
is an attribute
Ciaran,
On 12/11/06, Tim White [EMAIL PROTECTED] wrote:
To address the poster's concerns, address is a block-level
element, not inline,
This would seem to contradict that?
http://www.w3.org/TR/html4/struct/global.html#h-7.5.6
I've stayed away from using address on some of my pages precisely
On 12/13/06, Tim White [EMAIL PROTECTED] wrote:
I believe that the (%inline) refers to what address can contain -- inline
elements. See same structure for headings:
http://www.w3.org/TR/html4/struct/global.html#h-7.5.5
Aha, that sounds probable (apologies to Siegfried).
The fact it can't
On 13 Dec 2006, at 11:53, Ciaran McNulty wrote:
so my pages don't validate correctly if I add address
Actually, it's more severe than just not validating. Nesting block
level elements within ADDRESS triggers error-handling in browsers,
such that the DOM does not reflect your mark-up.
The fact it can't contain block level elements still makes it unusable
for my needs though (I can't fit my hCard into entirely inline
elements, so my pages don't validate correctly if I add address).
-Ciaran
But you can still use hCard -- just wrap it in something else (div
id=hcard/div).
Am Mittwoch, 13. Dezember 2006 12:53 schrieb Ciaran McNulty:
On 12/13/06, Tim White [EMAIL PROTECTED] wrote:
I believe that the (%inline) refers to what address can contain --
inline elements. See same structure for headings:
http://www.w3.org/TR/html4/struct/global.html#h-7.5.5
Aha, that
In message
[EMAIL PROTECTED], Ciaran
McNulty [EMAIL PROTECTED] writes
On 12/12/06, Andy Mabbett [EMAIL PROTECTED] wrote:
Not to mention: mentor, mentee, trainer, trainee,
I would suspect that mentor, trainer would suffice, with then
@rev=mentor and @rev=trainer providing the reciprocal
On 13 Dec 2006, at 18:29, Andy Mabbett wrote:
I thought rev was in the process of being deprecated?
I do hope not; I'm quite a fan of the little blighter. Do you have a
URL for that?
___
microformats-discuss mailing list
In message [EMAIL PROTECTED], Ben
Ward [EMAIL PROTECTED] writes
On 13 Dec 2006, at 18:29, Andy Mabbett wrote:
I thought rev was in the process of being deprecated?
I do hope not; I'm quite a fan of the little blighter. Do you have a
URL for that?
No, but it was recently discussed here, IIRC.
Search the list -- Tantek has made related statements.
I too like the idea of the rev attribute, but it's potentially a crap
shoot as there's so little behavior for it to be semi-worthless.
The idea of XBN is one we've explored previously as well
(x-business-network). Again, try searching.
I always find it interesting how on a mailing list someone can make a simple
comment with a pretty small scope and then have the community run with it,
misinterpretting the original comment or suggestion, expanding its scope,
and then debating and often even criticizing the assuming original
In message
[EMAIL PROTECTED], Chris
Messina [EMAIL PROTECTED] writes
While
'colleague' and 'co-worker' are a good start, they don't capture
'former-employer', 'client', 'consultant' or much else.
The goal is not to describe all relationship variations, but common
ones that are shared between
As an aside, at the risk of starting a firestorm, it would be nice if there
were a way to let the user decide his one relationship, i.e. maybe
a rel=custom: href=...John Smith/a
Where is of course the person's one identifier. Basically this would
allow people to create a folksonomy.
In message [EMAIL PROTECTED], Mike Schinkel
[EMAIL PROTECTED] writes
I would like to propose that we add to XFN respect in the
professional category, or some other similar term which the community
decides is more appropriate, and increment the version to 1.2.
I'm curious in the absence of rev,
Andy Mabbett wrote:
In message [EMAIL PROTECTED], Mike Schinkel
[EMAIL PROTECTED] writes
I would like to propose that we add to XFN respect in the
professional category, or some other similar term which the community
decides is more appropriate, and increment the version to 1.2.
I'm
In message [EMAIL PROTECTED], Rob O'Rourke
[EMAIL PROTECTED] writes
I'm curious in the absence of rev, what would be the reverse
relationship of respect?
rel=diss
Ah, but that's the opposite, not the reverse.
--
Andy Mabbett
* Say NO! to compulsory ID Cards:
Aren't claims that you are respected by ___ kind of arrogant? Is a
reverse useful? It's one thing for someone to claim they respect
another, and another thing entirely to claim to be respected.
On 12/13/06, Andy Mabbett [EMAIL PROTECTED] wrote:
In message [EMAIL PROTECTED], Rob O'Rourke
On Dec 13, 2006, at 10:39 AM, Ben Ward wrote:
On 13 Dec 2006, at 18:29, Andy Mabbett wrote:
I thought rev was in the process of being deprecated?
I do hope not; I'm quite a fan of the little blighter. Do you have
a URL for that?
Currently it's not in HTML5. To be conservative, I don't
Andy Mabbett wrote:
In message [EMAIL PROTECTED], Rob O'Rourke
[EMAIL PROTECTED] writes
I'm curious in the absence of rev, what would be the reverse
relationship of respect?
rel=diss
Ah, but that's the opposite, not the reverse.
Thats just my misunderstanding, sorry for
In message [EMAIL PROTECTED], Mike Schinkel
[EMAIL PROTECTED] writes
OTOH, I could use any of the following if attached to professional:
Respect, admire, impressed by,awed, revere, worship, idolize, iconize.
If would be nice if there was a way to extend professional respect and
admiration.
Not
In message
[EMAIL PROTECTED], Angus
McIntyre [EMAIL PROTECTED] writes
If we start encoding not only hierarchical relations but expressions of
approval/disapproval, you have the possibility to write some extremely
career-limiting XFN expressions.
a href=... rel=colleague boss despise ... /a
I should think that:
a href=... rel=spouse despise ... /a
might cause some trouble, too! ;-)
It would probably have a reciprocal:
a href=... rel=spouse sleeping-on-couch ... /a
;)
--
--- http://www.200ok.com.au/
--- The future has arrived; it's just not
--- evenly distributed. - William
In message [EMAIL PROTECTED], Tantek Çelik
[EMAIL PROTECTED] writes
Subject: Re: XFN usage stats and Re: [uf-discuss] rel=muse
implies romantic relationship?
Did you perhaps forget to change that?
microformats do not try to alter people's publishing behavior in an
unnatural way - and ask
In message [EMAIL PROTECTED], Tim
White [EMAIL PROTECTED] writes
Perhaps you missed this comment:
http://microformats.org/wiki?title=hresume-feedbackcurid=1777diff=0oldid=11198rcid=20574
in which a poster describes how he rejected hResume because it sought to
change his publishing
Tantek Çelik wrote:
Aside - this entire thread particularly warms my heart - it's been a while
since we've had a serious but light-hearted topic, and clearly the time had
come.
Jason Garber, welcome to the list, and thanks for a much appreciated bit of
levity on a weekend afternoon.
Anytime!
On Dec 10, 2006, at 6:08 PM, Chris Messina wrote:
And despite my attempts to explain, as you all have, the origins of
the romantic sense of the term, Tara never gave me the benefit of
the doubt, hence the semantic change. ;)
So yes, Tantek, a FAQ entry would certainly be appreciated.
Have a
34 matches
Mail list logo
