W3C home > Mailing lists > Public > www-rdf-interest@w3.org > January 2003

Re: XPackage anyone? (RDF newbie question)

From: Charles McCathieNevile <charles@w3.org>
Date: Tue, 14 Jan 2003 20:13:17 -0500 (EST)
To: Marjolein Katsma <wkf1s1l9yfpruqn001@sneakemail.com>
cc: <www-rdf-interest@w3.org>
Message-ID: <Pine.LNX.4.30.0301142003300.31409-100000@tux.w3.org>

Hi Marjolein,

I am not certain that what you re doing fits with the vocabulary of Xpackage,
but I think that there are clearly bits you could mix and match. The other
area I would look is at software packaging as done by RedHat's rpm -
http://www.rpmfind.net - or fink - http://fink.sourceforge.net - which uses
the debian equivalent apt-get.

These things have vocabularies that aren't really encoded in RDF (but could
be - I think rpmfind uses a draft RDF syntax but don't know) but do provide
vocabulary for identifying things like software dependencies and things which
are recommended but not essential.

Cheers

Charles McCN

On Mon, 13 Jan 2003, Marjolein Katsma wrote:

>Here's the problem that's the subject of this message:

>I'm trying to set up RDF for a new (sub)site where I will document and
>distribute some software, mostly extensions to an existing program. I'm
>envisioning that much of the content of the site (apart from actual texts
>I'd have to write) will be RDF-driven. I soon recognized that I'd have
>"Products" and "Packages" with a Package a subclass of Product; and as part
>of the RDF I'd need for this site, I'd need a way to describe Packages in
>terms of the files they contain.  Reading through the RDF Primer I found a
>description of XPackage which I looked up; I found the package concept
>(almost) completely matched my own, so it would be logical to use XPackage
>[1] (the package part, not the XML files part) as part of my solution,
>instead of creating my own vocabulary for that.
>
>However, I find I need to make two distinctions (or refinements): the
>reason is that there would (in my mind) be a difference between the
>"logical" package (all of the functionality as available on the user's
>system (once installed) with all the files needed for that functionality)
>and a "physical" package which is what I would distribute. I know "logical"
>and "physical" aren't very good terms here - I'm open to suggestions - but
>I hope you'll understand what I mean. There are two differences:

>- the "logical" package (once on the user's system) can "consist of" some
>files that are not in the "physical" (downloadable) package: they would be
>already on the user's system (installed with the program my package is an
>extension for) and I have no distribution rights anyway;

>- the "physical" package may also contain some files serving as
>documentation (readme, release notes, etc.) that are not strictly required
>for functionality, and the user may safely throw these away and not lose
>any functionality; I realize this more or less breaks the package concept
>as consisting of exactly those things that _are_ needed for functionality.
>
>It seems obvious to me I'd need some vocabulary in addition to what
>XPackage provides to express these distinctions/refinements but I'm not
>entirely sure if I could just add these to my own RDF schema and then "mix
>and match" with XPackage statements or whether I'd actually have to use a
>complete vocabulary of my own for this since it doesn't quite fit within
>XPackage and the concepts it's based on.
Received on Tuesday, 14 January 2003 20:13:18 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Monday, 7 December 2009 10:51:57 GMT