On Mon, 10 Nov 2003 06:31 pm, Tim Anderson wrote:
> URI Components
> --
>
> An absolute repository URI is written as follows:
>
> repository-uri = access-specifier "/" product-specifier "/"
>artifact-specifier
>
> For java artifacts, artifact-specifier is:
>
> ar
Noel:
Thanks for the W3C style reference. One of the subjects it deals with
is content negotiation http://www.w3.org/Provider/Style/URI.html#remove
- and this got me thinking about how metadata as opposed to a resoruce
that metadata is describing can be resolved. I'm going to try to dig up
so
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
embed
> 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.
Could? Yes. But that is just one way of many. I maintain that httpd could
serve the content of most repositories, meta-data and all, without d
Stephen McConnell wrote:
Noel:
Thanks for the W3C style reference. One of the subjects it deals with
is content negotiation http://www.w3.org/Provider/Style/URI.html#remove
- and this got me thinking about how metadata as opposed to a resoruce
that metadata is describing can be resolved. I'm g
