13:58:01 RRSAgent has joined #awwsw 13:58:01 logging to http://www.w3.org/2009/01/06-awwsw-irc 13:58:04 Zakim has joined #awwsw 13:58:12 zakim, this will be awwsw 13:58:12 ok, dbooth; I see TAG_(AWWSW)9:00AM scheduled to start in 2 minutes 13:58:39 TAG_(AWWSW)9:00AM has now started 13:58:46 +DBooth 14:02:04 +TimBL 14:04:49 +Jonathan_Rees 14:05:22 jar has joined #awwsw 14:08:39 Stuart has joined #awwsw 14:09:12 Hello /me just dialing (having checked in an early comment on the vocab page). 14:09:39 jar has changed the topic to: http://esw.w3.org/topic/AwwswVocabulary 14:09:58 +??P3 14:10:39 We should finish the HTTP in RDF review: http://esw.w3.org/topic/AwwswHttpVocabularyInRdfComments 14:13:32 -TimBL 14:17:23 +TimBL 14:21:31 +??P1 14:21:36 hhalpin has joined #awwsw 14:22:02 Zakim, who's on the phone? 14:22:02 On the phone I see DBooth, Jonathan_Rees, Stuart, TimBL, ??P1 14:22:09 Zakim, ??P1 is hhalpin 14:22:09 +hhalpin; got it 14:22:43 Topic: Vocabulary page 14:22:46 http://esw.w3.org/topic/AwwswVocabulary 14:23:05 Stuart: What do you mean by "subject matter"? 14:23:23 jar: I mean the RDF that we want to write. I'll fix the sentence. Sorry for the confusion. 14:24:18 ACTION: Jar to clear up confusion about what he means by "subject matter" 14:24:18 Created ACTION-12 - Clear up confusion about what he means by \"subject matter\" [on Jonathan Rees - due 2009-01-13]. 14:24:26 jar: Rules of engagement okay? 14:24:37 dbooth: Fine to start with. 14:25:13 jar: Also, when you introduce a class you need to have a relation to that class, to help understand what the members are. 14:25:37 ACTION: jar to add additional rule about having a relation when you add a class 14:25:37 Created ACTION-13 - Add additional rule about having a relation when you add a class [on Jonathan Rees - due 2009-01-13]. 14:26:33 jar: rfc2616:Entity okay? 14:26:40 dbooth: Looks good to me. 14:28:12 harry: If you don't have a URI, how could you post or put something there? 14:29:16 jar: Through some other protocol or API. You can also do a GET using an IP address and use that connection. 14:31:58 harry: If rfc2616:Resource doesn't require a URI, then we may need another class that does have a URI, so that peopel know they can access it with HTTP, etc. 14:32:09 s/peopel/people/ 14:33:29 Hmmm Re: "For example, suppose I connect to an HTTP server that has no DNS host name, and specify a relative URI." that you have established a connection at least gives you an IP address that could be used in the authority field. 14:34:01 harry: I'm okay with removing the URI requirement for the rfc2616:Resource definition, but we may want something like that later. 14:36:02 In Fieldings model of the world the mapping goes from URI to resource and from resource (modelled a "time varying membership function") to representations or URI (which I take to be redirection or the like). 14:36:12 JAR requests use cases from Harry that would benefit from modeling a has-URI/has-no-URI distinction. 14:36:28 ie. by Fieldings model the identifying URI is not intrinsic to the resource itself. 14:39:31 (TimBL: about separation of resource from its name (URI).) 14:39:50 I used to have a "...these are not the resources that you are looking for..." in the sense that the resource could simply be portrayed as the things that all the respresentations obtained from the resource are representations of... ie. if it's character changes - a weather page becomes a gambling page is just a strange resource and "...not the resource you were looking for...". 14:41:30 However, even though it may be poor practice allowing the mapping between URI and resources to change then the in general URI are not/cannotbe intrinsic to the resources they denote. 14:43:17 jar: What about "comes from"? 14:43:46 So, for timbl: http:rfc2616=awww:Representation 14:43:48 timbl: Shouldn't this be "has representation", as in AWWW? 14:44:08 jar: Wanted to start with 2616 notion first, not AWWW. 14:44:31 -TimBL 14:44:48 +TimBL 14:47:14 From 2616: 14:47:16 representation 14:47:16 An entity included with a response that is subject to content 14:47:16 negotiation, as described in section 12. There may exist multiple 14:47:16 representations associated with a particular response status. 14:48:31 FWIW: IMO rfc2616:Representations are admissable as entity bodies on requests and responses. 14:48:45 s/on/in/ 14:48:55 timbl: It's pointing out there may be multiple representations for a given resource -- not that conneg is a key characteristic of representation. 14:49:25 harry: I think it means it *might* be subject to conneg. Otherwise we have too many defs of representation around. 14:49:45 timbl: There's no way to know if conneg happened. 14:51:25 dbooth: The ability to have conneg is a by-product, not the distinguishing characteristic. 14:52:58 -TimBL 14:54:04 +TimBL 14:57:52 Ahah... TimBL has just hit upon an essential facet of a class defn that we may have missed - identity criteria, it a test for determining sameness. 14:58:06 s/it/ie/ 14:59:18 dbooth: I'm arguing that the domain of the "comes from" property is actually rfc2616:Representation: i.e., there does not exist an rfc2616:Entity X and rfc2616:Resource R such that "X comes from R" and X is not an rfc2616:Representation. 15:00:53 Topic: Next meeting 15:01:01 jar: Talk about HTTP in RDF doc next time? 15:01:41 -DBooth 15:01:54 Ok... I think that there is pun going on around representation - in the sense of a relation between and entity and a resource in the sense that the given entity is said to webarch:represent the rsource and a syntactic entity that has a mime type and bits. 15:02:39 I agree Stuart. 15:02:49 -TimBL 15:02:52 I think the punning is actually three ways. 15:02:55 hhalpin: Let's figure out how to plug 'web resource' and 'entity' into http-in-rdf vocabulary. 15:03:15 awww use representation to refer to such an entity, but I can see that that an entity in fact awww:represents a resource can only be objecivly determined by obtaining said entity in a response. 15:21:36 -Jonathan_Rees 15:24:05 http://www.ihmc.us/users/phayes/PatHayesAbout.html 15:30:38 -Stuart 15:30:41 -hhalpin 15:30:42 TAG_(AWWSW)9:00AM has ended 15:30:44 Attendees were DBooth, TimBL, Jonathan_Rees, Stuart, hhalpin 15:59:35 rrsagent, make logs public 15:59:53 Chair: Jonathan Rees 16:00:10 Present: TimBL, DBooth, JonathanRees, StuartWilliams, HarryHalpin 16:00:19 rrsagent, draft minutes 16:00:19 I have made the request to generate http://www.w3.org/2009/01/06-awwsw-minutes.html dbooth 16:29:30 Zakim has left #awwsw 16:51:11 Stuart has left #awwsw 16:51:46 hhalpin has joined #awwsw 17:22:18 hhalpin has joined #awwsw 19:34:14 RRSAgent has joined #awwsw 19:34:14 logging to http://www.w3.org/2009/01/06-awwsw-irc 19:34:22 Meeting: AWWSW 19:35:01 rrsagent, draft minutes 19:35:01 I have made the request to generate http://www.w3.org/2009/01/06-awwsw-minutes.html dbooth