W3C home > Mailing lists > Public > public-rdf-dawg@w3.org > July to September 2004

Re: design eval matrix in RDF and N3

From: Kendall Clark <kendall@monkeyfist.com>
Date: Wed, 7 Jul 2004 19:16:10 -0400
To: Dan Connolly <connolly@w3.org>
Cc: RDF Data Access Working Group <public-rdf-dawg@w3.org>
Message-ID: <20040707231610.GA28131@monkeyfist.com>

On Wed, Jul 07, 2004 at 05:24:54PM -0500, Dan Connolly wrote:

> I just made them world-readable... and linked them from
> http://www.w3.org/2001/sw/DataAccess/DesignEvaluations


> > I made up a namespace for the WG and for the UCR doc, as well as some
> > predicates in each namespace.
> Hmm... why? Why not:
> @prefix ucr: <http://www.w3.org/2001/sw/DataAccess/design-eval#>.

Good question. I'll think a bit more about this and update them if I
change stuff. (Or are you making a "only the WG itself can do this"

> odd... the namespace prefixes aren't used in cases like
> ucr:supports <http://www.w3.org/2001/sw/DataAccess/UseCases#r3.4>;
> is that because of the tool you used to produce the file?

Yes. I'll definitely be fixing this.

> and regarding
> ucr:not-evaluated <http://www.w3.org/2001/sw/DataAccess/UseCases#d4.8>
> that seems better left unsaid.


> > identify the designs we evaluated (since I wasn't sure they all had
> > stable "home pages", and I don't like the "home page stands for foo"
> > idiom much).
> Hmm... Why TAG URIs? Why not fragments of design-eval, again?

Because no one will try to deref a TAG URI and the requirements and
design objective URIs *can* be deref'd. I wanted this distinction to
be clear.

Received on Wednesday, 7 July 2004 19:16:24 UTC

This archive was generated by hypermail 2.3.1 : Wednesday, 7 January 2015 15:00:44 UTC