On 9/24/07, Matthieu Riou <[EMAIL PROTECTED]> wrote:
> On 9/23/07, Robert Burrell Donkin <[EMAIL PROTECTED]> wrote:
> >
> > <snip>
> > IMHO there are two sets of data that need to be collected and
> > maintained. (not sure whether both are in scope for discordia or
> > whether a separate mini-project might be a better home for the license
> > meta-data.)
>
>
> I've been wondering about that too. I think the data should be in the same
> project that will use it as we'll probably have some API to query and
> reconcile artifacts' licenses and the information about these licenses.
> Although this will have to get released so I'm not sure the lab is a good
> location. I think all those parts could live in the incubator to start with
> under the RAT umbrella, as different modules.

sounds like a good plan

i hope RAT -> incubator will start this week

> the first links artifacts to licenses. the DOAP vocabulary should work
> > fine for this. (indeed, DOAP would be another good source for
> > meta-data.) probably worth posting a hello to the DOAP mailing list.
>
>
> Yep.
>
> the second is meta-data about licenses. so, it's not enough to know
> > that groovy has a particular license but also that this license is
> > from the apache license 1.1 family. licenses in the apache 1.1 family
> > share the same legal properties: they are open source, they require
> > attribution, they are non-reciprical and so on. they also all share
> > the same apache policy WRT inclusion as dependencies.
> >
> > this seems to me quite a new and different vocabulary to DOAP. might
> > be a good idea to talk to the DOAP people about this new vocabulary.
>
>
> Good idea. Although do you think that format should live side-by-side with
> DOAP?

in terms of data storage?

> There could be some synergy too with the ASF legal affairs, I'm
> wondering how interesting they could be in this.

storing apache policy in RDF is cool. i plan to raise this on legal
discuss when we've done a little more work...

- robert

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to