On 10/2/07, Stefano Mazzocchi <[EMAIL PROTECTED]> wrote: <snip>
> 4) the use of "mvn:" URIs is a problem according to TimBL's notion of > 'linked data'. He suggests the use of HTTP URIs so that machines could > use HTTP to self-discover more information about that entity. A possible > URI scheme that is both plausible and usefule is > > http://apache.org/ns/org.apache.velocity/velocity/1.4 maven repositories are not canonical and are replicated so perhaps this url scheme might be better reservered for official releases. then there's the issue of maven 1 verses maven 2... self-discovery is an interesting issue. it's seems to me that it's unlikely that there's going to be any information to discovery at urls within that scheme. co-opting the maven artifact identification system (groupId-artifactId) within a mvn:// uri would allow applications who know about maven to discover information about that release. but the same advantages could be gained from a suitable http URL. using the actual URL (for example: http://people.apache.org/repo/m2-ibiblio-rsync-repository/org/apache/velocity/velocity/1.5/) allows an automated agent to discover the pom meta-data. - robert --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
