public inbox for [email protected]  

help / color / mirror / Atom feed

From: Joshua D. Drake <[email protected]>
To: Dave Page <[email protected]>
Cc: David Fetter <[email protected]>
Cc: w^3 <[email protected]>
Subject: Re: RFC: Product directory
Date: Mon, 02 Jun 2008 08:28:52 -0700
Message-ID: <[email protected]> (raw)
In-Reply-To: <[email protected]>
References: <[email protected]>
	<[email protected]>
	<[email protected]>

Dave Page wrote:
> On Mon, Jun 2, 2008 at 12:33 PM, David Fetter <[email protected]> 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"

I have to go with fetter here. Pricing is not our concern.

> 
>>  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.
>

+1


>> 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.

Yeah I mentioned this in my previous post. Publisher really needs to be 
pushed out. There is entirely too much redundant information that can be 
accumulated.

Sincerely,

Joshua D. Drake

view thread (16+ messages)  latest in thread

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients using the --to and --cc options:
  reply via email

  To: [email protected]
  Cc: [email protected], [email protected], [email protected]
  Subject: Re: RFC: Product directory
  In-Reply-To: <[email protected]>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by agora; see mirroring instructions
for how to clone and mirror all data and code used for this inbox