14:48:27 RRSAgent has joined #er 14:48:27 logging to http://www.w3.org/2006/11/08-er-irc 14:48:32 Zakim has joined #er 14:48:41 zakim, this will be ERT 14:48:41 ok, shadi; I see WAI_ERTWG()10:00AM scheduled to start in 12 minutes 14:48:47 meeting: ERT WG 14:48:53 chair: Shadi 14:49:12 regrets: Shane, Daniela, Jim, Chris 14:49:52 agenda: http://lists.w3.org/Archives/Public/public-wai-ert/2006Nov/0001.html 14:50:19 agenda+ re-adoption of uri:uri in WebContent class 14:50:46 agenda+ proposal for FileContent class 14:50:59 agenda+ sequences in the HTTP vocabulary 14:51:11 agenda+ additional validity level values 14:51:24 agenda+ addressing security/privacy in EARL 14:51:37 agenda+ ICRA review of EARL 1.0 Schema 15:00:32 WAI_ERTWG()10:00AM has now started 15:00:33 +Shadi 15:01:41 CarlosI has joined #er 15:02:08 CarlosV has joined #er 15:02:47 +CarlosV 15:02:48 -CarlosV 15:02:49 +CarlosV 15:03:51 JohannesK has joined #er 15:04:02 +Diego 15:04:20 zakim, Diego is really CarlosI 15:04:20 +CarlosI; got it 15:04:24 +CarlosV.a 15:04:51 zakim, CarlosV.a is really Johannes 15:04:53 +Johannes; got it 15:07:01 scribe: Johannes 15:07:10 scribenick: JohannesK 15:07:49 zakim, take up agendum 1 15:07:49 agendum 1. "re-adoption of uri:uri in WebContent class" taken up [from shadi] 15:08:15 http://lists.w3.org/Archives/Public/public-wai-ert/2006Oct/0073.html 15:09:31 saz: there's no need for uri:uri in public web content, but there are situations where the URI is not unique 15:10:21 saz: so earl:WebContent should have an uri:uri additionally to a unique rdf:ID (or rdf:about) 15:13:40 saz: information on how to use uri:uri and rdf:about should be in the guide 15:15:30 ci: WebContent is only for World Wide Web, local file system or private web servers are not world-wide 15:16:22 ci: both use cases should be handled by FileContent 15:16:58 saz: WebContent is for Web (HTTP), not necessarily World-Wide 15:17:05 cv: or FTP or ... 15:17:56 saz: WebContent right now is focused on HTTP (request/response stuff) 15:18:55 cv: can't I use WebContent for ftp resources? 15:18:58 saz: you can 15:19:28 saz: it's not just HTTP 15:20:28 saz/cv: you can use WebContent for basic FTP operations (using ftp URI) 15:21:12 drooks has joined #er 15:22:47 cv: subclass WebContent and put uri:uri into subclass 15:23:11 cv: private stuff needs uri:uri, public stuff doesn't 15:24:21 s/cv/ci/ 15:25:04 cv: rdf:about doesn't work with content negotiation 15:25:17 ci: so uri:uri must be used then 15:25:30 saz: make uri:uri optional (when needed)? 15:25:56 saz: used only when needed? 15:27:21 ci: we need to explain the use cases when to use uri:uri and when to use rdf:about, could be tricky 15:27:42 cv: don't see much difficulty in explaining 15:28:42 saz: we're talking about software developers, they are not that dumb 15:29:18 s/they are not that dumb/they should know their way 15:30:33 cv: when using http:GetRequest, uri:uri is not necessary on WebContent 15:31:34 ci: still think it could be difficult, but go on 15:34:34 saz: I now think to make uri:uri mandatory on WebContent 15:34:59 jk: if used on both classes, it must be the same, that's the only requirement I see 15:36:15 ACTION: saz to write a follow-up on when and how many times to use uri:uri 15:36:27 zakim, take up agendum 2 15:36:28 agendum 2. "proposal for FileContent class" taken up [from shadi] 15:36:56 e 15:36:56 [16:36] ACTION: saz to write a follow-up on when and how many times to use uri:uri 15:37:16 http://lists.w3.org/Archives/Public/public-wai-ert/2006Oct/0072.html 15:39:06 saz: filename is subproperty of uri:uri 15:39:47 file://index.html 15:39:52 jk: I wouldn't make it a subproperty, if it's not really a URI 15:41:58 AFAIK this means: the server host is index.html 15:44:29 file:///index.html means: a file with the path index.html in the file root on the local host 15:46:23 ci: you cannot just put file: in front of it and think it's a proper file URI 15:47:51 saz: do we have a data type for file names? 15:49:22 saz: we can leave it completely open (forward/backward slash, case sensitivity) 15:53:13 What is the benefit of using 'file://my/path/to/index.html' instead of 'index.html'? 15:53:46 or even 'my discosed index.html'? 15:54:04 ./index.html 15:55:29 jk: this has no indication of URI scheme, could be file, ftp, http, or even relative to the EARL resource containing it 15:55:44 ./www/index.html 15:56:19 index.html 15:56:29 jk: the call it file path, because it's a relative file path 15:56:38 s/the/then/ 15:57:51 file:./www/index.html 15:59:51 cv/saz: the use case is about finding files, not just labelling them 16:00:53 saz: are there issues with cv's example? 16:01:46 The path is '/www.index.html' 16:02:00 at least according to the Java implementation 16:02:36 oops, sorry 16:02:58 jk: confirmed 16:03:29 file://localhost/./www/index.html 16:03:42 ;-) 16:04:07 -CarlosV 16:04:33 ACTION: cv to post his thoughts on file name 16:04:40 -Johannes 16:04:42 -CarlosI 16:04:46 -Shadi 16:04:48 WAI_ERTWG()10:00AM has ended 16:04:50 Attendees were Shadi, CarlosV, CarlosI, Johannes 16:07:29 zakim, bye 16:07:29 Zakim has left #er 16:07:38 rrsagent, make logs world 16:07:44 rrsagent, make minutes 16:07:44 I have made the request to generate http://www.w3.org/2006/11/08-er-minutes.html shadi 16:07:45 rrsagent, make logs world 16:07:50 rrsagent, bye 16:07:50 I see 2 open action items saved in http://www.w3.org/2006/11/08-er-actions.rdf : 16:07:50 ACTION: saz to write a follow-up on when and how many times to use uri:uri [1] 16:07:50 recorded in http://www.w3.org/2006/11/08-er-irc#T15-36-15 16:07:50 ACTION: cv to post his thoughts on file name [2] 16:07:50 recorded in http://www.w3.org/2006/11/08-er-irc#T16-04-33