On 12/20/06, Steve Loughran <[EMAIL PROTECTED]> wrote:
robert burrell donkin wrote: > On 12/19/06, Steve Loughran <[EMAIL PROTECTED]> wrote: >> robert burrell donkin wrote: >> > On 12/19/06, Steve Loughran <[EMAIL PROTECTED]> wrote:
<snip>
>> 2. looking to get management approval to hand the code to the MIT Simile >> project (e.g. Stefano) > > cool > > (there seems to a lot of interest developing around RDF ATM amongst > apache members) > > stefano's keen to see discussions related to apache and RDFs in the > labs > http://mail-archives.apache.org/mod_mbox/labs-labs/200612.mbox/[EMAIL PROTECTED] > > (which makes sense to me.) In theory, RDF is a "better" way of gluing together metadata in a way that is tool neutral. For little tools, it should be effective. I know Stefano is a fan of the semantic web, but to me the JAR repository is an interesting analysis of how well it will work. We know that today there's a lot of inconsistency out there, even though there are some dedicated people (esp. Carlos) who put a lot of effort in to keeping things under control. If we have problems chaining together metadata from a single repository, what are the long term implications for the semantic web going to be?
+1 be interesting to see the level of practical benefit from application neutral meta-data
>> 3. Thinking of something to audit the metadata. Maybe in prolog (my >> choice), maybe something else. > > i plan to persuade projects (by including this in RAT rather than a > conventional configuration file) to start recording auditing meta data > about documents which didn't originate at apache in RDF. i've also > been toying with the idea of using RDF to record relationships between > licenses and policy about licenses. > > these sound like related problems to me yes, one of my proposed 'enhancements' for both pom and ivy.xml files is to include an audit trail in there, such as who created the pom. Supporting a metadata element that took RDF-as-XML triples would be a very extensible way to do this. Wagon and Ivy could ignore the data, but other tools could extract it.
+1 probably want more than just creator. for a repository, the creator of the pom may be different from the distributor who uploaded the descriptor and the original author of the artifact described. all of these would be useful in determining the audit trail. for example, i'd be more inclined to trust an artifact with signatures from representatives of each group than any alone.
How would you use RDF to differentiate the mysql interpreation of GPL from everyone elses?
i've been trying to work that out for a while it seems to me that there are several different layers of meta-data for a particular resource (an element of an open source project), i'm interested in license, license family, origin (url where the copy came from) and rights holder. (maybe other stuff such as whether it's been modified) i'm also interested in questions about aggregates: whether a particular collection of elements can be distributed together given some rules and meta-data about the other URLs referenced in the resource meta-data. together, these rules and meta-data would be policy. in the case of mysql, the family would be GPL but the license would be mysql-GPL. a policy might decide to trust their promise and describe this in meta-data. (i haven't really had time to explore this yet but i have hopes that this combination might be enough to make things work.) but this needs more work
>> Working title "repo-man". This not only lets us have a good name, it >> gives us good quotes > > repo man rules :-) Best film Alex cox ever made. > it's amazing at the cinema... > >> "It's 4 A.M., do you know where your jar is?" >> "You don't even know what's in your own trunk! And you know what? I >> think you're afraid to find out! " > > +1 Ok. then, we have a name! I wonder if we could include some of the quotes as error messages ( http://www.imdb.com/title/tt0087995/quotes) . Like when an artifact fails the audit [error] artifact rejected. [error] It happens sometimes. People just explode. Natural causes.
+1 humour injection is a powerful design pattern repo man powers the satirical web - robert --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
