Received: from localhost (unknown [200.46.204.183])
	by developer.postgresql.org (Postfix) with ESMTP id BB8242E0091
	for <pgsql-www-postgresql.org@developer.postgresql.org>;
	Mon,  2 Jun 2008 08:58:58 -0300 (ADT)
Received: from developer.postgresql.org ([200.46.204.71])
	by localhost (mx1.hub.org [200.46.204.183]) (amavisd-maia, port 10024)
	with ESMTP id 35928-08
	for <pgsql-www-postgresql.org@developer.postgresql.org>;
	Mon,  2 Jun 2008 08:58:49 -0300 (ADT)
X-Greylist: from auto-whitelisted by SQLgrey-1.7.6
Received: from gv-out-0910.google.com (gv-out-0910.google.com
 [216.239.58.191])
	by developer.postgresql.org (Postfix) with ESMTP id B26562E0085
	for <pgsql-www@postgresql.org>; Mon,  2 Jun 2008 08:58:53 -0300 (ADT)
Received: by gv-out-0910.google.com with SMTP id i36so2043739gve.7
	for <pgsql-www@postgresql.org>; Mon, 02 Jun 2008 04:58:51 -0700 (PDT)
Received: by 10.150.83.22 with SMTP id g22mr4022843ybb.146.1212407929602;
	Mon, 02 Jun 2008 04:58:49 -0700 (PDT)
Received: by 10.150.144.11 with HTTP; Mon, 2 Jun 2008 04:58:49 -0700 (PDT)
Message-ID: <937d27e10806020458o68717cd7sb7e0424338ff5d19@mail.gmail.com>
Date: Mon, 2 Jun 2008 12:58:49 +0100
From: "Dave Page" <dpage@pgadmin.org>
To: "David Fetter" <david@fetter.org>
Subject: Re: RFC: Product directory
Cc: w^3 <pgsql-www@postgresql.org>
In-Reply-To: <20080602113349.GA8921@fetter.org>
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
References: <937d27e10806020130l418d1730o84de8773f1f182f5@mail.gmail.com>
	<20080602113349.GA8921@fetter.org>
X-Virus-Scanned: Maia Mailguard 1.0.1
X-Archive-Number: 200806/3
X-Sequence-Number: 15230

On Mon, Jun 2, 2008 at 12:33 PM, David Fetter <david@fetter.org> wrote:

>> price text -- Pricing info (where relevant)
>
> Price is too complicated to model, and suffers from "cache coherency"
> issues.  Pointing to a web site, where appropriate, would handle this
> better.

Agreed but a) we already display that data and b) it's useful to give
users a ballpark figure, even if something like "$99.99US as at
15/12/2007"

<snip ddl>


> Products may have more than one category.

We don't currently allow listings in more than one category, and I'm
inclined to continue with that (unwritten) policy - the reason being
that listing in multiple categories will easily bloat the number of
generated pages that a product might be listed in, potentially
affecting search engine rankings. With relatively generic categories I
don't see any real need to allow multiple categories.

>  and more than one license.

Again, not sure I see a need. Either it's commercial, OSS, or freeware
- I don't think there's much scope to have more than one (the obvious
exception is something like "$99.99, or free to educational users" but
I'd just class that as commercial). I don't want to list the actual
OSS licence used as folks can decide whether a product meets with
their personal ethics once they visit it's homepage.

> The above schema handles these things.  Might we want to break
> "publisher" out into a separate table?

Possibly. Makes the coding & management a little more tricky though.
If we were to do that perhaps it should be part of a larger project to
have a directory of vendors/publishers etc for news, events, services
and products.

-- 
Dave Page
EnterpriseDB UK: http://www.enterprisedb.com