W3C home > Mailing lists > Public > www-tag@w3.org > April 2012

Re: Draft Minutes of TAG F2F 2-4 April 2012

From: Jonathan A Rees <rees@mumble.net>
Date: Wed, 25 Apr 2012 15:37:08 -0400
Message-ID: <CAGnGFMKvDkY-AQ6TV+bxyuR0NmH1Y-pUmJbKP-qhTLv1fta3TQ@mail.gmail.com>
To: Noah Mendelsohn <nrm@arcanedomain.com>
Cc: "www-tag@w3.org" <www-tag@w3.org>
I made copy edits to the first day minutes. Here's the diff output.

Jonathan

diff -r1.1 02-minutes.html
127,128c127,130
< ... this is the first of 2.5 use cases. What's going on here is
you're making a database about bibliographic information, using
sparkle or some other results <br>
< ... RDF was motivated by PICS whichc was about rating, before powder
---
> ... this is the first of 2.5 use cases. What's going on here is you're
> making a database about bibliographic information, querying using
> query language such as SPARQL <br>
> ... RDF was motivated by PICS which was about ratings, before POWDER
265a268
> <cite>larry:</cite>
275c278
< ... the type of indentified resource is unconstrained <br>
---
> ... the type of identified resource is unconstrained <br>
277c280,282
< ... "Definition of Reputation #3" by 'fiat' -- if the URI identifies
something and you do a GET and you get some bits, then by definition,
the represenation of the resource <br>
---
> ... "Definition of Reputation #3" by 'fiat' &mdash; if the URI
> identifies something and you do a GET and you get some bits, then by
> definition, the bits are a representation of the resource <br>
433c438
< &lt;<cite>timbl</cite>&gt; The RDF system had no inhereent ambiguity
om the trips.   It did decide to use URIs and HTTP, and in designing
them into the system, it constrained them, so URIs adn HTTP were
interpreted in a more cconstrined manner which produced a very nice
very clean system, whcih was very useful. But it involved imiteing the
way one talks about URIs and HTTP
---
> &lt;<cite>timbl</cite>&gt; The RDF system had no inherent ambiguity om the trips.   It did decide to use URIs and HTTP, and in designing them into the system, it constrained them, so URIs and HTTP were interpreted in a more cconstrained manner which produced a very nice very clean system, which was very useful. But it involved limiting the way one talks about URIs and HTTP
544c549
< &lt;<cite>Larry</cite>&gt; the web is unreliable -- we get 404 not
found all the time, but the web is sitll useful
---
> &lt;<cite>Larry</cite>&gt; the web is unreliable -- we get 404 not found all the time, but the web is still useful
556c561
< <cite>jar:</cite> we should be able to ground this in a discussion
where there's an application that do want to be able to make that
distinction
---
> <cite>jar:</cite> we should be able to ground this in a discussion where there's an application that does want to be able to make that distinction
588c593,594
< ... what are the possible sources <br>
---
> ... what are the possible sources [of information that might allow
> the distinction]<br>
599c605
< ... or the information could come from the exchange in http <br>
---
> ... or the information could come from the exchange [request] in http <br>
628c634
< ... New taxonomy of change proposals <br>
---
> ... New taxonomy of change proposals: <br>
641c647,649
< <cite>jar:</cite> 1. 'no agreement'  / 'nuclear' option -- no
statement about relationship between resource and representation <br>
---
> <cite>jar:</cite> 1. 'no agreement'  / 'nuclear' option &mdash; no
> statement about relationship between [identified] resource and
> [retrieved] representation <br>
774c782
< ... We had some other related findings around URIs and registeries
---
> ... We had some other related findings around URIs and registries
778c786
< <cite>jar:</cite> what's the criterion that comes from registeries?
---
> <cite>jar:</cite> what's the criterion that comes from registries?
790c798
< <cite>jar:</cite> so the criterion is that it should touch on the
relationship to registeries?
---
> <cite>jar:</cite> so the criterion is that it should touch on the relationship to registries?
833c841
< <cite>jar:</cite> the criteria for the story is different from
criteria for the solution
---
> <cite>jar:</cite> the criteria for the story are different from criteria for the solution
1094c1102
< ... talking about the process around getting things into registeries <br>
---
> ... talking about the process around getting things into registries <br>
Received on Wednesday, 25 April 2012 19:37:37 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 22:56:44 UTC