01:02:35 olyerickson has joined #GLD 01:02:39 olyerickson has left #GLD 11:04:04 RRSAgent has joined #gld 11:04:04 logging to http://www.w3.org/2012/01/26-gld-irc 11:04:13 fadi has joined #gld 11:04:13 Zakim has joined #gld 11:04:19 ACTION: cygri to move dcat-related content from eGov wiki to GLD wiki 11:04:19 Created ACTION-37 - Move dcat-related content from eGov wiki to GLD wiki [on Richard Cyganiak - due 2012-02-02]. 11:05:36 close Action-29 Completed 26/1/12 11:21:53 olyerickson has joined #GLD 11:21:55 olyerickson has left #GLD 11:33:03 action-29 Close 11:34:14 close Action-29 11:34:15 ACTION-29 Add products on issue tracker closed 11:36:44 action: PhilA to convert editors' draft of DCAT to make use of respec 11:36:45 Created ACTION-38 - Convert editors' draft of DCAT to make use of respec [on Phil Archer - due 2012-02-02]. 11:37:10 ACTION: cygri to update http://vocab.deri.ie/dcat to point to the new dcat ED 11:37:10 Created ACTION-39 - Update http://vocab.deri.ie/dcat to point to the new dcat ED [on Richard Cyganiak - due 2012-02-02]. 11:47:55 mhausenblas has joined #gld 11:53:21 dvilasuero has joined #gld 11:57:47 zakim, who is on the phone 11:57:47 I don't understand 'who is on the phone', cygri 11:57:55 Does zakim know that this IRC channel is connected to our call? 11:57:58 zakim, who is on the phone? 11:57:58 sorry, cygri, I don't know what conference this is 11:57:59 On IRC I see dvilasuero, mhausenblas, Zakim, fadi, RRSAgent, PhilA, cygri, csarven, BartvanLeeuwen, HadleyBeeman, cgueret_work, rreck, trackbot, sandro 11:58:05 zakim, this is GLD1 11:58:05 ok, HadleyBeeman; that matches SW_e-Gov( GLD)6:30AM 11:58:18 zakim, who is on the phone? 11:58:18 On the phone I see galway, HadleyBeeman, [LC] 11:58:27 zakim, fadi is with galway 11:58:27 +fadi; got it 11:58:34 zakim, PhilA is with galway 11:58:34 +PhilA; got it 11:58:39 zakim, dvilasuero is with galway 11:58:39 +dvilasuero; got it 11:58:43 zakim, i'm with galway 11:58:43 +cygri; got it 11:58:48 GofranShukair has joined #gld 11:58:49 t_gheen has joined #gld 11:58:57 zakim, mhausenblas is with galway 11:58:57 +mhausenblas; got it 11:59:08 zakim, GofranShukair is with galway 11:59:08 +GofranShukair; got it 11:59:23 zakim, BartvanLeeuwen is with galway 11:59:23 +BartvanLeeuwen; got it 11:59:33 zakim, csarven is with galway 11:59:33 +csarven; got it 12:00:08 (ghislain, boris, spyros and deirdre are not yet on IRC) 12:00:10 gatemezin has joined #gld 12:00:30 BenediktKaempgen has joined #gld 12:00:35 zakim, BenediktKaempgen is with galway 12:00:35 +BenediktKaempgen; got it 12:00:42 zakim, gatemezin is with galway 12:00:42 +gatemezin; got it 12:00:48 thanks, cygri 12:00:57 @cygri, thanks!! 12:01:04 +sandro 12:01:19 zakim, who is on the phone? 12:01:19 On the phone I see galway, HadleyBeeman, [LC], sandro 12:01:20 galway has galway, fadi, PhilA, dvilasuero, cygri, mhausenblas, GofranShukair, BartvanLeeuwen, csarven, BenediktKaempgen, gatemezin 12:01:32 +olyerickson 12:02:34 :) 12:04:57 boris has joined #gld 12:05:06 +GeraldSteeman 12:05:43 zakim, who's here>? 12:05:43 I don't understand your question, mhausenblas. 12:05:45 zakim, who's here? 12:05:45 On the phone I see galway, HadleyBeeman, [LC], sandro, olyerickson, GeraldSteeman 12:05:47 galway has galway, fadi, PhilA, dvilasuero, cygri, mhausenblas, GofranShukair, BartvanLeeuwen, csarven, BenediktKaempgen, gatemezin 12:05:50 On IRC I see boris, BenediktKaempgen, gatemezin, t_gheen, GofranShukair, dvilasuero, mhausenblas, Zakim, fadi, RRSAgent, PhilA, cygri, csarven, BartvanLeeuwen, HadleyBeeman, 12:05:53 ... cgueret_work, rreck, trackbot, sandro 12:06:07 zakim, boris is with galway 12:06:07 +boris; got it 12:06:10 +Washington 12:06:12 GeraldSteeman has joined #GLD 12:06:17 Morning, Washington 12:07:06 Mike_Pendleton has joined #gld 12:09:04 Wasn't there going to be some breakout work from eGov as well (on DCAT)? 12:09:16 Zakim, [LC] is me 12:09:16 +t_gheen; got it 12:09:58 spyroskotoulas has joined #gld 12:12:34 olyerickson has joined #gld 12:12:48 DeirdreLee has joined #gld 12:12:51 cmusialek has joined #gld 12:12:52 scribe: cygri 12:12:58 zakim, spyroskotoulas is with galway 12:12:58 +spyroskotoulas; got it 12:13:04 zakim, DeirdreLee is with galway 12:13:04 +DeirdreLee; got it 12:13:08 stasinos has joined #gld 12:14:28 gatemezin: ghislain atemezing, EURECOM, france 12:14:47 DaveReynolds has joined #gld 12:14:51 ACTION-31? 12:14:51 ACTION-31 -- Boris Villazón-Terrazas to create a Wiki page on multi-lingualism of vocabs -- due 2012-02-01 -- OPEN 12:14:51 http://www.w3.org/2011/gld/track/actions/31 12:14:57 topic: Report on work since yesterday 12:15:02 George has joined #gld 12:15:08 http://www.w3.org/2011/gld/wiki/Multi-lingualismOfVocabs 12:15:10 close ACTION-31 12:15:10 ACTION-31 Create a Wiki page on multi-lingualism of vocabs closed 12:15:12 boris: we created a wiki page on multilingual issues 12:15:30 +[IPcaller] 12:15:32 close ACTION-32? 12:15:35 mhausenblas: all please contribute to this page 12:15:38 ACTION-32? 12:15:38 ACTION-32 -- Michael Hausenblas to compile first version of vocabulary selection quality checklist -- due 2012-02-01 -- OPEN 12:15:38 http://www.w3.org/2011/gld/track/actions/32 12:15:42 zakim, IPcaller is me 12:15:42 +DaveReynolds; got it 12:15:47 zakim, mute me 12:15:47 DaveReynolds should now be muted 12:15:50 +[IPcaller] 12:16:00 close ACTION-32 12:16:00 ACTION-32 Compile first version of vocabulary selection quality checklist closed 12:16:02 http://www.w3.org/2011/gld/wiki/VocabularySelectionQualityChecklist 12:16:13 mhausenblas: we did a first cut of vocabulary selection checklist 12:16:15 Zakim, [IPcaller] is stasinos 12:16:15 +stasinos; got it 12:16:47 bhyland has joined #gld 12:16:59 q+ 12:17:07 mhausenblas: vocabulary selection might be too restrictive, so we reinterpreted as "dealing with vocabularies" 12:17:17 ... to cover vocabulary discovery, selection and creation 12:18:00 ... we expect that most users will be well-served by info on discovery+selection 12:18:01 DanG has joined #gld 12:18:08 ... but some will need to create new ones 12:18:41 ... discussing ontology creation methodologies are out of scope but might point to them informatively 12:19:27 ... versioning ... 12:20:17 ... flow chart ... driven by usage ... add/remove terms ... 12:20:36 ... deprecating vocabularies 12:20:51 ... some cross-cutting issues 12:20:55 olyerickson1 has joined #GLD 12:21:16 ... like stability 12:21:38 ack cygri 12:21:51 cygri: This was all about vocab selection? 12:22:00 When I browse to the Vocab Selection wiki, it doesn't show me as logged in...even though I'm logged in 12:22:04 cygri: No, part 1 was selection and discover, part 2 was about management 12:22:31 s/cygri:/mhausenblas:/ 12:22:59 mhausenblas: We said we want to provide a checklist, not a list of recommended vocabs 12:23:23 [[Vocabulary Selection. The group will provide advice on how governments should select RDF vocabulary terms (URIs), including advice as to when they should mint their own. This advice will take into account issues of stability, security, and long-term maintenance commitment, as well as other factors that may arise during the group's work.] 12:23:24 cygri: The charter doesn't mention vocab creation. It seems that we're stretching the charter 12:23:30 "advice as to when they should mint their own" 12:23:36 (but not *how* :-) 12:24:12 cygri: So my preference would be to stop at the point where selection and discovery fails 12:24:22 q? 12:24:23 Exactly, don't try to give pointers to advice on vocabulary creation. There's lots out there already and doing a comprehensive enough job seems out of scope. 12:24:24 q= 12:24:25 q+ 12:24:50 ‰q+ 12:24:58 q? 12:25:01 mhausenblas: There aren't any established BPs for vocab creation, stuff like deprecating terms and so on. 12:25:03 q+ 12:25:18 mhausenblas: If you don't talk about deprecation at all then people may think that it isn't possible 12:25:38 So explicitly state what issues are NOT covered, but don't try to partially cover then through "informative" sections. 12:25:38 mhausenblas: But people should be aware of the issues around creation 12:26:26 mhausenblas: So I agree with cygri - but we should focus on selection and discovery but then include a paragraph talking about what the issues are? 12:26:36 cygri: The otehr things was stability, versioning etc. 12:27:06 s/otehr/other 12:27:08 cygri: Is it worth breaking those out in the vocab selection? They get discussed in the BP document anyway so can we just refer to that? 12:27:14 I think we need to make stakeholders aware (a) that vocab selection matters (b) that there are best practices for selecting vocabs, based on common usage (c) that custom creation is possible but should be deferred if prior existing vocabs exist (d) that long-turn "stability" of vocabularies may be a factor 12:27:35 sandro: I agree with what's being sai 12:27:41 s/sai/said/ 12:27:57 good point sandro 12:28:44 sandro: when we say what consumers are looking for in a vocabulary, this also helps producers to understand what vocabulary consumers are looking for 12:28:54 ... so it's discovery/selection/evaluation 12:29:42 q+ 12:29:42 We should provide guidance (or pointers) to "evaluation criteria" rather than specific evaluation criteria. Also, evaluation criteria (and ratings systems0 for vocabs are evolving 12:29:43 mhausenblas: eager to capture experience of vocabulary maintainers, like danbri 12:29:47 q? 12:30:10 ack sandro 12:30:14 bhyland: creation of vocabularies should be a book of its own 12:30:15 ack bhyland 12:30:57 ... better to restrict to selection criteria. pay attention to who maintains the vocabulary, is there a long-term maintenance plan in place etc 12:31:08 ack 12:31:11 ack PhilA 12:31:31 PhilA: i wrote stuff for the EC last year that covers much of what we just talked about. i'll contribute that 12:32:07 action: PhilA to reflect on SEMIC advice on vocab selection etc. to see if there is more to contribute to the BP doc 12:32:07 Created ACTION-40 - Reflect on SEMIC advice on vocab selection etc. to see if there is more to contribute to the BP doc [on Phil Archer - due 2012-02-02]. 12:32:13 https://www.w3.org/2011/gld/track/actions/open 12:32:43 @Michael, et al, are we all agreed this is the main wiki page for Vocabulary discussion from which all other sub pages will be linked? See http://www.w3.org/2011/gld/wiki/Vocabulary_Discussion_Summary 12:32:46 q+ to talk about on how to use products (very quickly) 12:33:12 http://dvcs.w3.org/hg/gld/raw-file/default/dcat/index.html 12:33:22 Michael: Yes, bhyland, I think so 12:33:30 ta 12:33:40 http://www.w3.org/2011/gld/track/products/2 12:33:52 I have linked the newly public Editors; draft from today's agenda 12:33:58 http://www.w3.org/2011/gld/wiki/Data_Catalog_Vocabulary 12:34:25 ack mhausenblas 12:34:25 mhausenblas, you wanted to talk about on how to use products (very quickly) 12:34:54 cygri: we have a dcat editor's draft, updated list of dcat issues, and a stub wiki page for dcat on the gld wiki 12:35:08 mhausenblas: we now have separate products for dcat, best practices, cube in the tracker 12:35:12 What is the list of "products" in Tracker for us to assign? 12:35:19 ... so please assign new issues to the respective product 12:35:23 cmusialek has joined #gld 12:35:25 http://www.w3.org/2011/gld/track/products 12:35:41 Yigal has joined #Gld 12:36:38 mhausenblas: when you create/edit an issue, there's a product dropdown 12:36:45 ... i think you can't assign issues to products from IRC 12:36:47 bhyland you can create in IRC then fine-tune in the hyperinterface 12:36:58 George_ has joined #gld 12:37:54 topic: Standard Vocabularies 12:38:06 PLEASE specify pages when we're talking about specific pages 12:38:11 bhyland: there's a lengthy list of people here http://www.w3.org/2011/gld/wiki/Vocabulary_Discussion_Summary#Vocabulary_5:_Geography.2C_Spatial_Information 12:38:56 George has joined #gld 12:39:03 ... whom do i chase? 12:39:16 PhilA: for dcat, that's me, fadi, john, richard 12:39:27 cygri: for data cube, we have a list from yesterday 12:39:48 mhausenblas: looking at the charter, how do we break this down into specs? 12:39:51 q+ 12:40:15 sandro: no umbrella spec necessary 12:40:28 bhyland: we talked about it a bit yesterday 12:40:49 Surely vocab guidance is in Best Practices document 12:40:55 ... i think we might want to have an umbrella spec about selection etc 12:41:10 sandro: the umbrella spec should be the Best Practices 12:41:26 mhausenblas: so for each of the five areas in Standard Vocabularies, what do we do? 12:41:26 What "5 points" where are we looking... 12:41:38 olyerickson, look at the charter 12:41:56 Okay thanks 12:42:01 mhausenblas: charter, section 2.3 12:42:32 ... metadata corresponds to dcat, statistical cube data to data cube, don't know about the rest 12:42:47 q? 12:42:51 q- 12:43:15 Thanks mhausenblas (just trying to make sure we have links with words like "these" ;) ) 12:43:30 PhilA: the work i'm currently doing for the EC covers people, legal entities 12:43:43 ... i'd like to put some energy into organization ontology 12:43:49 Michael: I'd be interested in learning from DaveReynolds if he'd be willing to/interested to move ORG ontology into W3C (see 4. in section 2.3 of our charter) 12:43:53 q+ 12:44:02 ack me 12:44:10 ack me 12:44:46 DaveReynolds: transferring into w3c namespace and w3c care would be good 12:44:55 ... i can do very little work on that though 12:45:04 ... it's completely public domain, so no ip issues 12:45:12 I'd be interested in putting some energy into the organization ontology as well. 12:45:49 PROPOSAL: Moving http://www.epimorphics.com/public/vocabulary/org.html into W3C namespace and consider it as addressing 4. of section 2.3 of our charter 12:45:59 q+ to ask about timescales 12:46:02 gatemezi has joined #gld 12:46:03 Data.gov is interested in implementing an organization ontology for US govt entities in the short term 12:46:14 q? 12:46:35 http://www.epimorphics.com/public/vocabulary/org.html 12:46:49 ack DanG 12:46:54 ack DaveReynolds 12:46:54 DaveReynolds, you wanted to ask about timescales 12:47:28 DaveReynolds: this ontology is aimed at generic re-usable concepts. so it has to be extended for particular used 12:47:34 q+ to clarify his proposal 12:47:37 s/particular used/particular uses/ 12:47:57 ... so data.gov.uk had to extend it for UK gov use 12:48:05 charter: http://www.w3.org/2011/gld/charter 12:48:15 DaveReynolds: what's the timescale? 12:48:18 q? 12:48:26 q+ to talk about http://schema.org/Organization 12:48:40 DanG has left #gld 12:49:06 Wonder if there are some good Data.gov datasets with org data that could be useful test cases 12:49:21 charter says: FPWD in Dec 2011, LC Oct 2012, CR Dec 2012, PR Mar 2013, Rec Apr 2013 12:49:41 PhilA: should be not much work given the pedigree and uptake of this work 12:49:42 I used Site from Org to get to VCard:Address stuff 12:49:59 q? 12:50:18 DanG has joined #gld 12:50:30 Cygri: where is the UK govt's ontology implemented? Do you have a link to share? 12:50:46 cmusialek, that's a question for DaveReynolds 12:50:51 DaveReynolds: the issue is not the amount of time writing stuff; it's about public review, coordination etc 12:51:13 ... ideally we could serialize this, make progress on the data cube first, then org etc 12:51:14 DaveReynolds: I'd prefer to serialize this work, doing QB first. 12:51:23 q? 12:51:23 ack me 12:51:24 mhausenblas, you wanted to clarify his proposal 12:51:25 ack mhausenblas 12:52:02 mhausenblas: i disagree with serialization. we should send a signal soon, by doing FPWDs of whatever we have now 12:52:07 +1 mhausenblas 12:52:20 ... so that the world sees: these are the things in our scope 12:52:46 ... i agree that we can do serial focus once FPWDs are out 12:53:00 ... we should get FPWDs out in a matter of weeks 12:53:06 +1 mhausenblas 12:53:19 bhyland: i agree 12:53:56 +1 mhausenblas 12:53:57 q- 12:54:00 cmusialek: see http://health.data.gov/doc/hospital/393303/site/1 12:54:02 q? 12:54:46 PROPOSAL: Moving http://www.epimorphics.com/public/vocabulary/org.html into W3C namespace and consider it as addressing 4. of section 2.3 of our charter 12:54:51 +1 12:54:57 +1 12:54:59 +1 12:55:03 +1 12:55:15 +1 12:55:16 +1 12:55:19 +1 to schema.org not being appropriate for this 12:55:26 +1 (reconsider if we find any other viable options) 12:55:32 +1 12:55:33 +1 12:55:35 make what happen? 12:56:03 q+ 12:56:07 q? 12:56:26 RESOLUTION: Moving http://www.epimorphics.com/public/vocabulary/org.html into W3C namespace and consider it as addressing 4. of section 2.3 of our charter 12:56:28 action: PhilA to create W3C format of Org ontology specification document 12:56:28 Created ACTION-41 - Create W3C format of Org ontology specification document [on Phil Archer - due 2012-02-02]. 12:56:31 ack olyerickson 12:56:49 @Sandro - do we write APPROVED for the proposal to capture in minutes? 12:57:04 olyerickson: we've done some work on schema.org extensions in other areas 12:57:11 q+ to note that we have not discussed 3. People of 2.3 12:57:15 bhyland, we write RESOLUTION like i did 12:57:27 @PhilA - thanks! 12:58:07 @PhilA, I particulary like that due date: 2012-02-02 ;-) 12:58:07 olyerickson: just because schema.org doesn't cover something right now, this doesn't mean we can't extend it 12:58:10 bhyland, cygri did it fine, "RESOLUTION:" or "RESOLVED:" or "APPROVED:" should all work. 12:58:17 @sandro ta 12:58:37 Michael: Wondering if anyone fancies an action for cleaning up http://www.w3.org/2011/gld/wiki/Vocabulary_Discussion_Summary and sync w/ today's resolution 12:58:38 q? 12:58:49 topic: ADMS discussion 12:58:58 ack me 12:58:58 mhausenblas, you wanted to note that we have not discussed 3. People of 2.3 12:59:32 scribenick: BenediktKaempgen 12:59:51 Topic: ADMS 13:00:18 Yigal has joined #gld 13:00:48 EU Commission, Asset Description Metadata Schema (ADMS) 13:00:56 I can take an action for cleaning up http://www.w3.org/2011/gld/wiki/Vocabulary_Discussion_Summary 13:01:42 bhyland: any wishes to rearrange agenda? 13:01:55 FWIW: People interested in RPI's DCAT-driven Schema.org extension for Catalogs and Datasets can check out demo at: http://logd.tw.rpi.edu/schemaorg_dataset_extension 13:03:04 PhilA: Comment - hopes to make the most of the time 13:03:32 PhilA: Interoperable Solutions - big EU activity 13:04:13 ... two strangs: ADMS, Section on Core Vocabularies 13:04:28 ... Fadi, Gofran more on ADMS 13:05:10 ... UML diagram in the wiki - http://philarcher.org/isa/adms.png 13:06:05 ... describing meta data. Meeting in March: Using ADMS to interchange metadata. 13:06:55 ... lots of similarities with dcat: repository, asset, release of asset (in particular format) 13:07:26 -DaveReynolds 13:07:31 GofranShukair: asset can be dataset but reusable one 13:08:17 ... release (actual document representing asset) 13:08:30 @dvilasuero, thanks for cleaning up the vocab discussion summary page. We made some good progress today and it would be great to reflect that as a status update on that page and link to all the links provided in IRC today. 13:08:38 ping 13:08:43 ... asset, release have statuses (e.g., already published) 13:09:07 ping 13:09:36 +??P7 13:09:44 zakim, ??P7 is me 13:09:44 +DaveReynolds; got it 13:09:54 zakim, mute me 13:09:54 DaveReynolds should now be muted 13:09:56 ... idea behind ADMS: semantic assets making reusable. E.g., asset metadata, federation (professionals can find assets) 13:09:58 much better :-) 13:10:18 ... federation (explore, reuse of assets) 13:10:33 q? 13:10:42 PhilA: model is actually in public review 13:10:54 ... has well pedigree 13:11:00 @dvilasuero, thanks very much for tidying the vocab discussion summary page and reflecting what was discussed today. 13:11:03 ... through ? 13:11:32 ping 13:11:37 cmusialek has joined #gld 13:11:39 ACTION: cygri to update http://www.w3.org/2011/gld/wiki/Data_Cube_Vocabulary 13:11:39 Created ACTION-42 - Update http://www.w3.org/2011/gld/wiki/Data_Cube_Vocabulary [on Richard Cyganiak - due 2012-02-02]. 13:12:18 ... reuse of dcat repos, asset, relesase, lots of references to dcat, also to void, foaf 13:13:54 ... issue of dcat: particular use of term/class, and we have ranges: it can be that we are making relationships that we are not allowed to make. 13:14:25 ... wants to know whether this is of interest to US people 13:14:51 ... published as XML, RDF... 13:15:36 ... no problem to change example.org to w3c.org (TBL did not mind) 13:16:22 ... EU has concerns, e.g., about stability (change control) 13:17:02 ... politicians probably will have concerns. 13:18:06 q+ 13:18:13 sandro: Probably, it would be easier for US standards 13:18:19 rreck1 has joined #gld 13:18:45 (that wasn't sandro, BenediktKaempgen... didn't catch who it was.) 13:18:54 then it was george 13:19:05 I mix you often ;-) 13:19:05 Mike_Pendleton has joined #gld 13:19:06 s/sandro:/george:/ 13:19:52 ?: Interested. 13:20:05 yeah i wanted google+ yesterday 13:20:39 US Gov agency adoption of ADMS will be greatly facilitated by having ADMS namespace be provided by a 'voluntary consensus standards organization' (of which W3 is an important one) 13:21:13 s/?/cmusialek 13:22:04 PhilA: Will be elaborating on relationship to dublin core. 13:22:10 ... later this day. 13:23:03 ... e.g., will inferencing change concepts that are linked by ADMS. 13:23:04 Technically correct practice is to use OWL restrictions :) 13:23:48 +1 DaveReynolds 13:23:51 s\void\dublin core 13:25:01 s/void/dublin core 13:25:29 Arghh my tax dollars at work 13:25:44 can someone in washington try g+ on their laptop, to see if it sticks to port 80 or something? 13:26:11 PhilA: Second section: Core vocabularies. 13:26:43 ... EU Commission wants to recommends vocabulary to be used cross-country; possible to specialize. 13:26:45 noone here is willing to try 13:27:43 ... based upon lots of resources: First core vocabularies: person, business, location 13:27:50 http://philarcher.org/isa/corevocs.png 13:27:51 Link please 13:27:53 thanks 13:28:50 ... background: experts on vocabularies, Euro justice, business registrars, INSPIRE directive secretar (environmental data) 13:29:13 ... all three things are interlinked. 13:29:39 ISADate? 13:30:04 ... properties should be familiar. No relationships between persons. Only most important features. 13:30:09 -HadleyBeeman 13:30:41 ... without reference to other vocabs, but implicit references should be obvious (e.g., foaf) 13:31:01 Greek too 13:31:16 ... cultural differences covered e.g., patronymic Name 13:32:07 ... dates raise big problem: 13:32:15 bhyland has joined #gld 13:32:17 ping 13:32:25 ... many people do not know their birthdate or place 13:32:25 pong 13:33:10 ... recording dates: most dates in public databases not clearly defined 13:33:30 ... to represent those, raises big issues. 13:34:28 ... Cleaning would sometimes even make dates inaccurate (e.g., from August 1984 to midnight 1. August 1984) 13:34:34 PhilA: If you know dat, use xsd:date 13:35:36 ...if you can't type to xsd: date, use a literal with whatever you have 13:35:38 sigh. what a pain. not sure if there's a better solution. 13:35:38 sounds like a sane approach 13:36:04 i'd prefer xsd:gYear or xsd:gYearMonth over w3cdtf 13:36:11 ... actual recommendation would be to represent the date depending on the situation (e.g., representing parts separately). 13:36:13 Yes, there is a difference between date and datetime. Much gov data is actually about intervals, not dateTime points, hence the UK reference time service for time intervals. 13:36:45 I'd be inclined to use different properties, I think. one if you know it, one for a comment, especially if you dont know the actual value. 13:37:00 @sandro @cygri Our guys have suggested xsd: date then xsd: g* for date parts that are known 13:37:05 ... Next businesses: also issues to represent legal entities 13:37:27 ... Legal entities must have a legal identifier (registrar). 13:37:40 +1 to sandro, semantics are different if you are giving constraint or hints instead of value, so use different property 13:37:47 ... eg.., tax registration 13:38:33 ... Therfore identifier as an own class. Person: People have identifiers, also. 13:38:54 ... Diagram: http://philarcher.org/isa/corevocs.png 13:39:25 ... Dbpedia is used for location. 13:40:01 ... Address is also difficult: In the end we use dcat. 13:40:12 s/we use dcat/we use vcard/ 13:40:15 PhilA: Address gets all the attention, in the end we use vcard 13:40:16 s/dcat/vcat 13:40:24 q? 13:40:31 q+ 13:40:33 thanks cygri, you were faster 13:40:36 ... "addresses are a mine field" 13:40:51 ...none of these things record change 13:41:04 ...everything can change, we don't know how to do it 13:41:05 ... recognize need to record changes 13:41:21 ack cmusialek 13:41:26 ack DeirdreLee 13:41:35 ..."more research is necessary" (it is left as an exercise ;) ) 13:42:16 DeirdreLee: INSPIRE is complex, but this is their standard, how to resolve issues with relationship with INSPIRE and vcard. 13:42:27 DanG has joined #gld 13:42:34 PhilA: INSPIRE and vcard do not much diverge. 13:42:51 DanG has left #gld 13:43:12 DanG has joined #gld 13:43:17 PhilA: INSPIRE directive has legal force 13:43:24 ..."you shall use it..." 13:43:33 ... will make sure to make proper reference. 13:43:46 ...usage guidelines will specify how "they" map 13:44:15 george: Instance examples...illustrating mapping? 13:44:22 george: examples available for mapping to recommended vocabs 13:44:32 PhilA: usage guiamplesdelines will include instance data/ex 13:45:12 PhilA: does effort match to things you do in the US 13:46:00 DanG: Recommends to look at something. Will give link. 13:46:43 ISO 19773 13:46:45 19773 ISO 13:47:28 PhilA: Only small amount of uri's needed to be minted in Core Vocabs. 13:47:33 Doesn't seem to be free: http://www.iso.org/iso/iso_catalogue/catalogue_tc/catalogue_detail.htm?csnumber=41769 13:47:53 bhyland: title for vocab diagram? 13:48:30 -stasinos 13:48:51 q+ 13:49:02 ack had 13:49:07 + to "Thanks PhilA" 13:49:09 this MDR standard is only relted to schemas 13:49:26 ack HadleyBeeman 13:49:44 sorry — google plus is failing me 13:49:50 Title for the model Phil described "ISA Core Vocabulary Combined Conceptual Model" 13:50:03 I just wanted to know if member state representation has been… representtative. Are you happy with what you have? 13:50:16 Ahhh… no wonder. I've signed off from Zakim's telecon 13:50:57 PhilA: some but not enough member state representations. 13:51:27 Fair enough, PhilA. I was just wondering about status on that. Thanks 13:51:28 q? 13:51:45 ... is difficult to get them involved. Talking to various folks. Open to recommendations to whom they should be talking to. 13:52:37 Link to ISO/IEC 19773 is http://webstore.iec.ch/preview/info_isoiec19773%7Bed1.0%7Den.pdf 13:52:55 Let me know if this doesn't work. 13:54:23 WAIT 13:54:24 Topic: Procurement use cases. 13:54:58 is DERI on break 13:54:58 or just Michael? 13:55:24 MichaelPendleton: Issues, e.g., scope: guidance to people that needs to make that procurment happen (e.g., contract officers). Could be broader, also. 13:55:47 ... some text available but can be improved upon. 13:56:41 ... community directory part will be talked about later. 13:56:55 Point of order: could we please provide links before commencing with presos? 13:57:11 ... Slides: http://www.slideshare.net/michaelpendleton1/best-practices-procurement-of-linked-data-services 13:58:15 olyerickson, the link is in the agenda 13:58:24 ... possible questions regarding procurement, e.g., connection to community directory. 13:58:34 ... Should scope be broader? 13:59:02 q+ 13:59:12 ack me 14:00:04 PhilA: So many ways where procurement is relevant (not only for government). 14:00:28 ... How to know about own or external expertise? 14:01:34 bhyland: Institutions need to know what is different in publishing Linked Data from publishing content on the web of documents (which they are doing for a long time already). 14:02:28 bhyland: "let me help you with some collateral et.al. to get you up-to-speed on different types of services" 14:02:59 phila: heard a comment, it all sounds terribly US/UK 14:03:04 PhilA: Regarding, internationalizing it. UK is interested in it. 14:03:33 ...UK public consultation coming up "soon" 14:03:40 ... UK wants to include open standards in their procurement process 14:03:51 Just to add: 14:03:55 ... but first they need to know what standard 14:03:55 ...to define what an "open standard" is 14:04:34 bhyland: need other resources besides John Sheridan 14:04:37 the reason that this is a big deal NOW is that Cabinet Office now hava new centralised control over procurement— so the outcomes of this consultation can be rolled out to new effectiveness 14:04:44 I'm here— need to restart G+ 14:04:46 be right back 14:05:07 bhyland: not got john sherridan involved, yet. 14:05:31 PhilA: Hadley is the best "line of action" 14:06:15 I'm back now… Can I help? 14:06:40 ... can ask around but does not have a specific person in mind. 14:07:01 Question (since I can't use audio): Is it necessary to have the procurement checklist? Having a model of types of services makes sense. The checklist though seems to be based on a lot of assumptions which aren't universal. 14:07:14 Thaaaaaanks Bernadette 14:07:44 Not convinced W3C should be advising on procurement principles. 14:08:21 DaveReynolds, not principles, just products. 14:08:30 bhyland: glossaries part of recommendation? 14:08:31 +1 for glossary 14:08:40 W3C Glossary http://www.w3.org/2003/glossary/ 14:08:46 danbri has joined #gld 14:09:23 sandro: the principles of technology are OK but principles for *procurement*, NO! 14:09:31 PhilA: Not sure whether W3C glossary is still maintained. 14:09:50 DaveReynolds, agreed, absolutely. 14:10:16 sandro: so do you agree with having the current material from the wiki on a rec? 14:10:23 ping 14:10:38 sure, nP 14:11:16 sandro: does not understand procurement 14:11:37 george: it's about defining what we're procuding. Defining buying a "linked data server", like they buy a "database server" 14:11:48 george: Procurement officers want a checklist. 14:11:50 george: what does it mean to provide a Linked Data server? 14:12:00 Much of current checklist is not that LInked Data specific 14:12:05 s/procuding/procuring/ 14:12:19 Having looked, it seems that the W3C glossary is no longer an option. Neither, at present, is the cheat sheet (http://www.w3.org/2009/cheatsheet/) as to get the data in there is quite a hurdle and I'm not sure it's the best medium anyway so, scrub that idea 14:12:26 Agree with importance, VERY worried about unintended consequences 14:12:44 Nothing from me; I am relatively clueless on 'procurement" 14:13:02 who creates the action item? 14:13:23 would be very interested in how you're imagining or examples of unintended consequences DaveReynolds 14:13:30 q+ 14:14:01 annew has joined #gld 14:14:15 ack me 14:15:12 Summary of Procurement Topic: We need to get from point A to point B... what are the barriers to remove and allow the technical officer to get LOD to the public. 14:15:21 PhilA: Recommends to use the wiki for glossary. 14:15:37 PhilA: rec'd "nice page on the wiki" 14:16:17 bhyland: takes action to create glossary for best practice document 14:16:40 bhyland: it's 9:16 14:16:45 action: bhyland to gather terms for a Glossary section in the BP document, then link that static list to the live wiki page where these will be repeated and updated over time 14:16:46 Created ACTION-43 - Gather terms for a Glossary section in the BP document, then link that static list to the live wiki page where these will be repeated and updated over time [on Bernadette Hyland - due 2012-02-02]. 14:16:47 Does someone want to scribe? 14:16:50 *Far out 14:17:06 -DaveReynolds 14:17:07 Topic: Stability 14:17:14 scribe PhilA 14:17:17 GofranShukair has joined #gld 14:17:23 Thanks, Phil. 14:17:35 rreck: Introduces himself 14:18:27 DC: Lots of noise... 14:19:00 rreck: What could influence the stability of LOD? 14:19:14 rreck: If the info is extremely valuable, it will last a long time 14:19:29 What are we looking at? 14:19:44 slides are linked on the F2F page 14:19:46 Links please before we start presos!!!! 14:19:56 http://iama.rrecktek.com/html/sites/iama.rrecktek.com/files/Data_Properties.pdf 14:20:01 rreck: is talking through http://iama.rrecktek.com/html/sites/iama.rrecktek.com/files/Data_Properties.pdf 14:20:24 mhausenblas, can you invite me to the cool kids? 14:20:26 second part of stability presentation will be http://www.w3.org/2011/gld/wiki/images/0/06/W3C-Washington2012_F2F2.pdf 14:20:44 George: examples include "government approved contract vehicle" which tend to be biased towards large companies, "interface to load data" which encourages a batch/static mindset instead of live integration, "Is the vendor or provider an active contributor to Standards groups" which again biases towards large companies. 14:21:48 I thought I had invited to one of my circles. 14:21:51 @annew yes but it is hard to juggle...we need "we're now looking at..." 14:21:51 thnx DaveReynolds understood 14:22:16 understood olyerickson 14:23:22 Yigal has joined #gld 14:24:05 I'm not scribing this as rreck's slides are a good record 14:24:12 q+ 14:24:37 Should HTTP URIs and attention to proper MIME types by the Linked Data client manage all this correctly? 14:25:11 q+ 14:25:13 ack me 14:25:15 Mike_Pendleton has joined #gld 14:25:56 PhilA: Pointing out that recommending not to use diacritic characters is not an internationally acceptable recommendation. 14:26:26 +1 PhilA 14:27:05 bhyland: Not sure whether this is relevant to the Gov Linked data WG - it's more generic and not specific to LD 14:27:20 ack me 14:27:20 q- bhyland 14:27:24 q? 14:27:28 q+ 14:27:31 q? 14:27:44 sandro: I share bhyland's thoughts 14:27:51 pop me from queue 14:28:07 sandro: stability here is about URI stability 14:28:07 ack olyrerickson 14:28:12 sandro: not sure the archive format is relevant. What is relevant in this space is URI persistence 14:28:22 Sandro:Stability is about maintaining persistent of a link, over time, that is the problem we are trying to solve. 14:28:25 PhilA: +1 - that's what I thought this session would be on 14:28:26 q+ 14:28:34 ack olyerickson 14:29:04 olyerickson: I wanted to disagree slightly with the point just taken 14:29:19 olyerickson: This touches on one of the conversations that we had yesterday 14:29:44 pop me from queue 14:29:50 Olyerickson: Disagrees slightly. Some of this touches on yesterday's conversation re: using good data management practices, but we should provide treatment of LOD differences. 14:30:06 olyerickson: It doesn't hurt to say that stakeholders should be using good data management lifecycle practices and then say that there are specific issues wrt LD that may not otherwise be obvious 14:31:00 ... The issue of different archive files is a problem RPI deals with daily. GB sized datafiles for download are non-trivial problems that we deal with somewhat uniquely within the LOD community. 14:31:37 q? 14:31:43 ack danG 14:31:52 DanG: I think I agree with olyerickson 14:31:53 cmusialek has joined #gld 14:31:57 The last speaker was me ;) 14:32:27 yeah, but we don't have the expertise/right to speak to data in general..... 14:32:30 DanG: Some of these recommendations are general and not specific to LD but they are specific to data and much of what is going to be said does still matter 14:32:39 ack DanG 14:32:44 annew has joined #gld 14:32:47 My point was there are *some* practices that are indeed unique to Linked Data 14:32:56 +1 sandro 14:33:09 q? 14:33:16 Are there other, more general W3C practices for data management that we can take in reference? 14:33:46 mhausenblas, yeah, I haven't been working on that this morning. 14:33:55 ...a provider can't trivially choose between formats they make available, etc... 14:34:14 bhyland: Suggest that we deal with - recognising that when you put data out ... 14:34:42 sandro: When i use RDF I refer to other people's URIs and I need some confidence in their management or my stuff will break 14:34:56 annew: That's part of the stability issue 14:35:30 bhyland: The other is dealing with very large file sizes. 14:35:47 bh: People don't download to their laptopns they work with them in the cloud 14:36:01 s/laptopns/laptops/ 14:36:40 @sandro I think I see the point --- hard for me to articulate, but this isn't about back-end stability, more about keeping the Web of Data stable 14:36:43 good question Hadley 14:36:49 q? 14:37:10 Mike_Pendleton: I'm happy to go back and make some revisions based on this interesting discussion 14:37:40 http://www.w3.org/2011/gld/wiki/images/0/06/W3C-Washington2012_F2F2.pdf 14:38:06 annew: Talking through http://www.w3.org/2011/gld/wiki/images/0/06/W3C-Washington2012_F2F2.pdf 14:38:07 bhyland has joined #gld 14:38:23 Summary of this topic (stability): 1) Stability is about maintaining persistent of a link, over time, that is the problem we are trying to solve. 2) Dealing with large file sizes. 14:39:03 Topic: Stability (continued) by AnneW 14:39:15 (Great, this stuff looks more in line with what I was expecting.... ) 14:39:46 MacTed has joined #gld 14:39:47 +1 14:40:27 AnneW: Best practices for Stability is all about "Making data available in perpetuity, persistently archived if necessary." 14:40:48 ... It is predictable, follows a logical format. 14:41:08 ... It is Externally visible and has stable consistent locations 14:41:24 +sandro.a 14:41:32 -sandro 14:41:43 ... provides a Legacy - uses earlier naming schemes, formats, data storage devices 14:42:26 ... Has stewards, someone needs to take responsibility - people are committed to consistently maintain specific datasets 14:42:26 q? 14:43:06 annew hadleybeeman was that "We have to have the Ability for Stability?" 14:43:13 ... If this is tied to support of a business unit, or legislative function, that is key. 14:43:28 Yep, olyerickson. That's the one. /cc annew 14:44:07 Contact and data consistency are related to success. Consistent infrastructure, and separation of internal politics and external stability. 14:44:46 q+ to highlight persistence WS http://www.w3.org/2001/tag/2011/12/dnap-workshop/notes.html 14:44:50 .... It is a good to have a data "last will & testament" to ensure your wishes are maintained in perpetuity. 14:45:24 The problem that estates have is that even if they are 'required' to persist (by policy or statute) they still might not b sustainable (no unfunded mandates) 14:45:35 ... I don't know what model we're going to recommend yet, but there are some for consideration. 14:45:50 q+ 14:45:59 Some models for stability include: Estate, Archives, Private Foundation, Government stewards, Internet organizations 14:46:56 q+ 14:47:14 q+ to comment on preservation of content vs preservation of access 14:47:53 Key concepts around interconnections. These are sources that establish a context for the production and/or use of an artifact. W3C Provenance. There are mechanims for persistence. Some are PURLs, handles. 14:48:12 q? 14:48:21 Key considerations: Preservation of Content, Preservation of Access, Conservation of media 14:49:10 ... Other considerations include how long term is long term? 2 years, 10 years, forever? Organizations need to consider this. 14:49:13 q? 14:49:17 Rock on 8 track tapes! 14:49:41 +[IPcaller] 14:49:43 http://www.w3.org/2011/gld/wiki/images/0/06/W3C-Washington2012_F2F2.pdf 14:49:51 http://www.w3.org/2011/gld/wiki/images/0/06/W3C-Washington2012_F2F2.pdf 14:50:08 Let me try again http://www.w3.org/2001/tag/2011/12/dnap-workshop/notes.html 14:50:13 chia ching! 14:51:05 Questions: PhilA mentioned workshop held earlier this month. Longevity differs depending on who you are speaking to. For example, a librarian things in centuries. 14:51:17 .cz has been gone *twice* 14:51:26 PhilA: we were reminded this weekend that the average life span of a government department in the UK is 5.5 years. 14:51:30 Various level domains have disappeared due to geographic boundaries changing, including countries. 14:51:37 Big implications for URI persistence/stability 14:52:01 ... Agreement with an institution in advance. For example, if W3.org goes away, then MIT.edu will pick it up. 14:52:54 RE "one of the registrars, it may have been someone from CNRI (representing Handles) or crossref (representing DOIs, based on Handles) 14:52:55 Cory has joined #gld 14:53:03 ... Top level domain for .arpa, only available if you have an RFC (Request for Comment). If you coordinate with IETC, you can get a .arpa domain. 14:53:27 .... someone suggested W3C should have w3.arpa, it is so important. 14:53:51 8 track = google + 14:53:59 ... DNS has been around for many decades, even longer than 8-track cartridges (which the cool kids know prevailed as a better technology solution) 14:54:07 q? 14:54:15 'for the life of the republic' 14:54:19 s/know prevailed/know should have prevailed/ 14:54:22 ack me 14:54:22 PhilA, you wanted to highlight persistence WS http://www.w3.org/2001/tag/2011/12/dnap-workshop/notes.html 14:55:03 olyerickson: Thanks annew for the talk. 14:55:13 olyerickson: I was involved in the handle.DOI discussion 14:55:24 q? 14:55:31 olyerickson: Thanks to AnneW for a very comprehensive talk that highlights her library science expertise/perspective. 14:55:39 olyerickson: When people set up institutional archives, a concern has been around what naming structure to use 14:56:24 ... Handles system - single source is a concern. What if CNRI went out of business, or Bob Kahn got hit by a bus. 14:56:52 DOI = Digital Object Identifier. A consortium of publishers created for commercial handles 14:57:04 ... people were concerned about (one or two) publishers backing DOIs ... too much central control. 14:57:36 ... Believes our WG's recommendations should help people make decisions. 14:57:47 handles http://handle.net from CNRI 14:57:53 ... PURLs infrastructure mentioned. 14:57:59 q? 14:58:03 bhyland 14:58:07 q+ 14:58:11 q- 14:58:21 ack Yigal 14:59:11 I think Web of Data (and persistence of links) adds new meaning to "preservation" 14:59:13 Yigal: NSF had a research program circa 2005 that looked into preservation of data. I remember a few things of note: 1) in order for things to be preserved, you must retain *interest* in the data. Maintenance of electronic data requires "care and feeding", a continued expense. 14:59:25 ...continuity of access <-> stability 14:59:25 ... if there is no perceived interest, these things will not be made available. 14:59:40 very good point - data won't survive loss of interest 14:59:52 @GeraldSteeman - can you chime in here about STI?? NASA's work??? 15:00:20 PhilA: Notes that W3C does not print its Recs. I believe that the IETF does print its RFCs 15:00:28 q? 15:00:30 I doubt storing paper is cheaper! 15:00:40 storing paper is different than migrating data. 15:01:02 migrating data required continuous activity and pruning and consideration 15:01:14 :-) 15:01:30 GeraldSteeman: Pressure within scientific & technical information community to digitize and provide guidance on longevity, access and of course, persistence. 15:01:44 ... If there is no interest, is there no value? 15:02:01 ... perceived value may change over time. Interest may change over time. 15:02:59 and the first electronic census is lost 15:03:02 DanG: shares the story about the circa 1960's data on some tape format that cannot be read. The 9 track tape readers have all gone to the dump and cannot get at the data. 15:03:19 That's really sad 15:03:19 George has joined #gld 15:03:27 q? 15:03:29 ... census data from 1960's data is lost while we have paper based records from the 19th centry that persisted. 15:03:36 q+ lunch 15:03:37 this is the danger of going electronic without considering the long term storage of it. 15:03:46 ack cygri 15:03:46 cygri, you wanted to comment on preservation of content vs preservation of access 15:04:05 cygri: There was a question about the disctinction between persistence of content and access 15:04:20 cygri: not sure where the draw the line between the 2 15:04:30 Cygri: persistence of access and content ... where do you draw the line. 15:04:37 cygri: I create a bunch of files with the RDF and structure to support it 15:04:57 cygri: where to draw the line, persistence of data/persistence(??) of access 15:04:58 cygri: Once the content that I set up no longer dereference, a big part of it has been lost 15:05:00 s/19th/18th 15:05:04 ... for content to persistent because someone has a copy of these files. But once the URIs don't de-reference any more, the value has been lost. 15:05:17 +1 to cygri's point that we need to preserve access, in addition to the content itself. Preserved content that no one can access isn't useful. 15:05:56 olyerickson... you just aren't cool ;-) 15:06:07 bhyland: Tries not to get into the nit picking between URI and URL. After lucnh we'll have a session on HttpRange14 15:06:13 Thus preserviing the value of URIs is very important, URIs must remain resolvable (agreed to not open URI vs URL discussion here ...). 15:06:27 cygri: The 2nd question concerns the stages that might kill the stability of deployed data 15:06:29 We can say there are staged events to help stability of deployed content ... 15:06:47 cygri: Can the thing outlibe the individual who set it up departing the organisation? 15:06:54 HadleyBeeman, the point the Handle/DOI community has made for years is that having "persistent IDs" in the infrastructure is useless if there is no commitment to maintain continuity of access 15:06:55 s/outlibe/outlive/ 15:06:56 1) Can the data outlive the steward. Someone leaves and can their organization be a good steward? 15:07:10 ...and that requires back-end maintenance etc 15:07:16 cygri: Can it outlive the death of DNS? Western civilisation? 15:07:26 2) Can it outlive the DNS and death of Western Civilization as we know it on the Internet? 15:07:56 ... Of course DNS has been stable for some decades, but change happens. 15:08:10 cygri: Individuals leave all the time, but DNS seems pretty stable for now 15:09:37 zen philosophy... zen and the art of rdf maintainence 15:09:38 ... It would be good to include advice on moving top level domains, and there are strategies for handling this. We should provide guidance on this. 15:09:53 ... Mention there are costs associated with URIs. 15:10:04 q? 15:10:08 AnneW: It is about a stability of infrastructure that we're talking about. 15:10:22 annew: it's "stability of infrastructure' we're talking about 15:10:42 annew: I'll take the point about accepting that it's about managing change, not working to avoid it altogether 15:10:46 AnneW: I'll fold in guidance on gracefully handling change ... save the end of Western Civilization or the entire economy changes ... 15:10:49 ack sandro 15:10:55 ...we need to bound conversation (no questions about economy collapsing, etc) 15:11:04 sandro: has said a lot of what I wanted to say 15:11:20 q+ 15:11:28 Sandro: I think this WG needs to be concerned about keeping a given URL working. 15:11:30 sandro: this group needs to be concerned about "keeping that URL working" 15:11:35 +1 sandro 15:11:38 sandro: The idea that some copy of the data survives somewhere is separate. What we need to focus on keeping the URL live 15:12:05 q+ to mention danbri's law 15:12:10 ...Need new second-level domain for any new "project" that needs to persist 15:12:12 sandro: Every time you have a new project, set up a new domain that can be moved from person to person, organisation to organisation without any change 15:12:22 ... everytime I hear this conversation, I think stability will be assured by assigning a new atomic, unique top level domain. I know this is not a consensus position. 15:12:43 ...not a consensus, but to be considered 15:13:05 For example, thing1.org, thing2.org. 15:13:10 ...Domains that can move and have their own "life" 15:13:14 +1 .data 15:13:57 q? 15:14:03 ack bhyland 15:14:19 I want to see if people have strong feelings on purls? 15:14:21 bhyland: want's to here if people have strong opinions on esp PURLs 15:14:45 bhyland: It was news to me that the LoC is using handles/DOIs and not just pruls 15:14:50 s/pruls/purls 15:15:06 AnneW: For FDSys, all the new documents are handles not PURLs. 15:15:21 annew: basically new stuff is being given handles, purls are seen as old system although is maintained 15:15:55 sandro: Speaks against the use of PURLs 15:16:11 sandro: They may be a necessary evil but they add another point of failure 15:16:26 PURLS tradmarked = (Persistent Uniform Resource Locators) http://purl.oclc.org 15:16:29 sandro: If you can't get your own domain name, you have your own problems... 15:16:35 ...Note that Handle System is parallel to DNS, not dependent on it. 15:16:38 i like purls. 15:16:47 i like pearls... 15:16:50 PhilA: Notes that bhyland has a business that sells PURLZ servers 15:17:11 PhilA: There is a difference between PURLs and purl.org 15:17:22 ack GeraldSteeman 15:17:24 90% of Handle System use is through rpoxies, but HDL infrastructure is independent 15:17:36 s/rprox/prox/ 15:17:49 GeraldSteeman: I wanted to agree with sandro on the pre-PURL discussion 15:17:51 s/rpox/prox/ 15:18:11 Government Printing Office GPO http://www.gpo.gov/fdsys/ 15:18:11 GeraldSteeman: If it can live on its own then its value can be passed from one person to another 15:18:29 @PhilA, note, I don't have a business that sells PURLs servers. PURLs is a FLOSS project. I run a company that provides commercial support for a given instance of a production server running PURLs by the US GPO. 15:18:38 GeraldSteeman: The US has an 'official record' and gov officials are bound to submit it to the national archives so that there is an archived version of that info 15:19:10 s/Notes that bhyland has a business that sells PURLZ servers// 15:19:25 It is the difference between a company running a production Apache server for a customer and the Apache Project. We are not the PURLs project, just a user of it :-) 15:19:34 ack cygri 15:19:35 cygri, you wanted to mention danbri's law 15:19:40 danbri's rule: "Rule of thumb - when wondering what info to include in a namespace URI, ... try to leave *out* as much as possible" 15:19:41 The items printed by the GPO, official record, can be accessed through handle technology 15:19:55 cygri: I wanted to say +1 to sandro's point about getting a new domain for a project 15:20:30 Cygri: Danbri's advice is 'leave it out if possible', any thing that can change should be left out if possible. 15:20:44 cygri: schema.org URIs are short, easy to remember and a good example 15:20:47 q+ 15:20:51 q- 15:20:53 ack lunch 15:20:56 q? 15:21:16 Lunch is HUNGRY 15:21:24 -sandro 15:21:34 calendar says 1.5 hours 15:21:40 Thanks all for a great discussion 15:21:49 so— 1 hour? 15:21:55 reconvene at 11:15 and 4:15 15:21:56 What was the question? 15:21:57 thank you annew! 15:21:58 \quit 15:22:01 bye 15:22:06 Zakim, mute galway 15:22:07 galway should now be muted 15:22:25 -t_gheen 15:35:19 -GeraldSteeman 15:42:13 olyerickson has joined #GLD 15:47:16 q+ to suggest a timeline for FPWD 9 Feb and 23 Feb 15:47:18 q? 15:48:40 mhausenblas I lost your G+ audio... 15:53:41 Michael: The latest ED of the BP document is now available via https://dvcs.w3.org/hg/gld/raw-file/a1cb0d2a8fc9/bp/index.html 16:03:39 +sandro 16:06:23 boris has joined #gld 16:10:48 whoa, that was noisy... 16:14:35 Zakim, unmute galway 16:14:35 galway should no longer be muted 16:21:30 Galway's ready 16:21:35 Zakim, who's here? 16:21:35 On the phone I see sandro, galway, olyerickson, Washington, [IPcaller] 16:21:37 galway has galway, fadi, PhilA, dvilasuero, cygri, mhausenblas, GofranShukair, BartvanLeeuwen, csarven, BenediktKaempgen, gatemezin, boris, spyroskotoulas, DeirdreLee 16:21:41 On IRC I see boris, olyerickson, Cory, MacTed, GofranShukair, danbri, DaveReynolds, stasinos, GeraldSteeman, BenediktKaempgen, dvilasuero, mhausenblas, Zakim, fadi, RRSAgent, 16:21:44 ... PhilA, cygri, csarven, BartvanLeeuwen, HadleyBeeman, cgueret_work, rreck, trackbot, sandro 16:21:53 spyroskotoulas has joined #gld 16:22:03 boris_ has joined #gld 16:22:39 +??P1 16:22:49 Zakim, ??P1 is stasinos 16:22:49 +stasinos; got it 16:26:47 DanG has joined #gld 16:26:50 Here's a piece relevant to the discussion earlier about procurement and what the UK Cabinet Office is doing http://www.computerweekly.com/news/2240114381/UK-Governments-prepares-to-open-up-IT-procurement 16:26:54 Mike_Pendleton has joined #gld 16:26:55 +HadleyBeeman 16:27:00 q? 16:28:28 dcat slides: http://www.w3.org/2011/gld/wiki/images/2/28/Dcat-gld-f2f2.pdf 16:29:13 Topic: DCAT 16:29:37 Richard covering DCAT 16:30:03 q- 16:30:09 George has joined #gld 16:30:13 gatemezi has joined #gld 16:30:21 scribe: gatemezi 16:30:27 scribeNickname: gatemezi 16:30:45 cygri: slides are on the wiki... 16:30:59 cygri: http://dvcs.w3.org/hg/gld/raw-file/default/dcat/index.html 16:31:20 ..is not a publicly editor draft 16:31:25 DCAT Editors Draft available 16:31:46 cygri: have dataset, can have distribution... 16:32:00 Editor's draft *is* now public, however, do not take any notice of the URIs for it - this has not been agreed 16:32:04 ....with the different versions of the data (csv, xml,..) 16:32:32 many properties from FOAF 16:32:34 cygri: DCAT has been shapered along withi the eGov . 16:32:55 ..still in the process to move stuff in the W3C domain 16:33:08 connecting use cases and requirements 16:33:14 cygri: collected some requirements... 16:33:16 Cory has left #gld 16:33:19 Cory has joined #gld 16:33:28 cygri: Slide 5, use cases inherited from earlier eGov discussions 16:33:47 ...Q: what to do with these use cases 16:33:55 ...may make sense to separately publish 16:33:55 cygri: what will we do with those requirements? publish them as note? 16:33:55 publish use cases as notes is a possibility 16:34:41 cygri: certainly have things to be added...some works up-to-date this morning 16:34:56 identifed open issues in GLD tracker 16:35:30 bhyland has joined #gld 16:35:31 cygri: Some issues were raised up... 16:35:42 +sandro.a 16:35:49 -sandro 16:35:54 cygri: four people are interested in this work so far 16:35:54 zakim, who is on the call? 16:35:54 On the phone I see stasinos, HadleyBeeman, sandro.a, galway, olyerickson, Washington, [IPcaller] 16:35:57 galway has galway, fadi, PhilA, dvilasuero, cygri, mhausenblas, GofranShukair, BartvanLeeuwen, csarven, BenediktKaempgen, gatemezin, boris, spyroskotoulas, DeirdreLee 16:36:06 Phil, John, Fadi and Richard are woking this issue 16:36:34 cygri: next steps for the following weeks are also described in the last slide 16:36:41 Richard asked for those interesting to join 16:37:00 interested not interesting... 16:37:12 DeirdreLee has joined #gld 16:37:17 FPWD => "First Public Working Draft..." 16:37:24 s/interested/interesting 16:37:43 cygri: work through the tracker issue... 16:37:59 q? 16:38:19 DanG has joined #gld 16:38:34 thanks PhilA 16:38:43 cygri: people aked how does it related to ADMS, etc...? 16:38:50 q+ 16:39:11 cygri: there are of course of alignments but till now not really good answer for that 16:39:42 Michael: The diffs/overview etc. re DCAT, VoiD, etc should be explained via the BP deliverable 16:39:49 ack me 16:39:54 q+ 16:39:55 Richard: how can we ready as many publishers of data catalogs as possible; need outreach 16:40:06 cygri : outreach to publisher should be to take in consideration 16:40:09 q+ to talk about outreach 16:40:19 ack olyerickson 16:40:33 cygri: comments ? questions? 16:41:27 olyerikson: issue in complexity into the draft that we don't necessary need 16:41:40 -sandro 16:41:52 ...we have issue for example about language 16:42:01 Q from olyerickson: draft has no official status, but stable for some time; concern about legacy issues discussed add complexity to process and draft very late that we don't need; we have had little issue with DCAT (other than language); concerned about working issues we don't need to 16:42:28 s/olyerikson/olyerickson 16:42:36 cygri yes, that was my largest point 16:42:42 cygri: we should be aware of existing deployment 16:42:55 q+ to comment on the process 16:42:56 q? 16:43:23 Richard: We need to be aware DCAT is being used and we should be aware of that when considering changes; however, it is a draft and not comfortable with saying we shouldn't change it 16:43:23 ...and yes, the issues were tabled, not actually dealt with 16:43:25 ...it's still a draft, but we need to talk about the issues raised by people 16:43:54 q? 16:44:20 philA: an issue does not need to follow the changes in the draft 16:44:48 ack me 16:44:48 PhilA, you wanted to talk about outreach 16:45:41 philA: we can put the same time org, best practices in the same time. 16:45:53 would like to hear more about CKAN DCAT 'funniness' 16:45:55 PhilA: "CKAN uses DCAT, but in a 'funny way'" 16:45:58 philA: CKAN is a big use case of the use of DCAT. 16:46:51 cygri: need to articulate what we need in other to them to use (CKAN) 16:46:57 Michael: I think we can summarise this - we (DERI) can take care of CKAN/OKF liaison as we work together on project basis (LATC, LOD2) 16:48:03 q+ to comment on reach out 16:48:20 @mhausenblas, thank you. This is really important. Can you update the GLD WG on whatever frequency makes sense as we're really interested outreach to OKF. 16:48:33 PROPOSAL: Richard C acts as liaison point for OKF/CKAN 16:48:46 +1 16:48:46 q+ 16:48:57 philA: if DCAT is not attractive to CKAN, there may be a problem somewheere 16:49:05 q? 16:49:14 ack mhausenblas 16:49:14 mhausenblas, you wanted to comment on the process 16:49:15 Happy to help, Cygri, if you need someone to chat to them on the ground in London. 16:49:23 (though it sounds like you have it all in hand) 16:49:32 +sandro 16:49:34 thanks HadleyBeeman - prob take you up on that 16:49:37 CKAN "funny" use of DCAT doesn't mean DCAT is 'wrong' any more than RPI use of DCAT means it's right ;) 16:49:43 mhausenblas: goal to get out working draft; define processes 16:49:50 HadleyBeeman, it will be good if they hear about dcat from multiple directions 16:50:07 +1 mhausenblas 16:50:30 PROPOSAL: Richard C acts as liaison point for OKF/CKAN regarding DCAT 16:50:33 +1 16:50:42 +1 16:50:45 mhausenblas: propose cygri to be the liaison to CKAN 16:50:46 +1 16:50:47 +1 16:50:51 +1 to mhausenblas proposal 16:51:01 ( I don't think we need a WG resolution on this kind of thing. :-) 16:51:04 +1 16:51:05 you're welcome :-D 16:51:09 +1 16:51:14 Hadley will support Richard 16:51:15 Noted: Hadley also in a good position to liaise with OKF re: DCAT 16:51:33 Do we need a proposal w.r.t. specific work on issues? 16:51:47 q? 16:51:47 q? 16:51:52 ack fadi 16:51:52 fadi, you wanted to comment on reach out 16:52:09 RESOLUTION: Richard C acts as liaison point for OKF/CKAN regarding DCAT 16:52:22 fadi: CKAN uses DCAT in two services 16:53:04 ... need a proper and clear statement of DCAT 16:53:06 ack DeirdreLee 16:53:41 Repeat the question? 16:53:45 q? 16:54:04 George: Next step questions posed - do we want to work on them? 16:54:11 george: do we discuss the next steps now? 16:54:27 The question was about non-CKAN usage of DCAT and what we could learn from that. Fadi noted that a number of Spanish catalogues use DCAT but all do it differently 16:55:13 http://www.w3.org/egov/wiki/Data_Catalog_Vocabulary/Use_Cases_and_Requirements 16:55:28 cygri: For the requirements, they have text for that, it is just to pass them to WG 16:55:36 +1 to turn the UC into a WG Note, that is non-REC-Track 16:56:12 +1 to mhausenblas 16:56:15 Wondering specifically what spanish catalogs Fadi is referring to. We haven't seen (much if any) dcat use in the wild 16:56:18 cygri: Arguing that publishing the UCs as a draft WG Note helps to attract more review and interest 16:56:27 ...is fadi referring to CTIC? 16:56:35 Bernadette: Process for note? 16:56:52 W3C process for Working Note vs just having a more mutable wiki page. 16:57:03 Yigal has joined #gld 16:57:06 olyerickson: catalonia http://www20.gencat.cat/portal/site/dadesobertes 16:57:12 q+ to talk about WG Notes 16:57:17 philA: need a resolution for DCAT use case.. 16:57:47 olyerickson - catalonia, barcelona, gijon and balearic islands use it in their local catalogs 16:58:13 Per PhilA, it is a shorter process than Recommendation. Circulate email to TLR, chairs with intension to publish Working Notes with some descriptive context as to why we're we doing this. 16:59:01 ... Working Notes that supports Recommendation and carries slightly more heft than the wiki page. 16:59:14 RRSAgent, pointer? 16:59:14 See http://www.w3.org/2012/01/26-gld-irc#T16-59-14 16:59:56 Michael: http://www.w3.org/2005/10/Process-20051014/tr.html#q75 17:01:33 to me "resolution" == "decision" == "written record of an agreement" 17:01:48 +1 @sandro 17:01:50 trackbot has joined #gld 17:01:57 -1 to tracker issues now 17:02:08 trackbot, how the heck are you? 17:02:21 PROPOSED RESOLUTION: That the DCAT Use Cases be formatted as a draft WG Note and that the chairs seek permission to publish at /TR/dcat-use-cases 17:02:32 George has joined #gld 17:02:59 @philA: thanks! 17:03:02 +1 to The DCAT Group having separate call to thrash through, preceded by email discussion 17:03:14 I think there needs to be a general discussion before some group goes off by itself to look at an issue 17:03:15 How do we want to address tracker issues? Can we use thursday call or separate call 17:03:16 q+ 17:03:19 q? 17:03:20 +1 to separate call 17:03:28 Sorry, sandro, I don't understand 'trackbot, how the heck are you?'. Please refer to http://www.w3.org/2005/06/tracker/irc for help 17:03:30 +1 to mostly emails, with separate call at the end 17:03:43 +1 to The DCAT Group reporting back to larger group 17:03:56 q+ to make a proposal regarding what we talk about today cf. other occasions 17:03:59 ack me 17:03:59 mhausenblas, you wanted to talk about WG Notes 17:04:02 +1 to more content on the weekly calls. 17:04:28 Bernadette recommends working on specific issues on our regular weekly calls 17:04:32 q? 17:05:07 bhyland: should there be a specific telecon for DCAT group? 17:05:13 annew has joined #gld 17:05:16 ack me 17:05:25 q? 17:05:28 q+ 17:05:35 ack olyerickson 17:05:40 ack me 17:05:40 PhilA, you wanted to make a proposal regarding what we talk about today cf. other occasions 17:05:44 arrggghh 17:05:50 Zakim, who is here? 17:05:50 On the phone I see stasinos, HadleyBeeman, sandro, galway, olyerickson, Washington, [IPcaller] 17:05:53 galway has galway, fadi, PhilA, dvilasuero, cygri, mhausenblas, GofranShukair, BartvanLeeuwen, csarven, BenediktKaempgen, gatemezin, boris, spyroskotoulas, DeirdreLee 17:05:56 On IRC I see annew, George, trackbot, Yigal, DanG, DeirdreLee, bhyland, Cory, gatemezi, Mike_Pendleton, boris, spyroskotoulas, olyerickson, MacTed, GofranShukair, danbri, 17:05:59 ... DaveReynolds, stasinos, GeraldSteeman, BenediktKaempgen, dvilasuero, mhausenblas, Zakim, fadi, RRSAgent, PhilA, cygri, csarven, BartvanLeeuwen, HadleyBeeman, cgueret_work, 17:06:00 https://www.w3.org/2011/gld/track/issues/raised 17:06:02 ... rreck, sandro 17:06:06 Cygri: If others think it is a good use of our weekly telecons to dig deeper into DCAT to help streamline it moving forward, please indicate your interest. 17:06:12 +1 by bhyland 17:06:48 PhilA: looking at the well catalogued issues, some are detailed about individual properties, and thos should be handled among interested folks on a separate call; others are of broader interest 17:06:51 q+ to talk to fragmentation vs. efficiency 17:07:33 phila: is referring to the "distribution" stuff 17:07:40 PhilA: mechanism for what is in a zip; like CKAN has 17:07:50 q? 17:07:55 q? 17:08:10 q? 17:08:51 q+ Secret incantation to hop the queue ;-) 17:09:10 q+ to suggest (re dates) we *not* merge data with comments on the data, in the same field 17:09:20 are boiled frogs legs necessary to jump the queue? 17:09:46 olyerickson: there are some issues to be talked by emails and after if necessary others in the regular call 17:09:47 olyerickson: if there are high level issues which should be discussed today or on reg. call; other low level issues on email/breakout call; leave it to chairs/rest of group 17:09:48 i think that's consistent with PhilA 's suggestion 17:09:54 ack me 17:09:54 mhausenblas, you wanted to talk to fragmentation vs. efficiency 17:10:04 @Mike_Pendleton: thanks 17:10:40 @ gatemezi: it takes a village 17:10:52 q? 17:10:57 mhausenblas: how details of the discussion do we like ? Efficiency arises when the small group meets together 17:11:46 ack sandro 17:11:46 sandro, you wanted to suggest (re dates) we *not* merge data with comments on the data, in the same field 17:11:51 Sandro: date question - approach of having typed value if known or string if you don't know the date 17:12:09 q+ 17:12:38 IMO better to make it easier for the publisher than for tool builders (writing code around stuff) 17:12:43 sandro is concerned about best way to handle "uncertainty" around dates 17:13:03 Sandro: Handling uncertainty is dates - labeling and annotation 17:13:07 ...clear what to do when it's known e.g. xsd: date but what to do when NOT known 17:13:09 sandro: is there any research going on in handling uncertainty? 17:13:43 DaveReynolds has left #gld 17:13:44 philA: in half the time publishers don't type very well the data 17:13:49 *nod* this is about whether the burden goes on the publisher or consumer.... 17:14:02 Q+ 17:14:33 PhilA: half the time data publishers use the wrong date type - better to use two versions 17:14:46 ack stasinos 17:14:47 George: Make it easier on the publisher 17:15:09 http://placetime.com/ 17:15:19 q? 17:15:20 +1 @george being TOO specific e.g. with dateTime or gYear tec can b a problem 17:15:28 Zakim, allow cygri 30s 17:15:28 I don't understand 'allow cygri 30s', mhausenblas 17:15:53 Zakim, allow cygri 30 s 17:15:53 I don't understand 'allow cygri 30 s', mhausenblas 17:16:24 Zakim, allow cygri 30 sec 17:16:24 I don't understand 'allow cygri 30 sec', mhausenblas 17:16:32 ack cygri 17:17:25 cygri: if you have 2 properties, you have to write how to use them, no complexity in term of coding 17:17:26 q+ to suggest a third way that I don't like but recognise it's a possibility 17:18:24 cygri: DCAT takes existing metadata of data and expose them in RDF 17:18:26 allow 30 sec 17:18:43 q? 17:18:45 cygri: Purpose of DCAT is to take existing databases of metadata and exposing them as RDF. Anything that requires recoding of dates is COMPLETELY out of the question for cygri. 17:19:04 ... quantfy uncertainty is too difficult. 17:19:17 s/quantfy/quantify 17:19:20 +1 to cygri being persuasive ;) 17:19:29 q+ 17:19:42 Sandro: Is persuaded by cygri's argument. 17:20:04 The use case of legacy dates MUST NOT be ignored 17:20:22 ack me 17:20:22 PhilA, you wanted to suggest a third way that I don't like but recognise it's a possibility 17:20:32 q+ 17:20:35 q+ 17:20:38 q? 17:21:22 Discussed: Data accurary using XSD Date which is the most ubiquitous date format 17:21:43 That's up to the consumer 17:21:58 s/accurary/accuracy 17:22:13 bhyland: chair interrupt 17:22:47 Bernadette: Gov't orgs have to accept whatever; they accept data that sometimes they can't clean up. 17:23:00 q? 17:23:07 (but: unclean data in - unclean data out) 17:23:30 bhyland that's the point, we're talking about a string-bucket as a roll-over 17:23:41 Discussion is about how do we handle and not fall over with systems give us ill-behaved/ill-formatted data. 17:24:13 ... Is our recommendation 'leave it as a string' or data type it if we DO know it is a date. 17:24:15 +1 to xsd: date preferred, string literal otherwise 17:24:21 +1 17:24:25 +1 17:24:26 +1 17:24:26 ;) 17:24:32 ack stasinos 17:24:34 +1 17:24:34 q- 17:24:36 ack me 17:24:41 sandro: if you know the date, use xsd:data; if not use it as string 17:24:45 +1 (untll some folks come with a compelling rdfs:range use case) 17:25:42 q? 17:26:18 A literal doesn't necessarily imply anything more than what it really is (unless further context is give). The interpretation is up to the consumer. 2012-01-26 (would be on that day, or the whole day, and not necessarily on the midnight of that day). 17:26:22 Mike_Pendleton has joined #gld 17:26:28 q+ to propose close queue 17:26:31 stasinos: propose not to allow string 17:26:54 q? 17:26:57 Stasinos recommends looking closely at PlaceTime.com - URIs for Places and Times. PlaceTime.com is intended to be a URI space containing URIs that represent places and times. 17:27:05 stasinos proposed to not allow *unstructured* strings 17:27:13 philA: it is difficult to ask providers to reformate their data 17:27:27 q? 17:27:28 q? 17:27:37 ack me 17:27:37 mhausenblas, you wanted to propose close queue 17:28:28 Mhausenblas: are there other things we want to cover? 17:28:37 mhausenblas: do we have another important issue to discuss? 17:29:12 +1 to shaken, not stirred 17:29:23 +1 to it being 5 O'Oclock Somewhere 17:29:34 -[IPcaller] 17:29:43 Zakim, what would Jimmy Buffett do? 17:29:43 I don't understand your question, olyerickson. 17:29:57 q? 17:30:33 q+ on usage advises on external vocabs 17:30:40 q+ 17:30:46 q+ 17:30:48 q? 17:30:51 q+ to mention third (OWL) option 17:30:53 philA: how do we use DCterms issued? 17:31:04 q+ 17:31:16 PhilA: Issue 2 :-) In definition of DCAT, cube data, etc, we will be saying 'use this term' and this is how we want them to use it; is it right to make range statements about others terms? 17:31:20 Michael: I'd prefer a soft advise as we did in VoID such as in http://www.w3.org/TR/void/#dublin-core 17:31:50 trackbot has joined #gld 17:31:53 +1 to "anyone can say anything about anything" http://bit.ly/yZvdpk (RDF def'n) 17:31:56 q? 17:32:19 +q 17:32:24 ack mhausenblas 17:32:24 mhausenblas, you wanted to comment on usage advises on external vocabs 17:33:02 ack stasinos 17:33:07 +1 mhausenblas 17:33:13 q- 17:33:16 +1 usage notes michael 17:34:29 +1 to the AAA slogan 17:35:18 @olyrickson: is not "anyone can say anything about any topic" ? :-) 17:35:32 ack DanG 17:36:22 @gatemezi I'd like to understand why not. The way it is being presented, it sounds like that to me; this is why I'd like some examples 17:36:23 olyerickson: There's a specific case cited in the issue http://www.w3.org/2011/gld/track/issues/4 17:37:31 ack cygri 17:37:31 cygri, you wanted to mention third (OWL) option 17:37:33 q+ 17:37:40 DanG: in standards community; conformity is the notion, not compliance, and extends to a technical spec. For example, US Open Govt vocab working group; as long as vocab conforms to the spec., all is good; takes us out of the business of telling people what and how in particular circumstances 17:38:02 Thanks @PhilA, I think I get it. Problem being discussed is, cases where a 3rd party term is used but with an added restriction 17:38:32 @Mike_Pendleton: thanks!! it is sometimes difficult to scribe alone :-) 17:38:53 ...ie "we use foo: xyz BUT only with range xsd: fooBar " 17:39:24 q- 17:39:52 I think my statement is consistent with what Richard is saying. 17:40:28 cygri: actually OWL is powerful to make explicit context about datasets, or DCAT 17:40:46 trackbot has joined #gld 17:40:48 I like what cygri is saying about using OWL - that sounds like a solution to me (along with a textual note) 17:41:01 q? 17:41:01 q 17:41:04 q+ 17:41:08 ack DeirdreLee 17:41:16 OWL might be overkill for this particular use case 17:41:54 DeirdreLee: saying in prose in open to interpretation, formalise it is better; agrees with cygri 17:41:57 q? 17:41:59 deirdreLee: DCAT usage is open to interpretation 17:42:09 ack stasinos 17:42:31 there's a difference between conflicts due to errors and conflicts due to people redefining other people's stuff 17:42:44 q+ 17:43:16 yes - defining a subproperty is always possible and avoids the problem 17:44:05 +1 to defining a subproperty 17:44:10 ack me 17:44:27 +1 to backward-chaining -1 to tableaux 17:44:49 yes - defining a subproperty means inventing a new property. 17:45:53 philA: Ok for the defining a subproperty; but problems come when using a reasoner using inferencing 17:46:17 philA: using owl is the wright thing 17:46:22 PhilA: stasinos idea is the most accurate solution; however Richard pointed out that most linked data systems don't involve reasoners, so it doesn't matter 17:46:29 q? 17:46:43 Can someone please explain why dcat's use of dc dates is not an example? 17:46:48 Zakim, who is here? 17:46:48 On the phone I see stasinos, HadleyBeeman, sandro, galway, olyerickson, Washington 17:46:50 galway has galway, fadi, PhilA, dvilasuero, cygri, mhausenblas, GofranShukair, BartvanLeeuwen, csarven, BenediktKaempgen, gatemezin, boris, spyroskotoulas, DeirdreLee 17:46:54 On IRC I see trackbot, Mike_Pendleton, annew, George, Yigal, DanG, DeirdreLee, Cory, gatemezi, boris, spyroskotoulas, olyerickson, MacTed, GofranShukair, danbri, stasinos, 17:46:58 ... GeraldSteeman, BenediktKaempgen, dvilasuero, mhausenblas, Zakim, fadi, RRSAgent, PhilA, cygri, csarven, BartvanLeeuwen, HadleyBeeman, cgueret_work, rreck, sandro 17:46:58 dc doesn't say anything about xsd: date 17:47:13 q? 17:47:40 cmusialek has joined #gld 17:48:05 Possible Ways forward: 1) define the sub domain and range as we see fit and don't care 2) only define domain and raneg in a usage note specific to DCAT etc, 3) define ranges in OWL 17:48:10 @cygri: do we have a link of the slides? 17:48:22 gatemezi, which slides? 17:48:23 slide 8: http://www.w3.org/2011/gld/wiki/images/2/28/Dcat-gld-f2f2.pdf 17:48:32 ah ok 17:48:55 @benediktKaempgen: thanks 17:49:10 bhyland has joined #gld 17:49:13 option 4) define subproperties and subclasses 17:49:53 +1 for option 4) 17:50:12 PhilA: By "Combination of 2 & 3" do you mean prose + RDFS, or RDFS + OWL, or??? 17:50:37 option 5) it depends. 17:50:41 olyerickson: I mean use OWL and text, not RDFs 17:50:45 6) all of the above 17:50:53 Can we have a vote after we have a short break? and a clarification of the question 17:50:56 7) do nothing 17:50:57 PhilA ah okay 17:50:57 7) none of the above? 17:51:11 8) go for dinner 17:51:20 me notes it's waaay after 5p in Galway ;) 17:51:21 s/dinner/beer 17:51:30 yeah, like 51min 17:51:33 s/dinner/martini 17:51:53 1) define the sub domain and range as we see fit and don't care 17:52:11 -0.8 17:52:13 -1 17:52:18 +0.2 17:52:19 -1 17:52:27 rreck +1 1 17:52:29 +0.3 17:52:30 +.03 17:52:30 abstain 17:52:38 Who is "we" (I'm serioues) 17:52:41 + 1E-1 17:52:45 nil 17:53:14 Anne will give promises of preservation and stability to whoever buys drinks 17:53:18 No we're not 17:53:27 Trying to understand who "we" is 17:53:34 Will someone please write down a succinct atement of the question? 17:53:42 +1 dang 17:53:45 2) only define domain and raneg in a usage note specific to DCAT etc 17:53:50 +1 17:53:51 s/atement/statement 17:54:01 s/atement/statement 17:54:10 s/atement/drinkment/ 17:54:17 abstain 17:54:21 this was 3 before, wasnt it? 17:54:22 +0.8 17:54:42 DanG: When publishing the machine readable version of a vocabulary, how should we indicate that in the context of that vocabulary, terms from other namespace should be used in a way that is more restrictive than is defined in the original definition 17:54:49 -1 17:54:52 -1 (then we do not need to call it domain/range) 17:55:04 -1 17:55:04 0.2 17:55:10 +1 17:55:12 +1 17:55:15 3) define ranges in OWL 17:55:19 -1 17:55:22 WHO IS "WE"???????? 17:55:24 +0.5 17:55:27 +1 17:55:28 --0 17:55:28 -1 17:55:29 -1 17:55:37 +0.5 17:55:48 q? 17:56:14 Michael: On a serious note - can we delegate this to the DCAT TF - this doesn't make sense to me at all 17:57:02 17:57:14 philA: WE=vGLD group 17:57:14 Thanks! Sorry for exploding 17:57:17 q+ 17:57:21 +1 mhausenblas. we've collected the options and heard some opinions and arguments, that's perhaps as good as we can do here. 17:57:33 s/vGLD/GLD 17:57:57 here comes (8) again: do nothing 17:58:00 +1 to bhyland and mhausenblas 17:58:19 +1 break 17:58:21 q? 17:58:23 Let's package it up as a proposal in email and thrash it there 17:58:28 +1 for break 17:58:35 +1 break if we close the "debate" 17:59:00 q- 17:59:01 bhyland: break 10 minutes 17:59:02 okay. 17:59:02 -galway 17:59:04 -sandro 17:59:10 -HadleyBeeman 17:59:20 -stasinos 18:03:56 wondering what galway is looking at (curious) 18:04:16 SimpsonTP_ has joined #gld 18:05:07 csarven1 has joined #gld 18:06:00 mhausenblas_ has joined #gld 18:06:02 cygri_ has joined #gld 18:06:41 hey Galway, unmute 18:11:38 galway coming back 18:11:45 +galway 18:12:14 q+ to update people about BP 18:12:20 q+ to suggest a timeline for FPWD 9 Feb and 23 Feb 18:12:36 Topic: Review of all outstanding Documents that the WG is updating 18:13:35 Zakim, who's here? 18:13:35 On the phone I see galway, olyerickson, Washington 18:13:36 On IRC I see cygri, mhausenblas, csarven1, SimpsonTP_, bhyland, cmusialek, trackbot, Mike_Pendleton, George, DanG, DeirdreLee, Cory, boris, spyroskotoulas, olyerickson, MacTed, 18:13:41 ... GofranShukair, danbri, stasinos, GeraldSteeman, BenediktKaempgen, dvilasuero, Zakim, fadi, RRSAgent, PhilA, HadleyBeeman, cgueret_work, rreck, sandro 18:13:47 gatemezi has joined #gld 18:14:05 Zakim, who is here? 18:14:05 On the phone I see galway, olyerickson, Washington 18:14:06 On IRC I see gatemezi, cygri, mhausenblas, csarven1, SimpsonTP_, bhyland, cmusialek, trackbot, Mike_Pendleton, George, DanG, DeirdreLee, Cory, boris, spyroskotoulas, olyerickson, 18:14:11 ... MacTed, GofranShukair, danbri, stasinos, GeraldSteeman, BenediktKaempgen, dvilasuero, Zakim, fadi, RRSAgent, PhilA, HadleyBeeman, cgueret_work, rreck, sandro 18:15:01 Zakim, who are the Cool Kids handing out on G+? 18:15:01 I don't understand your question, olyerickson. 18:15:40 q? 18:15:43 scribe: fadi 18:16:16 +HadleyBeeman 18:16:20 bhyland: let's review outstanding documents we are updating 18:16:56 Bernadette: How to keep momentum and make progress on a montly basis 18:17:05 ... we need to keep the great momentum we have 18:17:43 ... what's our strategy for the upcoming tele-calls? 18:17:59 DanG has left #gld 18:18:09 Michael: Can we first agree on FPWD please? And then have the meta-discussion? 18:18:33 ... we already have consumers involved 18:18:51 DanG has joined #gld 18:18:56 ... how to keep the moentum then, suggestions/comments? 18:19:10 s/moentum/momentum/ 18:19:12 q? 18:19:15 Topic: FPWD Best Practices timing 18:19:23 ack me 18:19:23 mhausenblas, you wanted to update people about BP and to suggest a timeline for FPWD 9 Feb and 23 Feb 18:19:43 See https://dvcs.w3.org/hg/gld/raw-file/default/bp/index.html 18:19:58 mhausenblas: we had a quick session in the moorninng updating an editor draft 18:19:59 can one of the google plus kids invite me again? 18:20:20 ... feel free to raise issues and provide feedback 18:20:30 PROPOSAL: The GLD WG decides to publish BP, DCAT, QB and ORG as FPWD on the REC-Track by end of Feb 2012 with 9 Feb ready for WG review and final decision to be taken on 23 Feb. 18:21:14 +sandro 18:21:44 PhilA: do we need the two weeks between 9 and 23? 18:22:26 mhausenblas: probably yes... based on experience, people need this time to review 18:22:34 ... talking about WG members 18:22:37 +1 to proposal timing and 1 week review cycle. IF needed, we can extend, but better to put a fire under people's bum 18:23:12 q? 18:23:36 Michael: I suggested 2 weeks review cycle, bhyland, just to clarify 18:23:53 bhyland: we are all here, so we can make a decision 18:24:30 ... anyone has particular input to people here who are working on the best practice? 18:24:45 PROPOSAL: The GLD WG decides to publish BP, DCAT, QB and ORG as FPWD on the REC-Track 18:25:23 q+ 18:25:26 q+ To just check we want the vocabs on the Rec Track 18:25:31 mhausenblas: any other document should go the REC-track? 18:26:13 bhyland: this looks a lot giving that some people expressed that they are busy currently 18:26:14 bhyland yes DaveReynolds was either working QB or ORG 18:26:17 ack cygri 18:26:54 Yes -- it's okay to have placeholders for sections of the document. 18:26:55 cygri: is it acceptable for the FWPD to have big gaps like entire section not written yet? 18:27:12 mhausenblas: yes 18:27:18 DaveReynolds is key person on ORG. What is being proposed is that 4 documents as FPWD. 18:27:24 the key thing to to give people an idea which way we are heading, and give them something interesting to review. 18:27:44 cygri: standard vocabulary doesn't seem covered in the list 18:28:27 right, People Vocab is missing. 18:28:28 ... referring particularly to the "people" 18:28:37 Mike_Pendleton has joined #gld 18:28:37 ... mentioned in the charter 18:29:09 PhilA: as part of the core vocabulary work we are working on a "person" vocabulary 18:29:32 ... there will be soon a version available in the public domain 18:29:48 ... this might be used as basis for representing people 18:29:56 ... not going with FWPD 18:30:16 ... but just pointing that we tackled the "people" representation topic 18:30:37 PROPOSAL: The GLD WG decides to publish BP, DCAT, QB and ORG as FPWD on the REC-Track, while people area will be addressed later (based on ISI draft) 18:31:19 ... the ISA person vocabulary can be, when available, a candidate 18:31:25 PROPOSAL: The GLD WG decides to publish BP, DCAT, QB and ORG as FPWD on the REC-Track, while people area will be addressed later (based on ISA draft) 18:31:32 PhilA: Hoping that people in this WG would consider as a candidate for endorsement the ISA Person Core Vocbulary .. 18:31:34 PROPOSAL: The GLD WG decides to publish BP, DCAT, QB and ORG as FPWD on the REC-Track, while people area will be addressed later (based on ISA-core draft) 18:31:36 ... for the WG to consider 18:31:37 ack me 18:31:37 PhilA, you wanted to just check we want the vocabs on the Rec Track 18:32:17 PhilA: to get to REC you have to prove it is being used correctly 18:32:20 PhilA: Part of being a Recommendation, is a reference implementation to provide it is being used, and used correctly. 18:32:22 q+ 18:32:23 PhilA: by publishing vocabulary on the REC-Track, it needs to be proved that the vocabulary is used 18:32:33 ack me 18:32:38 Link to ISA Core Person Vocabulary http://joinup.ec.europa.eu/asset/core_person/description 18:32:42 q+ to say that the charter says the vocabs will go REC 18:32:44 ... and is used in a correct manner... a note doesn't have this restriction 18:32:53 mhausenblas: with dcat for example we can prove it 18:32:57 mhausenblas: DCAT, Cube and ORG are all used and we can prove it. 18:33:02 q+ on implementation reports 18:33:03 Proof comes from signature logs, etc 18:33:09 ... using mailing lists, Sindice log, answer.semantic.org 18:33:21 Link to all ISA Core Vocabularies (reference) https://joinup.ec.europa.eu/software/isa-cv/description 18:33:30 PhilA: you need to prove that people use *all* of it 18:33:31 This is sounding like a significant bit of research. 18:33:56 q? 18:34:01 q+ 18:34:07 ... every element of the specification has been implemented more than once in a right manner 18:34:28 cygri: the charter said that the vocabularies will be on the REC-track 18:34:33 ack cygri 18:34:33 cygri, you wanted to say that the charter says the vocabs will go REC 18:34:43 ... looking at SKOS is helpful 18:34:47 q? 18:34:53 q- 18:35:03 ack bhyland 18:35:19 bhyland: We are not in the business of writing vocabs; we do checklists and specify what is used 18:35:33 Michael: I disagree. We do do vocabs 18:35:44 ... see sec 2.3 18:35:47 bhyland: with BP, the focus is on providing checklist help people choose vocabularies, etc... 18:36:01 ... Core vocabularies sounds out of the charter 18:36:01 q? 18:36:20 ... yesterday decision was not to give a particular recommendation on a vocabulary 18:36:41 PROPOSAL: The GLD WG decides to publish BP, DCAT, QB and ORG as FPWD on the REC-Track, while people area will be addressed later (based on ISA-core draft) 18:36:46 ... except for items that are explicitly mentioned in the charter 18:36:53 ... which includes people 18:37:02 rreck1 has joined #gld 18:37:33 PROPOSAL: The GLD WG decides to publish BP, DCAT, QB and ORG as FPWD on the REC-Track, while people area will be addressed later 18:37:41 cygri: it is early to decide/vote on the ISA core draft as we are fully aware of it 18:37:44 Cygri: couldn't be supportive of ISA Core Core vocab until we've had a chance to review it. 18:37:45 +1 18:37:46 + VCard? 18:37:47 +1 cygri 18:38:05 +1 18:38:07 +1 18:38:22 +1 18:38:24 +1 18:38:26 +1 18:38:32 +1 18:38:37 + 1 18:38:48 +1 18:38:49 +1 18:38:54 PROPOSAL: The GLD WG decides to publish the first batch of FPWD by end of Feb 2012 with 9 Feb ready for WG review and final decision to be taken on 23 Feb. 18:39:48 mhausenblas: the proposal gives two weeks for the members to comment 18:40:02 + where is my brain 18:40:14 PROPOSAL: The GLD WG decides to publish the first batch of FPWD by end of Feb 2012 with 9 Feb ready for WG review and final decision to be taken on 23 Feb. 18:40:27 +1 18:40:29 predictable 18:40:41 +1 18:40:43 +1 18:40:45 +1 18:40:45 +1 18:40:48 +1 18:40:51 +1 18:41:07 Well that was my question 18:41:46 RESOLUTION: The GLD WG decides to publish BP, DCAT, QB and ORG as FPWD on the REC-Track, while people area will be addressed later 18:41:57 RESOLUTION: The GLD WG decides to publish the first batch of FPWD by end of Feb 2012 with 9 Feb ready for WG review and final decision to be taken on 23 Feb. 18:42:06 PhilA: I will work on putting both dcat and ORG into respec 18:42:25 PhilA: it is a mechanical job 18:42:25 I'm +1 to DCAT (I think very little other than what PhilA is talking about) 18:43:01 mhausenblas: the two weeks comment period gives us a back-up 18:43:05 q+ to ask about volunteers for html churning 18:43:08 q? 18:43:11 I'm frankly unclear what additional work reqd for section changes to BP 18:43:12 ... in case the deadline of Feb 9 is not met 18:43:22 rreck_again has joined #gld 18:44:24 bhyland: a glossary is missed from the charter 18:44:37 ... this should be section 1.10 18:44:57 q+ on what is required for the BP 18:45:03 olyerickson: re. provenance I started working on the respected section 18:45:21 Michael: I suggest to keep it simple for the FPWD - our charter doesn't require provenance 18:45:25 q? 18:45:29 ... so far it is not clear what the requirements are 18:45:59 bhyland: I will work on the provenance section in the cook book 18:46:18 +1 to keeping what we have so far 18:46:20 mhausenblas: this doesn't look a requirement in the chapter 18:46:26 s/chapter/charter/ 18:46:37 Michael: it isn't a requirement ;) 18:46:42 mhausenblas: may be we'd better focus on the "must do" parts 18:46:43 bhyland that is NOT provenance 18:46:52 bhyland: I already have some contents ready 18:46:53 t_gheen has joined #gld 18:47:24 olyerickson: provenance need more discussion later 18:47:42 q? 18:47:49 ack me 18:47:49 cygri, you wanted to ask about volunteers for html churning 18:47:50 I'm more concerned about narrowing URI construction 18:47:55 ack me 18:47:55 mhausenblas, you wanted to comment on what is required for the BP 18:48:20 +1 to cygri 18:48:28 +1 to cygri 18:48:34 cygri: it would be great if someone is willing to help with the editorial work 18:48:59 cmusialek has joined #gld 18:50:09 + +1.703.201.aaaa 18:50:35 q+ to talk about why VCard is getting no GLD love 18:50:46 Bernadette: Any issues yet to be raised? 18:50:51 Zakim, aaaa is me 18:50:51 +t_gheen; got it 18:50:55 +q validation 18:51:21 mhausenblas: shall we have a meta-discussion? re. organizing, time management, etc. 18:51:22 oops imean the topic 18:51:30 q+ to talk about the non-Editor's role in the process 18:51:47 bhyland: now that we have the deadline set to Feb 9, we've got the motivation/target to work for 18:52:02 q? 18:52:14 q- validation 18:52:25 +1 to bernadette 18:52:35 q? 18:52:38 q+ to talk about future events that might provide opportunity for f2f meetings 18:52:41 +1 to bernadette and mhausenblas's points on big bang publishing approach 18:52:50 ack George 18:52:50 George, you wanted to talk about why VCard is getting no GLD love 18:52:51 ack George 18:53:09 George: Pulse check on VCARD 18:53:15 bhyland has joined #gld 18:53:17 George: what people think of vcard? 18:53:30 George: ORG seems to work with it pretty well 18:53:36 q? 18:53:39 ack me 18:53:39 mhausenblas, you wanted to talk about the non-Editor's role in the process 18:53:41 ... I'm curious to know about people's opinion about using it for represnting people 18:53:53 rreck_again has joined #gld 18:54:05 q? 18:54:08 +q 18:54:13 mhausenblas: need folks to review 18:54:13 mhausenblas: people who are not editors would help in reviewing the drafts 18:54:13 q+ 18:54:20 q- 18:54:23 ... they have an equivalent important role 18:54:30 http://www.w3.org/TR/vcard-rdf/ 18:54:34 s/represnting/representing 18:54:54 +[IPcaller] 18:54:55 ... re VCard 18:55:07 ... there are a lot of options currently 18:55:10 Zakim, [IPcaller] is stasinos 18:55:10 +stasinos; got it 18:55:23 ... FOAF, VCard, the ISA vocab, etc. 18:55:32 ... further research is needed to decide 18:55:41 mhausenblas: vCard needs a bit of research before we give de facto blessing ... if it is vCard, ok, but it deserves review in light of alternatives. 18:55:49 q? 18:56:13 PhilA: my opinion is that VCard looks very American-specific 18:56:14 Is this a vcard vs ISA Person discussion? 18:56:14 +1 to philA: vCard is difficult when you're in the UK (or outside the USA) 18:56:32 ... but it is hard to define a vocabulary that fit everybody 18:56:33 PhilA: vCard format is alien to many (except Americans) 18:56:33 s/difficult/awkward 18:56:50 HadleyBeeman what does the 'rest of the world" use? 18:57:01 PhilA: No one format will work for everyone 18:57:16 I'm Amercan and find vCard overly simplified. 18:57:28 olyerickson we've been talking about that this week at LinkedGov. We're shoe-horning stuff into vCard— but it is awkward. And hard to explain to non-techie users. 18:57:37 George: thought it was an easy win; this is the pulse check we are looking for 18:57:54 HadleyBeeman has e.g. hcard come up? 18:58:12 Michael: In fact, as I 've been doing some work already in this area I'd volunteer to contribute to the 'people area' once we have the FPWD of BP out of the door 18:58:29 q? 18:58:40 1? 18:58:40 PhilA: VCard is still one of the best available options 18:58:47 q? 18:58:48 ack rreck_again 18:58:53 +1 to PhilA: implementation > convenience 18:58:57 olyerickson: yeah, it has. (I can't remember right now what the problem was there, to be honest) I think we'll end up using vCard but relabelling the fields for UK-based users (for input only). 18:59:01 q+ to talk about people vocab contribution 18:59:25 rreck_again: valid RDF is important and woth being added to the check list 18:59:38 q+ to answer on validation and bnodes 18:59:44 s/VCard is still one of the best available options/VCard is still one of the most readily available options and is no worse than any of the others/ 18:59:46 HadleyBeeman hCard discussed here http://microformats.org/wiki/hcard could be lack of official status 18:59:48 ... re. blank nodes 18:59:53 rreck: two topics: 1. When I get RDF, it doesn't always validate against 'X'; 2. Anonymous nodes - tell govt's not to use B nodes 19:00:05 ... I'd suggest to governments not using it 19:00:13 I like bnodes when they are right for what I am doing! 19:00:20 genid uris 19:00:22 bhyland: more suitable point for the RDF WG 19:00:33 ... suggest replacing B nodes with URIs 19:00:38 cygri: Commented on decissions / discussions within RDF WG for RDF 1.1 19:00:44 http://dvcs.w3.org/hg/rdf/raw-file/default/rdf-concepts/index.html#section-skolemization 19:00:55 Who is talking? 19:01:05 cygri: in RDF WG we have a note on how to replace blank nodes with identified ones 19:01:07 Avoid where possible. 19:01:18 @ olyerickson it was rreck 19:01:27 @sandro thanks 19:01:28 olyerickson: I'm quite familiar with microformats. :) It may well be that the Google Refine code we're using to import data defaults to vCard? (We're still building a proof-of-concept; that stuff will be refined as we go) 19:01:33 ... looks like blank nodes are not "liked" in general 19:01:50 cygri: re. validation there is one available from the W3C 19:02:01 ... but it only supports RDF/XML and not Turtle 19:02:12 ... it is worth raising the point to the RDF WG 19:02:20 +1 this group can say how important an RDF validator (with Turtle, etc) mght be for GLD. 19:02:22 ... and asking for Turtle support in the validation 19:02:52 ... talking about the validator operated b the W3C 19:02:53 HadleyBeeman RE Refine defaulting to vCard I wouldn't be surprised. Makes me wonder what e.g. socrata defaults to when it interprets data types 19:03:13 s/ b / by / 19:03:21 q? 19:03:31 ack me 19:03:31 cygri, you wanted to answer on validation and bnodes 19:03:42 cygri: Would be helpful if the GLD WG liaised with RDF WG that improved validation in .ttl would be very useful. 19:03:43 Bernadette: I can bring this up with the RDF working group (David Wood) 19:03:47 Michael: charter [[People, such as elements of FOAF or vCard in RDF. This is an area for particular attention to privacy considerations.]] - reminds me on the NeoGeo approach, see http://geovocab.org/doc/neogeo.html 19:04:16 sandro: when each of us votes to accept a FPWD it means that to the best of our knowledge 19:04:29 ... the working draft is correct 19:04:41 ... so each one is encouraged to review the working draft 19:04:46 ... and provide feedback 19:05:22 s/is correct/ has the WG consensus/ 19:05:28 Sandro: Appearance in a FPWD means there is consensus among the GLD WG. It is an accurate representation of the published view of the GLD WG. 19:05:35 q? 19:05:37 -HadleyBeeman 19:05:39 ack sandro 19:05:46 When you vote, you are agreeing that it should be published. There can be sections that are "undecided" 19:06:10 s/When/My understanding is that when/ 19:07:13 Michael: Iff we resolve on 23 Feb we can go public on 28 Feb 19:07:26 ... which means we show up on http://w3.org/TR/ 19:07:28 PhilA: W3C MarComm team should be advised of the upcoming publication of the batch of FPWD from the GLD WG. 19:07:29 "Government Linked Data Working Group proposes specs which will destroy the Internet, unless you comment now." 19:08:22 s/ MarComm/Comm/g 19:09:06 sandro: after the working drafts are out, we still have to iterate and refine them towards 19:09:10 ... the last drafts 19:09:23 s/last drafts/last call drafts/ 19:09:51 +HadleyBeeman 19:09:57 (charter says LC in oct 2012) 19:09:59 q? 19:10:10 PhilA: with vocabulary we can get to the last call draft faster than the rest 19:10:42 +1 to mhausenblas "febuary" proposal. Now I must jump off call... 19:10:45 HadleyBeeman has joined #gld 19:10:53 ... to speed up the process, we use the fact that the vocabularies are used currently 19:10:58 -olyerickson 19:10:59 Michael: thanks olyerickson and cya 19:11:04 bye! 19:11:11 thanks olyerickson! 19:11:21 ... so we might be able to reduce the implementation face 19:11:22 q? 19:11:23 Bye olyerickson 19:11:28 s/face/phase/ 19:11:41 @olyerickson : bye! 19:11:46 q? 19:12:08 ack me 19:12:08 mhausenblas, you wanted to talk about people vocab contribution 19:12:46 mhausenblas: re. representing people which is mentioned in the charter 19:12:57 q? 19:13:04 q+ to talk about people vocab 19:13:33 ... I am afraid of ending up with a very "shallow" vocabulary if we care too much about being compliant with every previous candidate 19:13:33 ack me 19:13:42 ... I'd be glad to contribute there 19:13:52 +1 to bhyland 19:14:02 I suspect this may be some of the conversations that are coming out of PhilA's group… re unique identifiers for people (and the privacy implications) 19:14:29 q? 19:14:33 ack sandro 19:14:33 sandro, you wanted to talk about people vocab 19:15:04 mhausenblas: reviewed GLD WG charter and noted: People, such as elements of FOAF or vCard in RDF. This is an area for particular attention to privacy considerations. Michael is willing to participate after FPWD re: privacy aspects ... 19:15:20 q+ 19:15:23 sandro: "people" topic is particularly sensitive because it implied privacy concerns 19:15:40 s/Michael is willing/Michael is not willing 19:15:45 ... schema.org is strong in regards of representing people 19:15:45 If the vocab forces that fields about people are filled in, the vocab might break privacy regulations 19:15:46 q+ to try and answer the privacy point made by mhausenblas 19:15:53 [14:15] s/Michael is willing/Michael is *not* willing/ 19:15:59 Michael: yes, contribute to people and thanks to sandro I now understand what the privacy part means 19:16:08 ... a lot of publishers would like to use schema.org fro representing people 19:16:12 Michael: I AM willing (after FPWD) 19:16:13 Sandro: Discussed schema.org's people vocab and we should give it due consideration. 19:16:28 q? 19:16:36 sandro, don't Google and Bing still index other forms of mark-up? (RDFa and microformats)? 19:16:52 Yigal has joined #gld 19:16:54 ack me 19:16:56 q? 19:17:16 cygri: one of the privacy concerns is the use of IFP 19:17:20 q+ to talk about the 'usefulness' of people vocab 19:17:22 q? 19:17:25 ack me 19:17:25 PhilA, you wanted to try and answer the privacy point made by mhausenblas 19:17:29 HadleyBeeman, RDFa and microformats are syntaxes --- the only vocab they plan to use is their own (I think -- that could perhaps change, too). 19:17:29 ... for example foaf:homepage 19:18:07 PhilA: there is an important distinction between describing person as individual animal vs. describing the identity 19:18:25 Michael: In fact, Google+Bing+Yahoo, parse microdata and RDFa lite 19:18:27 q? 19:18:33 ack me 19:18:33 mhausenblas, you wanted to talk about the 'usefulness' of people vocab 19:18:36 sandro, right, but if the argument for using schema.org's vocabulary is that it is more indexible, then wouldn't it also hold for the others? 19:19:27 HadleyBeeman, it would if schema.org had terms for these other uses cases, but I don't think they do (yet). 19:19:38 mhausenblas: people are involved in many areas for example in organization description you need a point of contact 19:19:42 q? 19:19:47 we COULD argue to schema.org that they should include these other terms we want. 19:19:59 ... we need to know what makes sense from government perspective 19:20:22 q? 19:20:25 q+ 19:20:31 http://xkcd.com/927/ 19:20:34 Sandro: we could ask schema.org to include those other things… for futher conversation in the future. 19:20:54 sandro: we could consider trying to add the ontologies as extension to schema.org 19:21:01 q? 19:21:22 q+ 19:21:27 ack bhyland 19:21:37 +1 to bhyland for having a serious discussion and an informed opinion on what our relationship should be with schema.org for use in government. 19:21:46 bhyland: We at least need a good answer for why not use schema.org, if we don't. 19:21:50 mhausenblas: we might invite danbri as he is involved in schema.org 19:22:03 ... AFAIK it is still very early 19:22:06 +1 to having danbri talk to this 19:22:20 ... as the process of extending schema.org is not finalized yet 19:22:58 q? 19:23:00 ack me 19:23:23 bhyland: in a previous webcast they showed interest in adding government related vocabs to schema.org 19:23:46 ... and encouraged people to act early 19:24:00 +1 bhyland We need to have a conversation with the schema.org folks about whether do to do these vocabs in schema.org, or whatever. 19:24:15 What is the extension mechanism for adding gov't vocabs to schema.org. 19:24:23 +1 to inviting Guha to speak to us 19:24:41 ACTION: bhyland to invite Vocab TF chair to talk about Schema.org extensions 19:24:42 Created ACTION-44 - Invite Vocab TF chair to talk about Schema.org extensions [on Bernadette Hyland - due 2012-02-02]. 19:24:45 q? 19:25:01 ACTION: bhyland to invite RV Guha to speak at GLD WG telecon on extension mechanism for adding to schema.org 19:25:02 Created ACTION-45 - Invite RV Guha to speak at GLD WG telecon on extension mechanism for adding to schema.org [on Bernadette Hyland - due 2012-02-02]. 19:25:53 sandro: there is a distinction between adding it and extending the schema through an extension mechanism 19:25:54 Michael: Exactly, sandro, the *Extension* mechanism is not (yet) defined 19:26:13 ... I think the former is at this time better 19:26:36 close ACTION-44 19:26:36 ACTION-44 Invite Vocab TF chair to talk about Schema.org extensions closed 19:26:39 q? 19:26:54 q+ to say nothing more, really 19:27:16 PhilA: Any events happening in next 6 mos that we could leverage for next F2F. 19:27:20 PhilA: an upcoming event... on the 21 June 19:27:37 ... and 22nd "the digital agenda summit" in Brussel 19:28:04 q+ 19:28:05 ... June 21-22, 2012 in Brussells Digital Agenda Summit ... good place to meet possibly? Govies from EU in Brussels. 19:28:12 q- 19:28:17 ... plenty of government people will be in Brussel 19:29:11 lanyrd.com? 19:29:24 http://xkcd.com/927/ 19:29:37 that's for any conference 19:29:40 http://epsiplatform.eu/ 19:29:41 http://epsiplatform.eu/news 19:29:48 mhausenblas: a list of government-related events http://epsiplatform.eu/ 19:29:56 q? 19:30:08 lanyrd.com does track by keywords… open data is one, linked data is another that theytrack 19:30:16 Mike_Pendleton: Smetech is also interesting 19:30:40 Michael: Agreed, also outreach into WWW in Lyon 19:30:48 bhyland: I submitted a talk there 19:30:49 Mike_Pendleton_ has joined #gld 19:30:58 +1 to WWW 19:30:59 Also, I'm doing an open data workshop at WWW2012 19:32:26 http://www2012.wwwconference.org/ 19:33:19 http://lanyrd.com/search/?context=future&q=open+data 19:33:26 @HadleyBeeman: could you provide the link of the workshop on open data? 19:33:35 (sorry to bang on about this— but lanyrd.com is so easy to use!) 19:33:51 thnx HadleyBeeman ! 19:33:59 q? 19:34:08 ack Mike_Pendleton_ 19:34:13 Mike_Pendleton asked about whether WG is giving a talk at SemTech West in June. Answer: Yes, bhyland submitted one on behalf of the WG. 19:34:13 q- 19:34:28 q- Mike_Pendleton_ 19:34:35 ack Mike_Pendleton 19:34:38 For Gatemezi: Open Data in Practice workshop at WWW2012 (last on the page): http://www.w3.org/2012/04/tuto-track.html 19:34:47 mhausenblas: we can have a Google+ hangout for outreach 19:35:19 Michael: The nice thing is that we can record is as well, we can share screen and docs - once FPWD are out we can try this for an hour 19:35:49 Thx bhyland!! 19:35:52 bhyland: we need to be more active on the egov blog as well 19:35:55 q+ Pint of Smithwicks Please 19:36:29 Great to see you all! 19:36:42 glawway out! 19:36:47 -galway 19:36:59 bye, thanks. 19:37:01 sandro: Are you taking care of the minutes? 19:37:11 -t_gheen 19:37:12 bye 19:37:32 Bye, all. Enjoy the pub(s)! 19:37:41 -HadleyBeeman 19:37:43 PhilA, uh, sure. 19:37:55 -Washington 19:37:56 sandro: I should have said "please" 19:37:59 -sandro 19:37:59 -stasinos 19:38:00 SW_e-Gov( GLD)6:30AM has ended 19:38:02 Attendees were galway, HadleyBeeman, fadi, PhilA, dvilasuero, cygri, mhausenblas, GofranShukair, BartvanLeeuwen, csarven, BenediktKaempgen, gatemezin, sandro, olyerickson, 19:38:05 ... GeraldSteeman, boris, Washington, t_gheen, spyroskotoulas, DeirdreLee, DaveReynolds, stasinos, +1.703.201.aaaa 19:38:11 Yigal has left #gld 19:38:19 HadleyBeeman has left #gld 19:41:42 Suggested: Google+ Hangout once the the various FPWD's are released. 19:41:46 ping 19:42:44 mhausenblas has joined #gld 19:43:49 RRSAgent, set logs world-visible 19:44:01 RRSAgent, generate minutes 19:44:01 I have made the request to generate http://www.w3.org/2012/01/26-gld-minutes.html bhyland 19:53:04 PhilA has left #gld 21:40:46 Zakim has left #gld 22:58:26 BartvanLeeuwen has joined #gld 23:26:09 cygri has joined #gld