Henry Story wrote:
On 1 Apr 2005, at 19:52, Thomas Broyer wrote:
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.

This is not the same "next" relationship...

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.

Well, feeds also carry link elements with a possible "alternate" value for their rel attribute...

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.

Ok, I finally understand what you mean...

Actually, the problem is applying "alternate version" to "resource" rather than "representation of a resource".

What about:
[[
The value "alternate" signifies that the IRI in the value of the href attribute identifies a resource whose representations are an alternate version of the resource described by the containing 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>

But the former one says (fmpov) something like "...else.html" is an alternate of "entry" while the latter says "entry" is an alternate (representation) of "...else.html".
You are switching the directions of the meanings (ok, without switching the directions of the arrow... that's something like active/passive forms in grammar)


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.

yes

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.

The problem with the web-arch "language" is that once you print a web page (a representation of a resource), it (the printed sheets) is not the same resource any more (if I understand correctly). Though the still are resources/representations/call-how-you-want of the same "thing".


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.

Yes, but why not call it "alternate"?

--
Thomas Broyer



Reply via email to