Noel, So let me understand. You're saying that those interested in enabling a repo with metadata and searches based on this metadata could wrap the repository with a servlet. The URI could be used by the servlet to give a different view of the repository based on parameters, search filters embedded in it et. Cetera. Then the servlet manages the interaction behind the scenes with some sort of metadata database to conduct the query and return the results as if they were regular files on the server's repo file system.
That sounds like it has a lot of potential. Alex > Noel J. Bergman wrote: > > >Stephen McConnell asked: > > > > > > > >>File system - a convenient and simple solution - but should a file > >>system driven approach be the basis for the next generation? > >> > >> > > > >The basis is a URI space. Whether a URI is efficiently served by a > static > >file, or by some servlet, CGI or Grandma Moses typing very VERY fast > really > >should not be visible to the user-agent. > > > > > > > >>A solution must be implementation independent > >> > >> > > > >See: http://www.w3.org/Provider/Style/URI.html > > > >The URI is a request for content. It should not change, regardless of > the > >means by which the content is generated. > > > > > > > >>So why a preoccupation with meta-less file system structures as opposed > >>to a preoccupation with an extensible repository protocol? > >> > >> > > > >The "extensible repository protocol" is HTTP. Nothing else needs to be > >visible. The only thing that the infrastructure team needs to deal with > is > >the implementation of the URI space (allowing that the content addressed > by > >a URI can vary based upon the user-agent). > > > > --- Noel > > > > > > > > > > -- > > Stephen J. McConnell > mailto:[EMAIL PROTECTED] > >
