Thanks. You explained the distinction between files and resources better
than I did.
I think what I'll do is to specify two different types of contracts for
pURLs: a resource-type contract and a file-type contract, the first one
being the newest version while the second being always the same thing. I
will probably also force the URL to be of a certain form as well to
differentiate between the two.
I-Lin Kuo, Ann Arbor, MI
----Original Message Follows----
From: "Marco Rolappe" <[EMAIL PROTECTED]>
I think you're mixing up the concepts of files and resources.
persistent URLs should AFAIR bind to resources, which in turn may represent
a file (and may redirect to a URL for that file, or something like that).
example (contrived):
http://cocoon.apache.org/manuals/BeginnersGuide
this, being a resource may be permanent. the actual representation/file
delivered (redirected to) may be html, pdf, whatever. and it may well be a
different version of the document (e.g. this resource always redirects to
the most recent version).
that depends on how specific the contract is. you could also have
http://cocoon.apache.org/manuals/BeginnersGuide/1.0 which should represent
the resource with the specific version. and finally you could specify
http://cocoon.apache.org/manuals/BeginnersGuide/1.0/html or something alike.
so I think the minimum contract of your file URLs is that a file exists at
that url.
to your last question: if i saw an url like
http://cocoon.apache.org/manuals/beginner_1.0.html I would expect it's
always going to be the same file.
_________________________________________________________________
STOP MORE SPAM with the new MSN 8 and get 2 months FREE*
http://join.msn.com/?page=features/junkmail
---------------------------------------------------------------------
Please check that your question has not already been answered in the
FAQ before posting. <http://xml.apache.org/cocoon/faq/index.html>
To unsubscribe, e-mail: <[EMAIL PROTECTED]>
For additional commands, e-mail: <[EMAIL PROTECTED]>
