On 1 Apr 2005, at 19:52, Thomas Broyer wrote:
Henry Story wrote:
On 1 Apr 2005, at 14:53, Eric Scheid wrote:
Prior art in other specs says the relationship is from where the link is
found, and to the thing at @href.
I think we are agreeing here.
The link is from the representation "<entry>....</entry>" to the resource identified by the href. That is what proposal A says, I think.

Not for me...

Taking back Eric's example:
<entry>
...
<link rel="http://example.org/rels#next";
href="http://example.net/somethingelse.atom"; />
...
</entry>
My interpretation is that "...somethingelse.atom" is the next (entry or whatever is defined by the @rel value herein) from the point of view of the entry containing the link element.

ok. <...somethingelse.atom> would be the next resource. Though I think the next
link was meant for feeds, and has been moved over to the API document. So it is
a little unfortunate to be basing your argument on an example that is not in the
spec, and that if it were would be attached to the feed.


If you replace the @rel with @rel="alternate", then "...somethingelse.atom" is an alternate representation of "me" ("me" being the entry carrying the link element).

no. <...omething.else.atom> is a resource, not a representation [1].
So what you mean to say is that <...somethingelse.atom> is an alternate resource
of me. But that won't do since "me" is a representation. Hence what we have to say
is that "me" is an alternate representation of the <...somethingelse.atom> resource.


Now you example is also a little confusing because the type of object that should be
at the end of an "alternate" link, would usually not be an atom document, but an html
document. So let us for the sake of clarity replace <...somethingelse.atom> by
<...somethingelse.html> at the same time as we move from "next" to "alternate"


If you want to say that the entry is an alternate representation of the thing at @href, then (re)introduce the rev attribute: @rev="alternate", meaning "I am an alternate representation of the thing at @href" where "I" is the entry carrying the link element.

I really don't see the problem

   "<entry>...</entry>" ---alternate---> <..else.html>

think of it as a short hand for

   "<entry>...</entry>" ---alternate-representation-of---> <..else.html>

You don't have to switch the directions of the arrows for this to be correct. As you
see it is a relation from representation to resource.


Perhaps you are thinking "alternate-representation-of" is some causal relationship
and so the arrow points from the resource to the entry representation. Since it is
easy to think of as the resources (in http land at least) as causing their
representation.


But there clearly need be no such causal relation at all between the resource at
<..else.html> and the "<entry>...</entry>" representation. <..else.html> may
be a resource that only produces html representation of it. It is none the
less true that the entry may be an "alternative" representation of that resource.
The relationship is logical not causal.


One could also think of the @rel="alternate" as a bi-di relation: "we" (the entry carrying the link element and the thing at @href) are alternate representations of the same thing, without telling which is the "primary" representation (maybe neither of both is, maybe the primary representation does not have any IRI). This means that @rel="alternate" has the same meaning as @rev="alternate".

(Again I think here you are mislead by thinking of the realtion as a causal one.)


One can't quite think of it as a bi-directional relationship, since the
relation is  asymmetric.

"<entry>...</entry>" ---alternate-representation-of---> <..else.html>

 works, but

<..else.html> ---alternate-representation-of---> "<entry>...</entry>"

does not. <..else.html> is not a representation, it is a resource. [1]

Well, finally, I'll go for the last... As we are looking at the relation from the point of view of the entry carrying the link element, it is clear that the thing at @href is an alternate representation of the entry that we know of,

yes

but it is not defined that the "primary" representation might be the entry nor that the thing at @href knows of the entry as an alternate representation of itself,

Here we are!
As I said above this is not a causal relationship. We are not saying that
the <entry>...</entry> representation is "known" by the hrefed resource, that it
can produce it, or anything like that. We are just saying that it is an alternative
representation (alternative is happily quite vague) of the remote resource.


whichever is the "primary" representation... Well, in a few words: they are alternate representations of the same thing.

"They" meaning what?
<...else.html> and "<entry>...</entry>" are not both representations only the second
one is.


what you mean is that <...else.html> has many representations. Some of these are html
ones that it produces, others are atom ones that are produced by others. We have something
like this


<...else.html> ---representation---> "<html><body>...</body></html>"
      |-----------representation---> "<xhtml><body>...</body></xhtml>"
      |
      |-----------representation---> "<entry>...</entry>"


If we now distinguish between cause and uncaused ones (call crep and rep)


<...else.html> ---crep---> "<html><body>...</body></html>"
      |-----------crep---> "<xhtml><body>...</body></xhtml>"
      |                           ^
      |                           |
      |                        similar
      |                           |
      |-----------rep---> "<entry>...</entry>"

now "similar" is indeed a bi-directional representation. And I think you
are speaking of the similar relation just illustrated.

So to summarize the whole argument in a graph:

<<inline: Atom-related.jpg>>


we have three alternate relations
-spec6:alternate is currently what the spec says
-A:alternate is the one of my proposal A
-tom:alternate is the relation you mention above between two representations.
Notice that I should really draw tom:alternate as relation between
the "<entry>...</entry>" representation and each one of the "<html>..." and
"<xhtml>..." representations. The problem is that it would not be helpful
to express a relation between the different representations as we don't have
a good handle (name) on them.


So as I explained in previous posts, the problem with spec6:alternate is that the
relation is too strong.
In the graph I show some nodes in yellow and others in green. The green nodes
are grouped together because they represent a later stage in time when <..else.html>
was displaced to <displaced.html>. As a result perhaps a few links had to
be changed in the html and xhtml, and so <displaced.html> has different html and xhtml
representations. It also comes with a different "<entry>...</entry>" representation
(which has a different timestamp for example) and a different A:alternate relation.
But the id of both "<entry>..." representations is the same.
Now to say that we want a spec6:alternate relation would say that the <urn:uuid..>
resource is an alternate to <..else.html>, which it is not really. That would seem to
say that the later "<entry>..." representation is also in the same sense a spec6:alternate
to <else.html>. I think we are much clearer by sticking to A:alternate.



Same goes for @rel="related": both things are related. This is told by the entry carrying the link element. The thing at @href might not know it is related to this entry. As for "alternate", @rel="related" has the same meaning as @rev="related".

rel:related is a different relation. I have not checked carefully what I think of it yet.
But there is nothing a priori wrong with relations that relate the id of the entry to
another resource. We just have to ask carefully if that is what the authors of the spec
really intended.



This is because "alternate" and "related" don't define a direction to the relationship.
If you bring back the "next" relationship, it defines a direction which is read "from the entry carrying the link element to the thing at @href", it defines what is the thing at @href related to the entry: it is the "next".


In other words, with link elements, the entry says "hey, this is an alternate", or "hey, this is related", or "hey, this is the next". Here, I use "an" for alternate and related and "the" for next because *I* have defined the "next" relationship as being a one-to-one.

I think I have made my point as clearly as I can now. Let me know if that explanation
has helped.


Henry Story
http://bblfish.net/blog/

[1] http://www.w3.org/TR/webarch/#id-resources

Reply via email to