describes the relationship from the current document to the anchor
specified by the href attribute[2]
nsfw describes the authors opinion of the nature of the content to
be found at the end of the link, and by no means the nature of the
relationships between the destination and source documents.
On Jan 1, 2007, at 2:18 AM, Ben Buchanan wrote:
I'm not immediately convinced that it isn't it a relationship. NSFW
would formalise the fact that document A:
1) contains a link to document B
2) document A's author considers document B not safe for work by
their own standards
This isn't a
In message [EMAIL PROTECTED], Colin
Barrett [EMAIL PROTECTED] writes
Tagging is probably a better uF for this, IMO. I like the idea, but
someone pointed out (before the post on this list) that it's the wrong
semantics for @rel. For the semantic web to go further, we really do
need to respect the
On Dec 31, 2006, at 1:44 PM, Mike Schinkel wrote:
Exactly. The only use-case I forsee is for blog footnotes. There
may be
others, but in the spirit of going with existing markup, using for
a blog is
what I'm currently[1] doing.
Some examples of footnoting and endnoting can be found in:
On Jan 1, 2007, at 5:51 AM, Andy Mabbett wrote:
I thought tagging was for tagging the current page, not labelling a
link
to a second page.
It could be expanded to include links? -- I don't know a whole lot
about it, it was suggested in the discussion I had with someone where
it was
On 1/1/07, Colin Barrett [EMAIL PROTECTED] wrote:
On Jan 1, 2007, at 5:51 AM, Andy Mabbett wrote:
I thought tagging was for tagging the current page, not labelling a
link
to a second page.
It could be expanded to include links? -- I don't know a whole lot
about it, it was suggested in the
On Jan 1, 2007, at 7:29 AM, Ciaran McNulty wrote:
On 1/1/07, Colin Barrett [EMAIL PROTECTED] wrote:
On Jan 1, 2007, at 5:51 AM, Andy Mabbett wrote:
I thought tagging was for tagging the current page, not labelling a
link
to a second page.
It could be expanded to include links? -- I don't
In message
[EMAIL PROTECTED], Ciaran
McNulty [EMAIL PROTECTED] writes
Another @rel value that is more similar to the @rel=nsfw would be
@rel=no-follow, which is trying to express an opinion about the
linked page rather than describing the link relationship.
Having re-read the original content
Andy said:
Having re-read the original content rating discussion, it's clear that
the initial proposal was for a uF for ratings of a current page, for
which tagging was, not unreasonably, suggested.
The current proposal is for a method of rating (in a very loose sense)
the page which is
In message [EMAIL PROTECTED], Eran
[EMAIL PROTECTED] writes
The current proposal is for a method of rating (in a very loose sense)
the page which is being linked to, and for which tagging is not
appropriate.
I haven't followed the entire thread but this seems like a good use
case for xfolk
The 'wiki' page on xFolk:
http://microformats.org/wiki/xFolk
says:
If you need to define tags as part of a more specialised
format, rel=tag is the recommended way to do so, and xFolk,
hReview, hCard and hCalendar all do this.
Yet there is no mention of this,
On 1/1/07, Colin Barrett [EMAIL PROTECTED] wrote:
On Jan 1, 2007, at 7:29 AM, Ciaran McNulty wrote:
Another @rel value that is more similar to the @rel=nsfw would be
@rel=no-follow, which is trying to express an opinion about the
linked page rather than describing the link relationship.
Not
Andy said:
The xfolk version could look like this:
div class=xfolkentry
a class=taggedlinked href=http://goatse.cx;check this out!/a
(a rel=tag href=http://en.wikipedia.org/wiki/NSFW;NSFW/a)/div
That would also tag the *linking* page as NSFW.
(In fact, that seems to be an issue
On 1/1/07, Eran [EMAIL PROTECTED] wrote:
That last sentence pretty much leaves all interpretation of scope to the
application. In a blog the scope is usually a single post (even if several
posts appear on the same page), in hReview it is the product (or the rating
for the product) and in xFolk
In message [EMAIL PROTECTED], Eran
[EMAIL PROTECTED] writes
The xfolk version could look like this:
div class=xfolkentry
a class=taggedlinked href=http://goatse.cx;check this out!/a
(a rel=tag href=http://en.wikipedia.org/wiki/NSFW;NSFW/a)/div
That would also tag the *linking* page as
Ben,
I'm not immediately convinced that it isn't it a relationship. NSFW
would formalise the fact that document A:
1) contains a link to document B
2) document A's author considers document B not safe for work by
their own standards
at best you could make the argument that rev=nsfw is
16 matches
Mail list logo
