> From: Stephen McConnell [mailto:[EMAIL PROTECTED]
>
> Nick Chalko wrote:
>
> > Tim Anderson wrote:
> >
> >> For advocates of URI parsing, what problems are you trying
> >> to solve?
> >>
> >>
> >>
> >* Discovery of "what is available"
> >* Repository exploring.
> >* Auto cleanup
Here is my 20 second URI
http://host/[rootdir]/Orginzation/Product/version/
one dir each for Org, Prod, and Ver.
After that is dependent on the kind of Product. ie the java-artifact-spec.
So lets do a 20 sec java artifact spec
Stephen McConnell wrote:
Nick Chalko wrote:
Tim Anderson wrote:
For ad
Nick Chalko wrote:
Tim Anderson wrote:
For advocates of URI parsing, what problems are you trying
to solve?
* Discovery of "what is available"
* Repository exploring.
* Auto cleanup of repositories.
The URI spec is too loose.
I completely agree.
But I just want to add that all I wa
> Not a criticism, but I'd prefer to know the requirements,
> before writing the tools.
I know, I've been a huge advocate of that, but I'm starting to worry we are
in analysis paralysis. Logical URIs are so virtual it is easy to miss
practical implications. As such, I'd like to test the theory a
Tim Anderson wrote:
Not a criticism, but I'd prefer to know the requirements,
before writing the tools.
Here is a user story.
point a "tool" at the http://repo.apache.org and have it display "what
is available"
This is much easier to do if we can tell the version from the product
from the
> Sent: Tuesday, 25 November 2003 5:59 AM
> To: [EMAIL PROTECTED]
> Subject: Re: Use of '/' in ???-specifier's
>
>
>
> > Tim Anderson wrote:
> >
> > >For advocates of URI parsing, what problems are you trying
> > >to solve?
>
> This i
Tim Anderson wrote:
From: Nick Chalko [mailto:[EMAIL PROTECTED]
Tim Anderson wrote:
http://repo.apache.org/alpha/alpha/alpha/alpha/alpha/alpha.jar
http://repo.apache.org/1/2/3/4/5/6/7/8/9.jar
We really need to harden the URI spec a little and the "/" is a
good start.
I missed
> From: Nick Chalko [mailto:[EMAIL PROTECTED]
>
> Tim Anderson wrote:
>
> >>http://repo.apache.org/alpha/alpha/alpha/alpha/alpha/alpha.jar
> >>http://repo.apache.org/1/2/3/4/5/6/7/8/9.jar
> >>
> >>We really need to harden the URI spec a little and the "/" is a
> >>good start.
> >>
> >>
> >>
> >
>
> Tim Anderson wrote:
>
> >For advocates of URI parsing, what problems are you trying
> >to solve?
This is a simple matter of practicality. We've agreed to delay metadata so
we can get a nice/simple repository structure w/o all the differences of
opinion that metadata might introduce. We basicall
Tim Anderson wrote:
http://repo.apache.org/alpha/alpha/alpha/alpha/alpha/alpha.jar
http://repo.apache.org/1/2/3/4/5/6/7/8/9.jar
We really need to harden the URI spec a little and the "/" is a
good start.
I missed that the "jars" or type dir was required.
what about,
http://repo.apache.org/
> From: Nick Chalko [mailto:[EMAIL PROTECTED]
>
> Tim Anderson wrote:
>
> >For advocates of URI parsing, what problems are you trying
> >to solve?
> * Discovery of "what is available"
> * Repository exploring.
> * Auto cleanup of repositories.
>
> The URI spec is too loose.
>
> As far
Tim Anderson wrote:
For advocates of URI parsing, what problems are you trying
to solve?
* Discovery of "what is available"
* Repository exploring.
* Auto cleanup of repositories.
The URI spec is too loose.
As far as I can tell these are legal
http://repo.apache.org/alpha/alpha/alpha/
> From: Nick Chalko [mailto:[EMAIL PROTECTED]
>
> Noel J. Bergman wrote:
>
> >Seems to me
> >that there is limited utility to being able to parse the URI,
> and that the
> >real key is having meta-data with which to assemble it. But others don't
> >seem to agree with that view. They want to parse
to be taught of the organization as a
separate entity than the other segments and how to parse that out.
This is a small thing, but it would be nice to make it simple instead of
complex.
regards,
-Anou
From: Nick Chalko <[EMAIL PROTECTED]>
Reply-To: [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Noel J. Bergman wrote:
Seems to me
that there is limited utility to being able to parse the URI, and that the
real key is having meta-data with which to assemble it. But others don't
seem to agree with that view. They want to parse semantic information from
the URI.
The semantic information is
Tim Anderson wrote:
Alternative approaches would be to:
. limit each *-specifier to a single path segment (i.e, disallow "/")
Hopefully, the proposals show that this is too restrictive
It works the name are just very long, and thie directory listings are large.
. include delimeters in the URI
Noel J. Bergman wrote:
maybe the [organization]/[product] notion is artificial.
What [organization]/[product] and [organization]/[product]/[version]
do is to establish a path to an logical artifact.
At any of it does is establish a path to a logical artifact. Seems to me
that there is limite
> maybe the [organization]/[product] notion is artificial.
> What [organization]/[product] and [organization]/[product]/[version]
> do is to establish a path to an logical artifact.
At any of it does is establish a path to a logical artifact. Seems to me
that there is limited utility to being abl
Tim Anderson wrote:
From: Stephen McConnell [mailto:[EMAIL PROTECTED]
Nick Chalko wrote:
Given this spec
repository-uri = access-specifier "/" product-specifier "/"
version-specifier "/" artifact-specifier
What is the version of this URL
http://repo.apache.org/org/apache/com
> From: Stephen McConnell [mailto:[EMAIL PROTECTED]
>
> Nick Chalko wrote:
>
> > Given this spec
> > repository-uri = access-specifier "/" product-specifier "/"
> > version-specifier "/" artifact-specifier
> >
> >
> > What is the version of this URL
> > http://repo.apache.org/o
Nick Chalko wrote:
Given this spec
repository-uri = access-specifier "/" product-specifier "/"
version-specifier "/" artifact-specifier
What is the version of this URL
http://repo.apache.org/org/apache/commons/nightly/alpha/1.0/foo.jar
* Projet commons, version Nightly 1.0
Nick Chalko wrote:
Tim Anderson wrote:
The URI isn't valid, according to
http://nagoya.apache.org/wiki/apachewiki.cgi?ASFRepository/CommonBuildVersio
nSpecifier
-Tim
Try this one
http://repo.apache.org/org/apache/commons/alpha/1.0/foo.jar
* Projet commons, version 1.0 alpha
* Pro
Tim Anderson wrote:
The URI isn't valid, according to
http://nagoya.apache.org/wiki/apachewiki.cgi?ASFRepository/CommonBuildVersio
nSpecifier
-Tim
Try this one
http://repo.apache.org/org/apache/commons/alpha/1.0/foo.jar
* Projet commons, version 1.0 alpha
* Project commons-alpha,
> From: Nick Chalko [mailto:[EMAIL PROTECTED]
>
> Given this spec
>
> repository-uri = access-specifier "/" product-specifier "/"
>version-specifier "/" artifact-specifier
>
>
> What is the version of this URL
> http://repo.apache.org/org/apache/commons/nightly/alpha/1.0/foo.jar
24 matches
Mail list logo
