Souri: There was a question of getting some more functionality, however, AndyS pointed out a previous straw poll rejecting that

15:21:28 [dcharbon2]

AxelPolleres: It sounds like the comments have been addressed

15:21:44 [dcharbon2]

AndyS: Some of the issues have been opened as issues, everything should be noted

15:22:34 [dcharbon2]

AndyS: Would like to bring up a process issue for property paths, decided to publish with shortname. Will create a dangling document if property paths get merged into query specification. Will that cause a problem, can it be avoided?

15:22:36 [ivan]

zakim, unmute me

15:22:36 [Zakim]

Ivan should no longer be muted

15:22:38 [ivan]

q+

15:22:45 [ivan]

ack ivan

15:23:28 [dcharbon2]

ivan: to make things really nice, when we decide to merge the path into the query docuemnt, if we do decide that, we can put out a new version of the property paths document stating it has been discontinued and merged into the query document

15:23:37 [dcharbon2]

AndyS: That would be excellent

15:24:03 [dcharbon2]

ivan: When the group is closed, the site is set up so certain docs can be marked as retired and won't be available

AxelPolleres: If we psas this resolution, property paths would be allowed in update

15:41:10 [dcharbon2]

s/psas/pass

15:41:37 [AxelPolleres]

Strawpoll: any objections to allow full SPARQL1.1/Query WHERE clauses for update WHERE clauses?

15:42:02 [AxelPolleres]

Strawpoll: shall we allow full SPARQL1.1/Query WHERE clauses for update WHERE clauses?

15:42:07 [ivan]

+1

15:42:11 [dcharbon2]

+1

15:42:12 [AndyS]

yes +1

15:42:15 [ivan]

+1 for Orri

15:42:18 [pgearon]

+1

15:42:18 [MattPerry]

+1

15:42:19 [Souri]

+1

15:42:21 [chimezie]

0 (I'm cautious about allowing at the outset that amount of expressiveness in the update language)

15:42:21 [bglimm]

+1

15:42:21 [Prateek]

+1

15:42:23 [chimezie]

but will go with group

15:42:26 [kasei]

+1

15:42:31 [AxelPolleres]

+1

15:42:48 [LukeWM]

0

15:42:58 [dcharbon2]

AxelPolleres: Chimezie, can you elaborate your concerns?

15:43:05 [OlivierCorby]

+1

15:43:49 [dcharbon2]

chimezie: this would allow all constructs from 1.1 and there are some constructs that aren't fully settled. Understand using feedback to determine what to not allow in these where clauses in the update language.

ivan: Lee sent out an email about who might be at semtech. Please answer, we might propose to have a panel as we did previously

16:01:33 [dcharbon2]

ivan: need to know if there will be enough people to do that

16:02:01 [dcharbon2]

kasei: Talking with LeeF, about test cases. Need to start thinking about that and perhaps cover in a future call?

16:02:08 [AndyS]

+1 to starting to gather test cases

16:02:16 [kasei]

yes, thanks ivan.

16:02:33 [ivan]

bye everybody

16:02:34 [Zakim]

-Orri

16:02:34 [Zakim]

-Souri

16:02:35 [bglimm]

bye

16:02:37 [ivan]

zakim, drop me

16:02:37 [Zakim]

Ivan is being disconnected

16:02:38 [Zakim]

-Prateek

16:02:38 [Zakim]

-Ivan

16:02:40 [Zakim]

-AxelPolleres

16:02:42 [AndyS]

ADJOURNED

16:02:42 [Zakim]

-AlexPassant

16:02:45 [Zakim]

-bglimm

16:02:46 [Zakim]

-Matt

16:02:48 [Zakim]

-chimezie

16:02:52 [Zakim]

-kasei

16:02:54 [Zakim]

-dcharbon2

16:02:56 [Zakim]

-OlivierCorby

16:02:58 [Zakim]

-AndyS

16:03:37 [Zakim]

-pgearon

16:04:50 [AxelPolleres]

rrsagent, make records public

16:08:02 [OlivierCorby]

OlivierCorby has left #sparql

16:13:25 [AxelPolleres]

Summary for next time: We need to (1) resolve on publication for protocol and update, (2) we should talk about publishing process/schedule (probably just among team/chairs) (3) we should continue on the update issues, (4) we have discussion of comments open (some unresponded really old ones) (5) we have to talk about test cases... thanks everybody!