08:57:39 RRSAgent has joined #webid 08:57:39 logging to http://www.w3.org/2011/06/03-webid-irc 08:57:41 Deiu has joined #webid 08:57:46 rrsagent, please make logs public 08:57:56 trackbot, start meeting 08:57:56 *wages* 08:57:58 RRSAgent, make logs world 08:58:00 Zakim, this will be WEBID 08:58:00 I do not see a conference matching that name scheduled within the next hour, trackbot 08:58:01 Meeting: WebID Incubator Group Teleconference 08:58:01 Date: 03 June 2011 08:58:03 waves even! 08:58:07 gaedke has joined #webid 08:58:08 hi 08:58:22 elf-pavlik has joined #webid 09:00:26 bblfish: we're using [pgp-style] web of trust by reference 09:00:32 ....using x509 for the public key 09:00:52 ...the information is in these links between your homepages, so that your server decides to trust who it likes 09:01:04 ...you might create a group with edit permissions 09:01:18 q about domain names 09:01:27 bblfish: we can do it without domain names 09:01:46 bblfish needs to turn off bblfishes beep filter for bblfishes name 09:05:11 link for the videos: http://bblfish.net/blog/2011/05/25/ 09:05:19 http://www.youtube.com/watch?v=8iZPJBpI2Po 09:07:30 Video from Markus Sabello ist here http://ostatus.org/2010/10/26/ostatus-interview-markus-sabadello 09:07:40 bblfish: ietf emphasise what goes on the wire 09:07:46 (i thought he meant http://en.wikipedia.org/wiki/Robustness_principle but not sure now) 09:08:03 bblfish: if you can get the info you need from the profile doc, that's great; we're being format agnostic so far 09:08:25 bblfish: compatibility concerns -> why it's important to have test suites 09:08:37 ...where all implementors collab 09:08:55 ...without a test suite it's really hard to figure out what is happening, going wrong, 'cos SSL is all encrypted 09:09:05 so this helps with better responses for user when things fail 09:09:12 ...also helps us understand which tools are doing what 09:09:26 ... eg. this one understands/doesn't understand rdfa; this one logs me in even though no foaf file, etc 09:09:39 ...could come to conclusions eg. to use webfinger, we can get a measure of which systems can work with it 09:09:54 ...measures and stats give us understanding and help people know what to implement 09:10:15 myprofiletshirtguy: one advantage here is that there is no need to create APIs 09:14:54 q+ 09:16:03 having too many protocols to represent WebID data could pose problems on the long run; there can be cases where endpoints will not be able to understand a certain protocol 09:16:45 q+ 09:18:27 point on usability of email style formated identifiers over URI since people already relate name@domain to people 09:22:20 evan praises webfinger ;) 09:22:44 q- 09:24:50 we could, if we get bblfish 's attention 09:27:51 danbri presents sketch on dimentions with ID system, Profile Content... (can someone take a photo?) 09:47:20 discussion on 3rd parties which can take role of 'vouching' for someones identity 09:47:34 q+ re timekeeping / goals for rest of meeting (do we finish in 10 mins, per http://d-cent.org/fsw2011/agenda/ ) 09:47:45 domel has joined #webid 09:47:46 q- 09:48:25 q? 10:03:38 screening video of webid on cryptostick from: http://bblfish.net/blog/2011/05/25/ 10:06:57 is Andrei Sambra in the room? sorry for the names/faces fail... 10:10:31 I am 10:10:39 the myprofiletshirt guy 11:03:03 mischat_ has joined #webid 11:23:42 bblfish has joined #webid 11:31:52 bblfish has joined #webid 11:33:41 hi 11:33:47 mike has joined #webid 11:35:06 Deiu has joined #webid 11:37:28 Galaxor has joined #webid 11:37:31 domel has joined #webid 11:37:31 Hello. 11:37:33 http://bblfish.net/blog/2011/05/25/ 11:41:41 * Resuming the WebID XG meeting 11:42:19 it is important that we pick only formats which are capable of representing certificates 11:43:00 (ref. drawing) 11:43:42 preferred are the rdf sepcifies formats in particular rdf/xml, and rdfa 11:45:24 Cert/rsa ontology would be preferred ontolgy 11:45:42 format == Doc Syntax (ref. drawing) 11:46:11 http/https/ftp? are prefferred URI schemes 11:46:29 Cert/rsa ontology == Profile Content (ref. drawing) 11:46:54 gaedke has joined #webid 11:49:36 Make it clear in the spec that the RelyingParty decides on the authorization strength required to access a resource: ie: an http:// URI may not be strong enough a webid for some services 11:51:20 http://www.w3.org/ns/auth/cert 11:51:43 http://www.daml.org/ontologies/235 11:51:49 EARL ontology ^ 11:52:00 http://www.w3.org/TR/EARL10-Schema/ 11:52:06 http://www.axolotlfarm.org/~bergi/projects/rme/files/20110306_3d_webid.jpg 11:54:13 ^ drawing we previously referred to 12:02:40 julia has joined #webid 12:06:13 julia, we're in the next room (further down the hall) 12:06:45 "Conference room 1" 12:12:58 we are discussing ISSEU-9 12:13:04 http://www.w3.org/2005/Incubator/webid/track/issues/9 12:37:59 sorry, have to work :( 13:08:07 The SubjectAltName MUST contain at least one WebID URI. 13:08:09 It MAY contain more than one URI, but if it does each URI SHOULD point to the Same Document Content (i.e. mirror). 13:08:10 If the URIs do not point to the same document the server SHOULD resolve all URIs and construct a single graph. 13:08:12 If the Server does not resolve all different URIs then any resulting authorisation decision will be undefined. 13:08:18 I think this is what I meant! 13:15:03 humph, Mirrors might not work 13:19:34 domel has joined #webid 13:36:43 danbri2 has joined #webid 13:40:19 MacTed has joined #webid 13:40:23 trackbot, end meeting 13:40:23 Zakim, list attendees 13:40:23 sorry, trackbot, I don't know what conference this is 13:40:24 RRSAgent, please draft minutes 13:40:24 I have made the request to generate http://www.w3.org/2011/06/03-webid-minutes.html trackbot 13:40:25 RRSAgent, bye 13:40:25 I see no action items