Re: [WSG] REL REV

2005-07-13 Thread Ben Ward
Microformats.org have a nice little item in their FAQ about rel  rev
and some very useful 'plain english' expansions of common rel and rev
relationships. It cetainly cleared a few things up for me!

Ben

On 7/13/05, Patrick H. Lauke [EMAIL PROTECTED] wrote:
 Chris Kennon wrote:
 
  After pouring over endless minutiae, if yet to grasp when and how to
  use link rel=  link rev= after having seen it numerous  times,
  peering at the code of many respected sites.
 
 Right...first of all, I think that out of the two only rel is most
 commonly used, as rev does seem to cause weird logic conundrums and is
 not really necessary in most simple situations.
 
 The HTML 4 spec states:
 
 rel = link-types [CI]
  This attribute describes the relationship from the current document
 to the anchor specified by the href attribute. The value of this
 attribute is a space-separated list of link types.
 
 rev = link-types [CI]
  This attribute is used to describe a reverse link from the anchor
 specified by the href attribute to the current document. The value of
 this attribute is a space-separated list of link types.
 
 http://www.w3.org/TR/html4/struct/links.html#adef-rel
 
 To give an (hopefully clearer) example:
 
 say you have documents that make up a sequence, like separate chapters
 in a book where each document is a chapter, and you want to define the
 relationship between them with LINK elements to say which is previous
 and which is next in the set.
 
 Document1 has a link rel=next to Document2 - Document2 has a
 relationship with me in that it's the next document in the set
 
 Document2 has (although nobody does this) a link rev=next to Document1
 - I have a relationship with Document1 in that *I* am Document1's next
 document in the set
 
 Document2 also has a normal link rel=previous to Document1 -
 Document1 is my previous document in the set
 
 which is reciprocated in Document1 with a link rev=previous to
 Document2 - I am Document2's previous document in the set
 
 You see, the rev is basically used to reciprocate what the rel in the
 other document said.
 
 For simple relationships like this, it's fairly straightforward...but it
 can start being complicated when one document is the glossary and it
 needs to rev to any page that rels to it (every page would have a single
 link rel=glossary, but the glossary page itself would have a link
 rev=glossary for every single page that references it with a
 rel...madness)
 
 In practice, I have never encountered revs in the wild.
 
 Hope this makes some kind of sense...
 
 --
 Patrick H. Lauke
 __
 re·dux (adj.): brought back; returned. used postpositively
 [latin : re-, re- + dux, leader; see duke.]
 www.splintered.co.uk | www.photographia.co.uk
 http://redux.deviantart.com
 __
 Web Standards Project (WaSP) Accessibility Task Force
 http://webstandards.org/
 __
 
 **
 The discussion list for  http://webstandardsgroup.org/
 
  See http://webstandardsgroup.org/mail/guidelines.cfm
  for some hints on posting to the list  getting help
 **
 
 


-- 
http://ben-ward.co.uk
**
The discussion list for  http://webstandardsgroup.org/

 See http://webstandardsgroup.org/mail/guidelines.cfm
 for some hints on posting to the list  getting help
**



Re: [WSG] REL REV

2005-07-13 Thread Chris Kennon

Hi,

Almost grokked, so if I have the following sections:
Home, About, Photos, Contact, Portfolio

Would this structure be correct and needed:
From index page:

link rel=next href=./about.html /
link rel=next href=./photos.html /
link rel=next href=./contact.html /
link rel=next href=./portfolio.html /

From contact page:
link rev=previous rel =home href=./index.html /
link rev=previous rel =about href=./about.html /

On Jul 12, 2005, at 5:02 PM, Patrick H. Lauke wrote:


Chris Kennon wrote:


After pouring over endless minutiae, if yet to grasp when and how  
to  use link rel=  link rev= after having seen it  
numerous  times, peering at the code of many respected sites.




Right...first of all, I think that out of the two only rel is most  
commonly used, as rev does seem to cause weird logic conundrums and  
is not really necessary in most simple situations.


The HTML 4 spec states:

rel = link-types [CI]
This attribute describes the relationship from the current  
document to the anchor specified by the href attribute. The value  
of this attribute is a space-separated list of link types.


rev = link-types [CI]
This attribute is used to describe a reverse link from the  
anchor specified by the href attribute to the current document. The  
value of this attribute is a space-separated list of link types.


http://www.w3.org/TR/html4/struct/links.html#adef-rel

To give an (hopefully clearer) example:

say you have documents that make up a sequence, like separate  
chapters in a book where each document is a chapter, and you want  
to define the relationship between them with LINK elements to say  
which is previous and which is next in the set.


Document1 has a link rel=next to Document2 - Document2 has a  
relationship with me in that it's the next document in the set


Document2 has (although nobody does this) a link rev=next to  
Document1 - I have a relationship with Document1 in that *I* am  
Document1's next document in the set


Document2 also has a normal link rel=previous to Document1 -  
Document1 is my previous document in the set


which is reciprocated in Document1 with a link rev=previous to  
Document2 - I am Document2's previous document in the set


You see, the rev is basically used to reciprocate what the rel in  
the other document said.


For simple relationships like this, it's fairly  
straightforward...but it can start being complicated when one  
document is the glossary and it needs to rev to any page that rels  
to it (every page would have a single link rel=glossary, but the  
glossary page itself would have a link rev=glossary for every  
single page that references it with a rel...madness)


In practice, I have never encountered revs in the wild.

Hope this makes some kind of sense...

--
Patrick H. Lauke
__
re·dux (adj.): brought back; returned. used postpositively
[latin : re-, re- + dux, leader; see duke.]
www.splintered.co.uk | www.photographia.co.uk
http://redux.deviantart.com
__
Web Standards Project (WaSP) Accessibility Task Force
http://webstandards.org/
__

**
The discussion list for  http://webstandardsgroup.org/

See http://webstandardsgroup.org/mail/guidelines.cfm
for some hints on posting to the list  getting help
**



**
The discussion list for  http://webstandardsgroup.org/

See http://webstandardsgroup.org/mail/guidelines.cfm
for some hints on posting to the list  getting help
**



Re: [WSG] REL REV

2005-07-13 Thread Gunlaug Sørtun

Chris Kennon wrote:

After pouring over endless minutiae, if yet to grasp when and how to
 use link rel=  link rev= after having seen it numerous 
times, peering at the code of many respected sites.


If you want to make real world use of link rel=, then this page may
actually tell you how to do it.
http://www.literarymoose.info/-/item/depth-of-sequential-navigation/category/site-design
...use a good browser ;-)

regards
Georg
--
http://www.gunlaug.no
**
The discussion list for  http://webstandardsgroup.org/

See http://webstandardsgroup.org/mail/guidelines.cfm
for some hints on posting to the list  getting help
**



Re: [WSG] REL REV

2005-07-13 Thread Chris Kennon

Hi,

Thanks, good stuff, the page does cut-off after the first diagram in  
Safari 2.0

On Jul 13, 2005, at 10:37 AM, Gunlaug Sørtun wrote:


Chris Kennon wrote:


After pouring over endless minutiae, if yet to grasp when and how to
 use link rel=  link rev= after having seen it numerous  
times, peering at the code of many respected sites.




If you want to make real world use of link rel=, then this page  
may

actually tell you how to do it.
http://www.literarymoose.info/-/item/depth-of-sequential- 
navigation/category/site-design

...use a good browser ;-)

regards
Georg
--
http://www.gunlaug.no
**
The discussion list for  http://webstandardsgroup.org/

See http://webstandardsgroup.org/mail/guidelines.cfm
for some hints on posting to the list  getting help
**



**
The discussion list for  http://webstandardsgroup.org/

See http://webstandardsgroup.org/mail/guidelines.cfm
for some hints on posting to the list  getting help
**



Re: [WSG] REL REV

2005-07-13 Thread dwain

Gunlaug Sørtun wrote:

...use a good browser ;-)


are you referring to opera? ;^)

--
Dwain Alford
[EMAIL PROTECTED]
http://www.alforddesigngroup.com

The artist may use any form which his expression demands;
for his inner impulse must find suitable expression.
Wassily Kandinsky, Concerning The Spiritual In Art
**
The discussion list for  http://webstandardsgroup.org/

See http://webstandardsgroup.org/mail/guidelines.cfm
for some hints on posting to the list  getting help
**



Re: [WSG] REL REV

2005-07-13 Thread Gunlaug Sørtun

[EMAIL PROTECTED] wrote:

Gunlaug Sørtun wrote:


...use a good browser ;-)


are you referring to opera? ;^)


Well, I use Opera, and that site is obviously focused on Opera...
I was however hinting at the fact that that page and the site is not
very IE/win-friendly. I don't think Moose care much about weak browsers.

I haven't tested that site's cross-browser functionality, but Firefox,
and I think most other standard-compliant browsers, should do
just fine on that site - so there are options ;-)


regards
Georg
--
http://www.gunlaug.no
**
The discussion list for  http://webstandardsgroup.org/

See http://webstandardsgroup.org/mail/guidelines.cfm
for some hints on posting to the list  getting help
**



Re:Moose was [WSG] REL REV

2005-07-13 Thread dwain

Gunlaug Sørtun wrote:

Well, I use Opera, and that site is obviously focused on Opera...
I was however hinting at the fact that that page and the site is not
very IE/win-friendly.


i know you prefer opera.  it seems that this would be a good resource 
for dealing with opera problems.  i bookmarked it for that reason. 
thanks for your informative nature.



I don't think Moose care much about weak browsers.


i've been feeling the same way.  i will look at a html/css solution to a 
problem with less thought about ie these days.


regards,
dwain

--
Dwain Alford
[EMAIL PROTECTED]
http://www.alforddesigngroup.com

The artist may use any form which his expression demands;
for his inner impulse must find suitable expression.
Wassily Kandinsky, Concerning The Spiritual In Art
**
The discussion list for  http://webstandardsgroup.org/

See http://webstandardsgroup.org/mail/guidelines.cfm
for some hints on posting to the list  getting help
**



Re: [WSG] REL REV

2005-07-13 Thread Patrick H. Lauke

Chris Kennon wrote:


Almost grokked


Funny, just now reading Heinlein's Stranger in a strange land to brush 
up on my sci-fi classics...anyway...



link rel=next href=./about.html /
link rel=next href=./photos.html /
link rel=next href=./contact.html /
link rel=next href=./portfolio.html /


prev (by the way, my example was wrong as it should indeed be prev, not 
previous as I originally stated) and next should only be used in a 
linear sequence of pages. You can't have a one to many type 
relationship like the above.



 From contact page:
link rev=previous rel =home href=./index.html /
link rev=previous rel =about href=./about.html /


Not quite. As the example is flawed on the first step, let's take 
another one: a 3 page collection (page1, page2, page3):


Page1
link rel=next rev=prev href=page2.html /
(my next page is page2, and i am the prev page of page2)

Page2
link rel=prev rev=next href=page1.html /
(my prev page is page1, and i am the next page of page1)
link rel=next rev=prev href=page3.html /
(my next page is page3, and i am the prev page of page3)

Page3
link rel=prev rev=next href=page2.html /
(my prev page is page2, and i am the next page of page2)

As I said, in practice it's enough (IMHO) to use just rel.

--
Patrick H. Lauke
__
re·dux (adj.): brought back; returned. used postpositively
[latin : re-, re- + dux, leader; see duke.]
www.splintered.co.uk | www.photographia.co.uk
http://redux.deviantart.com
__
Web Standards Project (WaSP) Accessibility Task Force
http://webstandards.org/
__

**
The discussion list for  http://webstandardsgroup.org/

See http://webstandardsgroup.org/mail/guidelines.cfm
for some hints on posting to the list  getting help
**



Re: [WSG] REL REV

2005-07-12 Thread Patrick H. Lauke

Chris Kennon wrote:

After pouring over endless minutiae, if yet to grasp when and how to  
use link rel=  link rev= after having seen it numerous  times, 
peering at the code of many respected sites.


Right...first of all, I think that out of the two only rel is most 
commonly used, as rev does seem to cause weird logic conundrums and is 
not really necessary in most simple situations.


The HTML 4 spec states:

rel = link-types [CI]
This attribute describes the relationship from the current document 
to the anchor specified by the href attribute. The value of this 
attribute is a space-separated list of link types.


rev = link-types [CI]
This attribute is used to describe a reverse link from the anchor 
specified by the href attribute to the current document. The value of 
this attribute is a space-separated list of link types.


http://www.w3.org/TR/html4/struct/links.html#adef-rel

To give an (hopefully clearer) example:

say you have documents that make up a sequence, like separate chapters 
in a book where each document is a chapter, and you want to define the 
relationship between them with LINK elements to say which is previous 
and which is next in the set.


Document1 has a link rel=next to Document2 - Document2 has a 
relationship with me in that it's the next document in the set


Document2 has (although nobody does this) a link rev=next to Document1 
- I have a relationship with Document1 in that *I* am Document1's next 
document in the set


Document2 also has a normal link rel=previous to Document1 - 
Document1 is my previous document in the set


which is reciprocated in Document1 with a link rev=previous to 
Document2 - I am Document2's previous document in the set


You see, the rev is basically used to reciprocate what the rel in the 
other document said.


For simple relationships like this, it's fairly straightforward...but it 
can start being complicated when one document is the glossary and it 
needs to rev to any page that rels to it (every page would have a single 
link rel=glossary, but the glossary page itself would have a link 
rev=glossary for every single page that references it with a 
rel...madness)


In practice, I have never encountered revs in the wild.

Hope this makes some kind of sense...

--
Patrick H. Lauke
__
re·dux (adj.): brought back; returned. used postpositively
[latin : re-, re- + dux, leader; see duke.]
www.splintered.co.uk | www.photographia.co.uk
http://redux.deviantart.com
__
Web Standards Project (WaSP) Accessibility Task Force
http://webstandards.org/
__

**
The discussion list for  http://webstandardsgroup.org/

See http://webstandardsgroup.org/mail/guidelines.cfm
for some hints on posting to the list  getting help
**