Re: URI Syntax was: Repository
Some artifacts don't like having the full version number. dll for example. I think the DLL name needs to be stable and thus would not have the full version info. For the dll example we can mandate that it has to be put in a versioned zip/tar.gzip If we continue to think 100% generically we'll never hold all the permutations in Wiki, let alone out heads, and we'll fluster ourselves paralysis. It is clear that Java has a set of requirements, a style, that do not fit other languages. We can't do it all. I feel we could/should unashamedly complete our thoughts on Java, then go and recruit some per-language specialists to chime in on their flavour. Maybe we'll have one repository 'class' with per language sub-classes. Let's mature what we can agree upon before we specialize determine what we can't. [If we have a Java repository separate from a C++ one, so be it, but N better than 0. Heck, separate might be easiest management anyway.] Just my two cents... regards, Adam
RE: URL Syntax parts
I would prefer to NOT have the TLP represented in the URI if possible. Projects can be promoted. The package name for James was always org.apache.james, and so did not change when the project was promoted. Point being that I'm not sure if the URI should reflect the ASF organization. A project name ought to be unique across the ASF. --- Noel
re Group was Argrement #1? : Layout (aka URL)
Adam R. B. Jack wrote: Let's try to work this one through to completion: http://host/group/type/id[-version].ext So what should group be Given Noel's concern about Top Level Project and projects moving. I think that leaves us with the java package name. Allowing non java groups to use org.apache.tlp and then whatever. Also to keep the listing smaller can group be something like /apache/commons/beantuils or must it be apache-comons-beanutils. smime.p7s Description: S/MIME Cryptographic Signature
Re: metadata
Adam R. B. Jack wrote: Metadata: 3) Do we need per version metadata? Hmmm... :( I guess it's doable, tools could easily provide. The per id *.md5 or *.asc are such metadata. I think per version metadata can be just another TYPE of artifact stored in the repo baseurl/commons-beanutils/meta/depend.xml or something. R, Nick smime.p7s Description: S/MIME Cryptographic Signature
Re: URL Syntax parts
Things change, that is a fact that I'm just not sure we can generically pre-empt, nor try. Interestingly, Gump deals with a lot of the issues we are discussing here. The main difference is that Gump purely metadata based, and lives only in the 'now'. For changes it support aliasing. http://gump.covalent.com/log/cvsjars.html http://gump.covalent.com/log/bypackage.html BTW: Gump metadata management gets incredibly stale, incredibly quickly, if folks aren't nagged. I'm not proposing going that far w/ metadata, just realizing the similarities in situation... FWIIW: In Gump (and the repo it is producing) group = CVS module, not project. That could be changed. regards Adam - Original Message - From: Noel J. Bergman [EMAIL PROTECTED] To: [EMAIL PROTECTED] Sent: Thursday, October 30, 2003 5:37 PM Subject: RE: URL Syntax parts I would prefer to NOT have the TLP represented in the URI if possible. Projects can be promoted. The package name for James was always org.apache.james, and so did not change when the project was promoted. Point being that I'm not sure if the URI should reflect the ASF organization. A project name ought to be unique across the ASF. --- Noel
