15:00:20 RRSAgent has joined #shapes 15:00:20 logging to http://www.w3.org/2014/11/12-shapes-irc 15:00:22 RRSAgent, make logs rdf-data-shapes 15:00:22 Zakim has joined #shapes 15:00:24 Zakim, this will be 15:00:24 I don't understand 'this will be', trackbot 15:00:25 Meeting: RDF Data Shapes Working Group Teleconference 15:00:25 Date: 12 November 2014 15:00:42 zakim, this is shapes 15:00:42 ok, Arnaud; that matches DATA_RDFWG()10:00AM 15:01:08 +Arnaud 15:01:39 SteveS has joined #shapes 15:02:01 +karima 15:02:03 zakim, who's on the phone? 15:02:03 On the phone I see kcoyle, [IPcaller], Arnaud, karima 15:02:20 zakim, [IPCaller] is me 15:02:21 +hknublau; got it 15:02:29 +Arthur_Ryman 15:02:43 +Tony 15:03:16 arthur has joined #shapes 15:04:17 Irene has joined #shapes 15:05:19 solbrig has joined #shapes 15:05:30 + +1.914.777.aaaa 15:06:41 +[IBM] 15:06:48 Zakim, [IBM] is me 15:06:48 +SteveS; got it 15:07:05 Zakim, aaaa is Irene 15:07:07 +Irene; got it 15:07:20 zakim, who's on the phone? 15:07:20 On the phone I see kcoyle, hknublau, Arnaud, karima, Arthur_Ryman, Tony, Irene, SteveS 15:08:11 +ericP 15:10:26 Zakim, Tony is really HaroldS 15:10:26 +HaroldS; got it 15:11:01 Zakim, HaroldS is solbrig 15:11:01 +solbrig; got it 15:11:18 Scribe: SteveS chair: Arnaud agenda: http://www.w3.org/2014/data-shapes/wiki/Meetings:Telecon2014.11.12 15:11:51 Topic: Admin 15:12:55 Arnaud: will start with new day and time next week, Nov 20 Thurs @ 2pm ET 15:13:04 ... Skipping approval of minutes 15:13:26 Arnaud: minutes are still not in proper form, working with team as they are backloged after tpac 15:13:31 hopefully by next week 15:13:33 Topic: Tracking of Actions and Issues 15:13:54 Arnaud: Skipping tracking of actions and issues, have none yet 15:14:36 Topic: Relationship between shapes and resources 15:15:07 Arnaud: probably should open an issue for this, will when tracker up, been a long discussion on this 15:15:57 Arnaud: summarizes some of the positions based on emails and user stories, based on class or direct relationship 15:17:11 arthur: in context of OSLC, or some organization that is defining vocabularies for some domain and org also defining REST APIs so tools can provide a consistent interface for multi-vendor tools to interoperate 15:18:17 ... even in a given tool instance, it can host various scoping mechanisms (typically a projects) which have different configuration, based on a standard vocabulary + some customizations (either new properties or additional constraints) 15:19:27 Possible that even each resource could have its own specialization 15:21:22 Having a resource's type (class) linked to the constraint definition had issues as it would typically cause broader impact on resources controlled by different scoping mechanisms (projects), so we took an approach to link a resource or operation to a given shape. 15:21:27 +q 15:21:50 ack Tony 15:21:58 ack hknublau 15:23:27 hknublau: sees that if you don't have this linked to the type triple, you need to have something like that..which could be aligned. 15:23:57 ... this would point off to a graph that would describe the instance of that resource 15:25:42 It would characterize this as using named graphs for truth maintenance. 15:26:46 +q 15:26:59 It appears to exclude business processes with different constraints that have to talk to two interfaces at once. 15:27:02 +q 15:27:25 ack arthur 15:27:31 hknublau: describes approach he outlined in his email 15:28:48 arthur: getting further clearification on usage of owl:import 15:28:50 it is really about unions of graphs 15:29:15 hknublau: simple just using it as a way to link to another group, only owl term that is used 15:30:27 ack Irene 15:31:21 +q 15:31:28 ack arthur 15:31:55 Irene: the URI used is based on which graph it is contained it and then when it is dereferenced 15:32:05 +q 15:32:26 ack arthur 15:32:45 +q 15:33:12 ack hknublau 15:33:24 arthur: using http uris provides a single view of a resource, whether named graphs are in volved or not 15:33:37 +q 15:33:41 zakim, who's on the phone? 15:33:41 On the phone I see kcoyle, hknublau, Arnaud, karima, Arthur_Ryman, solbrig, Irene, SteveS, ericP 15:33:50 ack arthur 15:34:09 Zakim, Arthur_Ryman is arthur 15:34:09 +arthur; got it 15:35:41 +q 15:36:23 ack arthur 15:36:30 q+ to vocalize 15:37:24 (general discussion on various approaches and motivating use cases) 15:37:33 ack ericP 15:37:33 ericP, you wanted to vocalize 15:39:57 +q 15:40:54 ericP: summarizing some examples given in emaill that highlight some cases where shapes should be decoupled from type 15:41:07 +q 15:41:13 ack kcoyle 15:41:33 +q 15:41:38 i believe it's all type in the instance data 15:41:39 kcoyle: hoping to get clarification on what people are talking about when they are talking about type 15:41:51 ack arthur 15:42:10 arthur: type as present in the instance data, which could be more than one type 15:42:37 ack hknublau 15:43:43 hknublau: interested in multiple nesting and context aware constraints, have pointed out in latest response to ericP, by using sparql 15:44:42 +q 15:44:46 +q 15:45:14 +q 15:45:50 ack solbrig 15:47:17 solbrig: outlining a different use case, involves what information is required in a graph or what is not in it 15:47:48 ... looking at data model we typically find in UML and progressively apply constraints, such as labratory test data 15:49:00 may require gender as part of the test who is of type :Person and also recorder who is of type :Person, which would have different constraints 15:49:39 have attempted to use reasoners which help with what the data denotes but not if it contains certain data 15:49:42 ack SteveS 15:53:14 ack hknublau 15:53:27 SteveS: summarized how LDP has left off the ability to describe what LDPRS can be created ... hope was in the future something such as shapes chould be applied to define these constraints 15:56:00 so can we gather more use cases?! 15:56:04 the request is to have more detailed use case descriptions 15:56:07 hknublau: was hoping we could get to some details to highlight the test cases and we could demonstrate how existing solutions can address tehm 15:56:20 +q 15:56:55 ack SteveS 15:57:11 with examples like data snippets because words are ambigious 15:57:20 +q 15:58:17 Arnaud: wants to focus on consensus of requirements 15:58:59 +1 to more examples 15:59:14 ack arthur 15:59:20 SteveS: think it makes sense to work towards a set of test cases (scenarios) and common requirements, we can continue to evaluate existing technologies and if a closer fit to what would motivate the work product of this WG 16:00:05 Arnaud: examples will help clarify it, will add them and encourage others to do so 16:00:45 s/Arnaud:/arthur:/ 16:01:23 -arthur 16:01:24 -solbrig 16:01:25 -hknublau 16:01:26 hknublau has left #shapes 16:01:26 -Irene 16:01:27 -kcoyle 16:01:28 -SteveS 16:01:30 -Arnaud 16:01:36 -ericP 16:01:39 Arnaud: continue to flush out user stories and go through items from DC requirements 16:03:51 trackbot, end meeting 16:03:51 Zakim, list attendees 16:03:51 As of this point the attendees have been kcoyle, Arnaud, karima, hknublau, +1.914.777.aaaa, SteveS, Irene, ericP, solbrig, arthur Present: kcoyle, Arnaud, hknublau, SteveS, Irene, ericP, solbrig, arthur regrets: pfps, Nick 16:03:59 RRSAgent, please draft minutes 16:03:59 I have made the request to generate http://www.w3.org/2014/11/12-shapes-minutes.html trackbot 16:04:00 RRSAgent, bye 16:04:00 I see no action items