14:53:04 RRSAgent has joined #lld 14:53:04 logging to http://www.w3.org/2011/03/10-lld-irc 14:53:10 emma has joined #lld 14:53:13 rrsagent, bookmark 14:53:13 See http://www.w3.org/2011/03/10-lld-irc#T14-53-13 14:53:22 zakim, this will be lld 14:53:22 ok, antoine; I see INC_LLDXG()10:00AM scheduled to start in 7 minutes 14:53:34 Meeting: LLD XG 14:53:46 Chair: Tom 14:54:18 Agenda:http://lists.w3.org/Archives/Public/public-xg-lld/2011Mar/0039.html 14:54:57 Previous: 2011-03-03 - http://lists.w3.org/Archives/Public/public-xg-lld/2011Mar/0033.html 14:55:55 INC_LLDXG()10:00AM has now started 14:56:02 +[IPcaller] 14:56:10 zakim, IPcaller is me 14:56:10 +antoine; got it 14:56:57 Regrets: kai, joachim, jodi, uldis, kim, felix, lars 14:57:15 rrsagent, please make record public 14:57:27 rrsagent, please draft minutes 14:57:27 I have made the request to generate http://www.w3.org/2011/03/10-lld-minutes.html antoine 14:57:32 +??P7 14:57:47 zakim, ??P7 is TomB 14:57:47 +TomB; got it 14:58:02 + +33.1.53.79.aaaa 14:58:06 + +1.614.764.aabb 14:58:18 zakim, aabb is jeff__ 14:58:18 +jeff__; got it 14:58:36 GordonD has joined #lld 14:58:57 zakim, mute me 14:58:57 jeff__ should now be muted 14:59:37 +[IPcaller] 14:59:48 zakim, IPcaller is GordonD 14:59:48 +GordonD; got it 14:59:53 ww has joined #lld 15:00:06 michaelp has joined #lld 15:00:12 pmurray has joined #lld 15:00:19 kefo has joined #lld 15:00:22 marcia has joined #lld 15:00:23 +[LC] 15:00:24 zakim, LC is me 15:00:24 +kefo; got it 15:00:40 rsinger has joined #lld 15:00:45 +jeff__.a 15:00:52 Scribe: kefo 15:00:57 Scribenick: kefo 15:00:58 zakim, mute m 15:00:59 michaelp should now be muted 15:01:00 zakim, mute me 15:01:01 kefo should now be muted 15:01:07 + +1.330.289.aacc 15:01:27 + +1.423.463.aadd 15:01:39 zakim, mute me 15:01:40 zakim, aadd is rsinger 15:01:47 marcia should now be muted 15:01:51 +rsinger; got it 15:02:03 +??P26 15:02:08 zakim, ??P26 is me 15:02:09 zakim, ??P26 is ww 15:02:11 +ww; got it 15:02:13 I already had ??P26 as ww, antoine 15:03:07 google talk is currently offering free calls to the US, btw 15:03:35 kcoyle has joined #lld 15:03:47 +??P28 15:03:58 zakim ??P28 is me 15:04:01 +??P0 15:04:05 Zakim, mute me 15:04:05 ww should now be muted 15:04:16 zakim, ??P28 is me 15:04:16 +pmurray; got it 15:05:17 rsinger: good to know... in my office now, i would guess that the u of edinburgh has a good bulk ld deal so hopefully i won't bankrupt them :) 15:05:20 TOPIC: Admin 15:05:20 rrsagent, plese draft minutes 15:05:20 I'm logging. I don't understand 'plese draft minutes', emma. Try /msg RRSAgent help 15:05:30 rrsagent, please draft minutes 15:05:30 I have made the request to generate http://www.w3.org/2011/03/10-lld-minutes.html emma 15:05:47 TomB: proposes accepting mtg minutes 15:05:51 +1 15:06:43 q+ 15:06:50 ack emmanuelle 15:06:53 [ I missed a lot of that - noise in the room on my end 15:07:09 an hour earlier is actually better for me :) 15:08:03 I won't chair on march 24th, Antoine will 15:08:21 TomB: Emma won't chair on 24 march, Antoine will 15:08:29 ... moving on to asia pacific telecon 15:09:11 ... it's late for many, but happy to accommodate asia pacific participants and thanks to those joining from US and Europe 15:09:17 ... Can we identify a scribe? 15:10:42 ... Also, goals: we should walk through main agenda points and explain what's going on, how the process is going, encourage participation from them (especially in reviewing sections of the report), and let's leave time to hear from participants who might have something to present or emphasize (topics important to them). 15:10:51 ... Will be a informal call. 15:11:03 ... Do others have suggestions or comments on this plan? 15:11:07 sounds good! 15:11:34 -pmurray 15:11:38 ... I'll try to confirm moving the call an our earlier. 15:11:43 TOPIC: Final report draft 15:11:46 + +1.614.372.aaee 15:11:58 TomB: About the executive summary. 15:11:59 zakim, aaee is pmurray 15:12:00 sorry, antoine, I do not recognize a party named 'aaee' 15:12:21 ... Benefits: Emmanuelle and Ed are working on benefits. Would either like to comment? 15:12:29 Emma: Not started yet, personally. 15:12:54 Are these actions or topics? 15:13:02 TOPIC: Use case and requirements 15:13:10 http://lists.w3.org/Archives/Public/public-xg-lld/2011Mar/0038.html 15:13:11 Can topics be "continued? 15:13:42 How to is not the problem. .... Thanks emma 15:13:53 ACTION: emma and ed to start curating a section on benefits of LLD for libraries [recorded in http://www.w3.org/2005/Incubator/lld/minutes/2011/02/24-lld-minutes.html#action06] 15:13:59 -- continues 15:13:59 ACTION: Use cases and requirements (represented via clusters, plus an annotated list of use cases, plus requirement list?) 15:14:30 TomB: We'll have a separate report on use cases. Not too long, but enough. 15:15:00 ... Would anyone like to edit this section of hte report? 15:15:23 q+ 15:15:34 ... You do get to place your name on separate sections (as "editor"), which may be attractive if anyone needs to demonstrate impact of participating in this group/ 15:15:46 q- 15:16:27 kcoyle: Do we really need separate documents (one for hte Use Cases)? 15:16:52 ... the clusters have been distilled. Perhaps we just need a wiki page to point . I feel we've done this already. 15:16:57 a report makes it more official for dissemination ? 15:17:10 TomB: I think we have to. But I'd like to formalize it a little. It does not need to be complicated. 15:17:24 q+ 15:17:25 kcoyle: I don't see it as a "document" but a "wiki" page because I'd want it linked. 15:17:28 Antoine: What did the SKOS do for the usecases? 15:17:33 ack kc 15:17:35 TomB: I see. No a wiki page is fine. It does not need to be offline. 15:17:50 ack antoine 15:18:03 Antoine: I'd like to comment, also, Marcia asked a question about UC in SKOS. 15:18:52 ... We took some of hte Use cases in SKOS and that document linked to other wiki pages . So it was a mix between placing some content in a document and placing some in a wiki. 15:19:52 Example of archived wiki page: http://www.w3.org/2006/07/SWD/wiki/Deliverables 15:19:52 ... Regardin Karen's suggestion: A wiki can be edited, making it dynamic, and the W3C cannot archive a Wiki in quite the same way as a "document." They're are labelled as "archived" and no longer actively maintained. 15:20:29 TomB: Here is an example of a frozen wiki page: http://www.w3.org/2006/07/SWD/wiki/Deliverables 15:20:47 TomB: Not going to resolve this unless we have avolunteer. 15:20:51 --continues 15:21:13 -- continnues 15:21:15 -- continues 15:21:18 I give mup/ 15:21:45 ACTION: ACTION: Uldis and Jodi to create social uses cluster 15:21:50 -- continues 15:22:00 rrsagent, please draft minutes 15:22:00 I have made the request to generate http://www.w3.org/2011/03/10-lld-minutes.html emma 15:22:04 zakim, unmute me 15:22:04 kefo should no longer be muted 15:22:40 Kefo : sent an email to the list that completes the action 15:22:45 http://lists.w3.org/Archives/Public/public-lld/2011Mar/0092.html 15:22:58 http://www.w3.org/2005/Incubator/lld/wiki/Web_services_on_LLD 15:23:33 ACTION: Kevin and Joachim to review content of existing clusters to see where the web service dimension could be strengthened. 15:23:34 done 15:23:47 --done 15:24:23 zakim, mute me 15:24:23 kefo should now be muted 15:24:46 Zakim, unmute me 15:24:46 ww should no longer be muted 15:24:50 ACTION: Available data (vocabularies, datasets) (Antoine and Jeff) 15:24:57 - continues 15:25:10 TomB: We need to start closing some of these open actions. 15:25:17 +1 for closing the action 15:25:19 +1 15:25:35 Zakim, mute me 15:25:35 ww should now be muted 15:25:47 ACTION: Volunteers to send login information (openid credentials) to William Waite to curate LLD group on CKAN [recorded in http://www.w3.org/2010/11/25-lld-minutes.html#action04] 15:25:49 --done 15:25:55 TomB: Main point of call. Gordon's analysis/ 15:26:23 TOPIC: PROBLEMS / LIMITATIONS / ISSUES - SECTION IN REPORT 15:26:25 GordonD: Let's concentrate on sections 1 and 3. Section 2 (granularity) can probably be incporated into problems and limitations. 15:26:57 -> http://www.w3.org/2005/Incubator/lld/wiki/Library_standards_and_linked_data 15:27:02 ... we'll being with section 1: Issues for further discussion 15:27:26 ... benefits of "Constrained versus unconstrained properties and classes" 15:27:34 ... there's been recent disucssion about this on the list. 15:27:44 http://lists.w3.org/Archives/Public/public-lld/2011Mar/0055.html 15:27:51 ... Tom summarized the discussion nicely. 15:28:24 ... If we replace direct references to FRBR to something more generic like "library standards" we can get something out of this page, 15:29:03 ... Are there any comments on the pros and cons of "Constrained versus unconstrained properties and classes"? 15:29:21 TomB: Are you saying that both are needed? That if you do not have "constrained" properties you will lose information? 15:29:36 GordonD: Yes, that is what I'm saying. 15:29:49 LarsG has joined #lld 15:29:52 q+ to suggest getting inspiration from DC 15:29:58 q+ 15:30:09 TomB: The value of constrained properties allows for inferencing of more knowledge. 15:30:23 +[IPcaller] 15:30:34 zakim, IPcaller is me 15:30:34 +LarsG; got it 15:30:42 zakim, please mute me 15:30:42 LarsG should now be muted 15:30:47 ack emma 15:30:47 emma, you wanted to suggest getting inspiration from DC 15:30:50 GordonD: Yes. I take the point of unrestrained properties, and I've worked to find a middle ground with some groups. 15:31:29 Emma: I think we can look at DC, where the elements were unconstrained versus later definitions where some ranges are applied. 15:32:02 ... Some use the elements because they are unconstrained, others use the otheres. But, still, many do not recognize the distinction. 15:32:31 q+ 15:32:39 GordonD: I agree. People want and require guidance on this. How does someone choose a set of classes and properties from namespaces. It might be obvious to us, but not others. 15:33:00 q+ 15:33:03 s/otheres/constrained terms 15:33:06 .. I see a more general guidance piece coming out of this that addresses the mixing and matching and the choices implementers have/ 15:33:26 ack kcoyle 15:34:21 kcoyle: I'm going to question this. I see a far amount of guidance in the unconstrained properties. Take, for example, Work Title. Must that be constrained to FRBR Entity - it already has a clear meaning? It is defined inepdenently. 15:34:42 q+ to point out that SKOS has both constrained and unconstrained properties. The question is: which properties need to be constrained? Hopefully no more than necessary. 15:34:51 +1, Karen : guidance & data constraints are 2 different things 15:34:56 ... Some analysis should be done. Some *need* to be constrained to have meaning. But others do not. 15:34:59 +1 15:35:04 +1 15:35:05 +1 15:35:08 ... I see constraints as overkill. 15:35:10 q? 15:35:28 q+ 15:35:37 GordonD: I disagree. What will happen people will look at hte documentation and will choose a property based on the definition and not its context. 15:36:36 kcoyle: That argues for entity constraints on everything in the sem web. 15:36:47 GordonD: Library data is particularly semantically rich. 15:36:59 kcoyle: I don't know if it is that much different than other data. 15:37:15 ack me 15:37:16 ack jeff__ 15:37:21 ... I don;t see the problem, the need to constrain. 15:37:44 jeff_: I tend to agree with GordonD. The constraints help to tell me what they mean (not just how to use them). 15:38:13 or subclassed to rda without constraints, as in the registry 15:38:30 ... They provide a level of confidence in interoperability. But you can achieve this my constraining the FRBR ontology but sub-classing FRBR classes/properties to DC, for example. 15:38:40 GordonD: Yes. That is the middle ground. 15:38:46 s/my/by 15:39:05 zakim, mute me 15:39:05 jeff__ should now be muted 15:39:16 ack antoine 15:39:23 ... Use contrained versions where possibe and suitable to protect against data loss, but unconstrained when it matters less. 15:39:34 Antoine: I feel a little uncomfortable with constrained as well. 15:39:48 q+ 15:41:03 ... We should be careful about the granularity of hte semantics we want with these constraints. 15:41:09 I agree with Antoine on the point of overconstraint 15:41:17 Here is a place to see RDA properties by entity: http://kcoyle.net/rda/group1propsby.html 15:41:52 ... A benefit of constraints is that I can *infer* knowledge. But, this can be remedied with more expressing facts more explicitly. 15:42:43 +1 15:42:46 ack TomB 15:42:47 TomB, you wanted to point out that SKOS has both constrained and unconstrained properties. The question is: which properties need to be constrained? Hopefully no more than 15:42:49 ... necessary. 15:42:50 ... Finally, a practical addition to argument against constraints: you are adding many elements to your namespace. 15:43:39 TomB: When defining SKOS we wanted to keep it as simple as possible. So, some have domains, but others do not. Labelling properties are not restricted only to Concepts. I can be a "preferred label" for abnything you want to use it for. 15:44:05 ... We were cautious about restricting domains and ranges in order to facilitate adoption and use. 15:44:20 q+ 15:44:43 ksclarke has joined #lld 15:44:46 ... If you mechanically replicate properties and classes for *everything* it can lead to a proliferation of classees and properties. Perhaps the constraints should only be used prudently and carefully. 15:44:53 ack michaelp 15:45:11 ksclarke has left #lld 15:45:22 michaelp: My comments follow along the lines of Antoine's and Tom's. 15:47:01 ... Constraints tend to be used to specify semantically what we mean. We should be careful about what constraints here mean. In OWL, constraints can negatively impact interoperability because of inconsistency. 15:47:35 ... OWL makes assumptions about hte entities based on the properties. It's not *meaning* but "inferencing." 15:47:39 i completely agree with this 15:47:43 ack me 15:47:57 Michael: we should be careful about what constraints mean. OWL enforces constraints as "inconsistency". Use of X property forces something to considered a "work" (for example). It's not validation, it's inference, so be careful. Much of the constraints should happen on the side of the classes, not with proliferation of properties. 15:48:05 +1 for what michaelp said 15:48:14 +1, michaelp 15:48:19 q+ for proposing a modelling exercise 15:48:22 jeff_: I appreciate constraints when they make sense. 15:48:30 validation vs. inference -- validation means applying inference rules to exhaustion and not entailing a contradiction (modulo cardinality and such which dodn't work well) 15:48:40 q? 15:48:49 s/dodn't/didn't/ 15:48:53 ack kcoyle 15:49:06 zakim, mute me 15:49:06 jeff__ should now be muted 15:49:27 karen: I want to clarify a couple of things. There are alot of levels between constrained and unconstrained RDA. 15:49:46 ... We should consider that *some* require constraints. Therefore, not an all or nothing view. 15:50:06 .. People are concerned about WEMI Group 1, but less so Group 2 & 3. 15:50:15 .. People are concerned about the constraints on WEMI Group 1, but less so Group 2 & 3. 15:50:31 ... We should consider constraints applied to application profiles. 15:51:26 GordonD: Communities have invested huge effort into these models. They're well-defined and structured. i"m a little surprised that such rich models are not being welcomed as much as I would have expected. 15:52:10 ... We're trying to get general points out of this discussion. The details about the constraints on WEMI, for example, are us talking about the trees and missing the forest. 15:52:26 ack antoine 15:52:26 antoine, you wanted to discuss proposing a modelling exercise 15:52:51 Antoine: Agree with Gordon. We could be talking about any model., not just a FRBR one. 15:54:20 ... Could we continue this discussion by a type of modeling exercise? Taking the name and consider its modeling with properties versus classes. 15:54:36 i would like to see properties v. classes modeled 15:54:48 GordonD: I think this is a good proposal. 15:54:52 maybe in an 88 post email thread ;) 15:55:02 :-D 15:55:07 :-) 15:55:13 TomB: Gordon, bring us home... 15:55:28 GordonD: Application profiles, OWL ontologies. 15:55:37 perhaps we could just have it as an open issue in the final report... 15:55:39 ... Which might be better? 15:56:02 is this a matter for our report, or a question we want to incubate? 15:56:11 ... Perhaps it would be best to outline the pros and cons to each, which would touch on the constrained versus unconstrained issue. 15:57:06 q+ to scope what LLD XG can say and what we can identify as a problem 15:57:09 ... There's little agreement about hte *best* approach, but we could provide guidance by outlining the options. 15:57:18 ack TomB 15:57:18 TomB, you wanted to scope what LLD XG can say and what we can identify as a problem 15:57:49 +1 15:58:05 ack kcoyle 15:58:15 TomB: I think it's great if we can make some progress on this topic by looking at examples, but it might be unrealistic to provide solutions versus identifying the problem. We nee to be realistic about what we can do, especially in the time reamining. 15:58:37 GordonD: Quickly to section 3, linked data and legacy records 15:59:12 ... In many ways this is the flip side of what we were just talking about. Libraries are sitting on mounds of data. Many are beginning to see how opening this up would be beneficial. 15:59:18 q+ 15:59:29 ack kcoyle 15:59:30 ... We've had a number of discussions about this and I think we can bring some of these issues in. 15:59:37 ... Do others have something to say? 16:00:05 q+ 16:00:09 kcoyle: I think legacy data nad the constraint issue come together. Hard to move data into a constrained model. 16:00:59 GordonD: I actually see the existence of constrained properties assisting with providing additional value to legacy data. 16:02:09 ... for example, one could output standard MARC records to ISBD, as an initial step, and then, using property/class relationships, move to other namespaces, finally ending on a more FRBR model. But I just thinking out loud. 16:02:13 ack rsinger 16:02:38 and remember that there is a lot of non-library bibliographic dta 16:02:43 s/dta/data 16:02:53 rsinger: Not seeing how we will bridge the gap between current models/formats and a future one. 16:03:31 GordonD: We do the best we can. history has a way of working these things out. 16:03:38 fair enough 16:03:58 ++ for optimistic observation as closing remark :-) 16:03:58 TomB: We need to adjourn. I look forward to talking to others tomorrow to talk about problems and issues. 16:04:08 -michaelp 16:04:09 -jeff__ 16:04:09 -marcia 16:04:11 -kcoyle 16:04:11 bye 16:04:12 thanks ! 16:04:12 .. Mtg adjourned 16:04:14 -GordonD 16:04:15 -ww 16:04:17 -rsinger 16:04:21 zakim, unmute me 16:04:21 kefo should no longer be muted 16:04:23 -LarsG 16:04:25 zakim, who is on the call? 16:04:25 On the phone I see antoine, TomB, emma, kefo, pmurray (muted) 16:04:28 zakim, please list attendees 16:04:28 As of this point the attendees have been antoine, TomB, +33.1.53.79.aaaa, +1.614.764.aabb, emma, jeff__, GordonD, kefo, michaelp, +1.330.289.aacc, marcia, +1.423.463.aadd, rsinger, 16:04:32 ... ww, kcoyle, pmurray, +1.614.372.aaee, LarsG 16:04:37 -pmurray 16:04:39 rrsagent, please draft minutes 16:04:39 I have made the request to generate http://www.w3.org/2011/03/10-lld-minutes.html antoine 16:07:01 -kefo 16:07:06 michaelp has left #lld 16:07:44 http://lists.w3.org/Archives/Public/public-xg-lld/2011Mar/0038.html 16:07:54 rrsagent, please draft minutes 16:07:54 I have made the request to generate http://www.w3.org/2011/03/10-lld-minutes.html antoine 16:20:08 -emma 16:20:13 -antoine 16:20:17 -TomB 16:20:19 INC_LLDXG()10:00AM has ended 16:20:20 Attendees were antoine, TomB, +33.1.53.79.aaaa, +1.614.764.aabb, emma, jeff__, GordonD, kefo, michaelp, +1.330.289.aacc, marcia, +1.423.463.aadd, rsinger, ww, kcoyle, pmurray, 16:20:22 ... +1.614.372.aaee, LarsG 16:20:29 pmurray has left #lld 18:14:14 Zakim has left #lld