these are great suggestions. we started with the Linux docs as that is
what we are all closest too. but there is no reason not to have the design
aim for wider coverage, in fact that would be very very desirable. in
reality we are only talking about a few elements difference and those
elements are optional ones.
about freebsd, i plead ignorance of their efforts which is my loss
entirely (speaking only for me). the metadata is out there for comments
and is not set in stone (yet ;->). we do have it in a form that in theory
you could actually work with tho. that step seemed to be necessary to get
us to off the ground.
On Fri, 29 Oct 1999, Nik Clayton wrote:
> On Mon, Oct 25, 1999 at 04:25:57PM -0500, Kendall Clark wrote:
> > Speaking for myself only, as the LDP Core team hasn't talked about
> > this much yet, though I suspect they will all agree, I think we can
> > use LDP Core as the base for metadata schemas for several open source
> > projects. My guess is that Debian, GNOME, and FreeBSD would share
> > about 99% of this structure of LDP Core; and in that case, the name
> > isn't terribly problematic.
>
> It would have been nice if a heads-up had been posted to the FreeBSD
> -doc list, asking if anyone wanted to participate in this a bit earlier.
> I'm looking at the core element description at the moment, and it looks
> interesting.
>
> <snip>
>
> > So, for example, GNOME Metadata would be, essentially, LDP Core + one
> > or two GNOME-specific formal vocabularies. This would insure some
> > level of interoperability.
>
> Can I suggest that you try for a core that it is not Linux specific that
> other projects have to customise, but go for something that could be
> applied to pretty much any Doc. Proj., and then add customisations for
> Linux in a separate layer.
>
> For example
>
> Entry Linux FreeBSD GNOME KDE
> ------------------------------------------------------------
> COVERAGE.geographic X X X X
> COVERAGE.distribution X
> COVERAGE.kernel X
> COVERAGE.architecture X
> COVERAGE.os X X X X
>
> only those entries that apply across all of them (or, say, more than two)
> should be in the core. Anything else should be in a customisation layer
> for that project.
>
> I've picked four example projects up there, but that's certainly not a
> complete list.
>
> N
>
==========================================================================
Paul Jones
"We must protect our precious bodily fluids!" General Jack D Ripper
http://MetaLab.unc.edu/pjones/ at the Site Formerly Known As SunSITE.unc.edu
[EMAIL PROTECTED] voice: (919) 962-7600 fax: (919) 962-8071
===========================================================================
