Draft minutes from 12-Oct-2010 teleconference

http://www.w3.org/2010/10/12-awwsw-minutes.html
and below in plain text.

--------------------------------------------------------------
[1]W3C

      [1] http://www.w3.org/

                               - DRAFT -

                                 AWWSW

12 Oct 2010

   See also: [2]IRC log

      [2] http://www.w3.org/2010/10/12-awwsw-irc

Attendees

   Present
          Jonathan_Rees, David_Booth, Michael_Hausenblas

   Regrets
   Chair
          jar

   Scribe
          dbooth

Contents

     * [3]Topics
     * [4]Summary of Action Items
     _________________________________________________________

   invite zakim

   michael, are you joining the teleconference?

   <mhausenblas> yup, sorry

   <jar_>
   [5]http://lists.w3.org/Archives/Public/public-awwsw/2010Jul/0004.htm
   l

      [5] http://lists.w3.org/Archives/Public/public-awwsw/2010Jul/0004.html

   jar: What is the relation between a resource (used as the subject of
   an RDF statement) that is denoted by URI, and some HTTP exchanges?

   <mhausenblas> just for the record, as of
   [6]http://www.w3.org/TeamSubmission/turtle/ @base is in fact
   allowed, but [7]http://www.w3.org/2001/tag/awwsw/webarch.ttl still
   has some bugs

      [6] http://www.w3.org/TeamSubmission/turtle/
      [7] http://www.w3.org/2001/tag/awwsw/webarch.ttl

   <mhausenblas> I figured one

   dbooth: Two realms of answers to that question: 1. where you're
   talking about a web resource. 2. other resources.

   <mhausenblas> rdfs:seeAlso
   :[8]http://www.w3.org/2001/tag/2010/06/http-semantics.pdf . should
   be rdfs:seeAlso
   <[9]http://www.w3.org/2001/tag/2010/06/http-semantics.pdf> .

      [8] http://www.w3.org/2001/tag/2010/06/http-semantics.pdf
      [9] http://www.w3.org/2001/tag/2010/06/http-semantics.pdf%3E

   jar: I'm talking about the web resource case -- when you get a 200
   response.

   dbooth: we're talking web architecture, and any architecture is a
   fabrication or a fiction, in a sense.

   jar: yes, it's an ideal.

   dbooth: That also means that various architecture possible. So then
   we need to decide which architecture to choose, i.e., which is
   preferable.

   jar: we have an arch -- the arch embraced by the TAG -- the AWWW
   plus TAG findings and resolutions endorsed by the TAG.

   dbooth: some parts of this arch are clearer than other parts.

   jar: If you start with the central dogma of URI, resource,
   representation . . .

   dbooth: That only applies to web resources though

   jar: But that's a consequence of the arch, not an axiom. The
   distinction between web resources and others is not central.

   dbooth: I agree, it isn't central.

   michael: "web resource" == "awww:InformationResource"?

   dbooth: Yes, pretty much but the definition in the AWWSW is flawed.

   jar: I don't want to try to define it. I first want to account for
   200 responses. Then if we have a way to talk about them, then the
   other stuff should follow.

   <mhausenblas>
   [10]http://www.w3.org/TR/2010/WD-sparql11-http-rdf-update-20100601/#
   graph-identification

     [10] http://www.w3.org/TR/2010/WD-sparql11-http-rdf-update-20100601/#graph-identification

   <mhausenblas>
   [11]http://lists.w3.org/Archives/Public/public-rdf-dawg-comments/201
   0Aug/0004.html

     [11] http://lists.w3.org/Archives/Public/public-rdf-dawg-comments/2010Aug/0004.html

   dbooth: Michael, you were suggesting this as other interesting
   reading?

   michael: Yes, see how it fits in or contradicts.
   ... It may have impact beyond SPARQL 1.1.

   dbooth: Back to what we're doing here . . .

   jar: I'm still struggling with what form our analysis should take
   and how to deal with time.

   <mhausenblas> Michael: we could do a per-case study

   <mhausenblas> 1. 303 Linked Data RDF/XML

   <mhausenblas> 2. SPARQL endpoint

   <mhausenblas> 3. embedded RDFa

   <jar_> 4. fragid in Location:

   dbooth: So when you're doing a formalism the granularity is driven
   by the ways you wish to use your formalism afterward. Time adds
   complexity that is not needed for many simple uses.
   ... If we write n3 rules, who would use them, for what?

   <jar_> e.g. the representation in a GET/200 response is a rep of the
   resource ...

   dbooth: In other words: what questions do we want this formalism to
   answer?

   michael: in RDFa there are two representations returned by one
   resource.

   <jar_> For example: Are Tim's suggestions re SPARQL graphs
   consistent with our analysis of SPARQL?

   jar: Using the arch to show contraditions would be useful.

   dbooth: for #1, what are the possible contradictions?

   <jar_> GET U/200 => RDF that says U is a person.

   <jar_> GET U/200 => RDF that says U is not an information resource.

   <jar_> contradiction between what it says, and the architecture.

   dbooth: that would be a contradiction if persons are disjoint from
   informatino resources.

   <mhausenblas> Michael: would it be a starting point to use
   [12]http://www.w3.org/2001/tag/doc/selfDescribingDocuments.html#AlgP
   icture and then refine the picture?

     [12] http://www.w3.org/2001/tag/doc/selfDescribingDocuments.html#AlgPicture

   <jar_> yes.

   <scribe> chair: jar

Summary of Action Items

   [End of minutes]
     _________________________________________________________


    Minutes formatted by David Booth's [13]scribe.perl version 1.135
    ([14]CVS log)
    $Date: 2010/10/12 14:03:53 $
     _________________________________________________________

     [13] http://dev.w3.org/cvsweb/~checkout~/2002/scribe/scribedoc.htm
     [14] http://dev.w3.org/cvsweb/2002/scribe/

Scribe.perl diagnostic output

   [Delete this section before finalizing the minutes.]
This is scribe.perl Revision: 1.135  of Date: 2009/03/02 03:52:20
Check for newer version at [15]http://dev.w3.org/cvsweb/~checkout~/2002
/scribe/

     [15] http://dev.w3.org/cvsweb/~checkout~/2002/scribe/

Guessing input format: RRSAgent_Text_Format (score 1.00)

No ScribeNick specified.  Guessing ScribeNick: dbooth
Inferring Scribes: dbooth

WARNING: No "Topic:" lines found.

Default Present: DBooth, jar, mhausenblas
Present: Jonathan_Rees David_Booth Michael_Hausenblas
Got date from IRC log name: 12 Oct 2010
Guessing minutes URL: [16]http://www.w3.org/2010/10/12-awwsw-minutes.ht
ml
People with action items:

     [16] http://www.w3.org/2010/10/12-awwsw-minutes.html

WARNING: No "Topic: ..." lines found!
Resulting HTML may have an empty (invalid) <ol>...</ol>.

Explanation: "Topic: ..." lines are used to indicate the start of
new discussion topics or agenda items, such as:
<dbooth> Topic: Review of Amy's report


   End of [17]scribe.perl diagnostic output]

     [17] http://dev.w3.org/cvsweb/~checkout~/2002/scribe/scribedoc.htm



-- 
David Booth, Ph.D.
Cleveland Clinic (contractor)
http://dbooth.org/

Opinions expressed herein are those of the author and do not necessarily
reflect those of Cleveland Clinic.

Received on Tuesday, 26 October 2010 13:30:51 UTC