17:01:17 RRSAgent has joined #rdf-star 17:01:21 logging to https://www.w3.org/2023/02/16-rdf-star-irc 17:01:21 RRSAgent, make logs Public 17:01:22 please title this meeting ("meeting: ..."), ora 17:01:30 present+ 17:01:34 meeting: RDF-star teleconference 17:01:34 present+ 17:01:39 present+ 17:01:40 chair: ora 17:01:53 rrsagent, pointer? 17:01:53 See https://www.w3.org/2023/02/16-rdf-star-irc#T17-01-53 17:02:27 scribe+ gkellogg 17:03:35 https://w3c.github.io/scribe2/scribedoc.html 17:04:07 topic: approve minutes 17:04:23 https://www.w3.org/2023/02/09-rdf-star-minutes.html 17:04:43 olaf has joined #rdf-star 17:04:47 Dominik_T has joined #rdf-star 17:04:52 present+ 17:05:05 ora: propose to accept minutes 17:05:06 present+ 17:05:19 +1 17:05:26 +1 17:05:32 +1 17:05:42 +1 17:05:57 minutes accepted 17:06:24 topic: Semantic Predication 17:06:36 s/topic: Semantic Predication// 17:06:40 q+ 17:06:44 topic: status updates 17:06:58 ack az 17:06:59 q? 17:07:13 az: can we talk about levels of conformance? 17:07:45 zakim, who's here? 17:07:46 Present: enrico, AndyS, gkellogg, ktk, gtw, olaf, ora, rubensworks, pchampin, pfps, AZ, Dominik_T, Doerthe, TallTed 17:07:47 On IRC I see Dominik_T, olaf, RRSAgent, AZ, enrico, gkellogg, ora, AndyS, TallTed, ghurlbot, csarven, Tpt, Zakim, Timothe, ktk, gtw, rhiaro, agendabot, pchampin 17:08:16 scribe+ 17:08:28 https://github.com/w3c/rdf-star-wg/blob/340418d1e8ee3647912699d8ecdbbd28af1d58c7/docs/text-direction.md 17:08:31 gkellogg: discussion on text direction 17:08:44 pfps has joined #rdf-star 17:08:45 ... some activity from the I18N folks 17:09:22 ... proposing to extend abstract syntax to include text direction as a component of literals 17:09:32 q+ 17:09:40 ... this was an issue in JSON-LD 17:10:06 ... we now have the opportunity to update this in a more fundamental way 17:10:21 ack pfps 17:10:59 pfps: I argue that RDF language text strings do not need text direction. It does not change the meaning of the string at all. 17:11:15 ... It's only necessary for presentation. 17:11:30 ... I'd argue against I18N group if they push back. 17:11:41 ... RTL and LTR would compare as different things. 17:11:46 q+ 17:11:54 ack gkellogg 17:12:00 scribe+ 17:12:16 q+ 17:12:19 ack ora 17:12:19 gkellogg: not enough experience present - suggest a special meeting 17:12:36 ora: Yes, agreed, that's a prudent way to go. 17:12:50 ... The whole thing with text direction is sort of "black magic". 17:13:07 ... I've faced this before and welcome more expertise. 17:13:30 AndyS: I have a friend that speaks aribic, and he though it might be tough to accomplish. 17:13:44 ... The way it interacts with URLs is. 17:13:48 s/aribic/arabic 17:14:10 ... It's complicated when there are bits of text floating around. 17:14:27 Souri has joined #rdf-star 17:14:29 s/aribic/arabic/ 17:14:36 present+ 17:15:43 pfps: I'd like to get it done early. It will change every document and piece of software. 17:15:57 regrets+ 17:16:15 ... It's a fundamental change to RDF; potentially just as fundamental as embedded triples. 17:16:23 q+ 17:16:32 ora: whether it's a change or not, it would be good to understand it. 17:16:45 action: chairs to contact I18N group to start discussion. 17:16:52 Cannot create action. Validation failed. (Invalid user for this repository?) 17:17:46 topic: Use Cases 17:17:50 q- 17:18:08 pfps: I sent out an invite to join the task force. There are a number of people on the group. 17:18:24 ... I sent out some messages on a proposed policy and some example use cases, without feedback. 17:18:25 q+ 17:18:34 ack ora 17:18:35 ... Either make comments, or produce your own. 17:18:46 ... I'll put that in the issue. 17:18:50 q+ 17:18:54 q? 17:19:09 ack AndyS 17:19:19 AndyS: Were the ones from the CG be carried over? 17:19:44 pfps: I will take it upon myself to have someone reach out the the proposers to create real issues for the WG. 17:19:57 AndyS: I'm worried it's putting barriers in the way. 17:20:26 pfps: It needs to be more than a couple of sentences. A WG member could pick it up and continue the work. 17:20:44 ... I'll make sure that every existing UC has an entry. 17:21:42 topic: SPARQL docs 17:22:02 AndyS: Does are passing checks, except for entailment, which requires an editor. 17:22:08 pfps: I volunteer! 17:22:29 ... I looked at it a while ago and expect it won't need much change. 17:23:32 topic: Conformance 17:23:34 pfps, find the use cases doc from the CG at https://github.com/w3c/rdf-star/tree/main/UCR 17:24:39 AZ: I proposed two options: one to say we have only one standard RDF 1.2, but define a weaker conformance that only requires we conform to slight updates to RDF accounting for errata and so forth, but exclude embedded triples. 17:24:49 ... That might be "weak" or "classic" conformance. 17:24:52 q+ to say that the non-embedded conformance should be called RDF 1.1 17:25:03 ... Full conformance would take embedded triples into account. 17:25:25 ... The other option is to say there are two versions of RDF, one with embedded triples, and the other without. 17:25:48 ... Maybe "RDF-no-star" and "RDF". No weak or full, you just implement one or the other. 17:26:03 q+ 17:26:08 ... Like various OWL profiles, you implement a different specification. 17:26:30 ... We can conform to one or the other. 17:26:33 ack pfps 17:26:33 pfps, you wanted to say that the non-embedded conformance should be called RDF 1.1 17:26:45 ... Or there's only standard, but two ways to conform. 17:27:06 ... I'd say if we have a profile plus full RDF 1.2, we have two specifications. 17:27:28 ... There are risks, but having a clearly identified profile would make it more clear what the conformance is. 17:27:48 pfps: I'd suggest "weak" should be called RDF 1.1 or RDF 1.1.1. 17:27:49 q? 17:28:13 AZ: there are names for two types of conformances, and names for different profiles. 17:28:34 ... I'd say that "weak" is a way of partially conforming, and RDF-no-star would be it's own thing. 17:28:42 ack ora 17:29:08 pfps: If it's a profile than something that abides by it needs to be able to deal with embedded triples. 17:29:34 AZ: when I say profile, I don't mean exactly the same thing as OWL. I'm using it in a more informal way. 17:29:48 ... A sub-language of RDF 1.2 which does not include embedded triples. 17:30:08 ora: Wouldn't RDF 1.1 conformance be something we already have. 17:30:32 ... If we make the other non-star changes to the spec, it would be a possibility. 17:30:44 ... Secondly, how has the OWL profile mechanism worked in practice? 17:31:04 AZ: I'm not sure about all the details about OWL 2 profiles. 17:31:21 q+ 17:31:21 ... The profiles mostly restrict reasoning. 17:31:51 pfps: A number of OWL processors accept ontologies as RDF documents and complain if there's something they can't handle. 17:32:13 q+ 17:32:19 ... There are other processors which look at it and determine what profile it fits in, and then use that using an appropriate reasoner. 17:32:20 ack Souri 17:32:53 pfps: In some cases, there is something out side of the system that determines if it's okay. 17:33:14 Souri: In Oracle, we allow the user to specify what profile to use (-OL or -EL). 17:33:25 ack ora 17:33:54 ora: I think the situation with OWL profiles is different, as there is no syntactic difference. 17:34:05 ... In RDF-star, processors will see input they can't handle. 17:34:06 q+ 17:34:26 s/-OL/-RL/ 17:34:33 pfps: There is and is not difference in OWL profiles when it comes to the native syntax. 17:35:08 ... What happens is before the ontology is set to the reasoner there is a step to be sure the ontology fits. 17:35:35 ack gkellogg 17:36:40 q+ 17:37:06 ack AndyS 17:37:31 AndyS: Is there going to be one profile that _is_ RDF 1.2, and others that are subsets? 17:37:55 ... If we have two with equal weight, there's a bifurcation. We should make 1.2 _the_ output. 17:38:16 ... The charter is no changes that change RDF 1.1 entailments. 17:38:32 ... No changes such that an RDF 1.1 processors would make different directions. 17:39:05 ... Text Direction would make such a change. If we're touching quite a lot of bits and pieces, we can end up trying to parse the charter to see if we conform. 17:39:10 q+ 17:39:23 ... Every WG that has had a charter to not change something ultimately needs to make a judgement. 17:39:40 ack ora 17:39:45 ... Sometimes things come up which are obvious improvements. 17:40:06 ora: We have several things that are important. Backwards compatibility and bifurcation. 17:40:30 ... Ideally, I'd like to see a new spec that everything must conform to, but that may be to idealistic. 17:40:44 ... Some might choose one set of new features over another. 17:41:18 ... We already have RDF 1.1 conformance. If we make small changes outside embedded triples, it should be included in "weak/classic" conformance. 17:41:55 ... If we add things that substantially change things. 17:42:21 AndyS: If you introduce a datatype that introduce things that processors are supposed to interpret, you've fundamentally changed things. 17:44:04 ... Considering SKOS labels, if you introduce something that gets too naively passed through 1.1, things can get lost. 17:44:29 ... We're also set up for a living specification that does allow new features to be introduced. 17:44:46 ora: What's the way forward? 17:44:59 ... there's obviously embedded triples or no embedded triples. 17:45:11 q+ to say no levels 17:45:15 ... I'm not sure what happens if we say there are a lot of new features and you can pick and choose. 17:45:31 AndyS: The RDF 1.1 WG did make a big change by getting away with strings having no datatype. 17:45:40 ... It went smoothly. 17:46:05 ... Within the SPARQL WG, it was an issue. 17:46:19 ... It gets in the way if you're too dogmatic about "no changes". 17:46:33 q- 17:46:46 ... Data is different though, as it stays around much longer. 17:47:19 ora: Next step is to write an actual proposal. The conversation is useful, but a bit abstract. 17:48:05 ... I'm seeing there's old, new, and embedded triples. 17:48:42 topic: next steps 17:49:02 +1 to defer - this discussion needs some time 17:49:03 ora: I wanted to discuss Enrico's work, but think we should defer to next week. 17:49:28 enrico: There's a good discussion on the mailing list. 17:49:30 +1 to a meeting specifically on Enrico's inout 17:49:32 RRSAgent, draft mminutes 17:49:32 I'm logging. I don't understand 'draft mminutes', TallTed. Try /msg RRSAgent help 17:49:36 RRSAgent, draft minutes 17:49:38 I have made the request to generate https://www.w3.org/2023/02/16-rdf-star-minutes.html TallTed 17:49:45 s/inout/input/ 17:49:48 RRSAgent, make logs public 17:50:10 ora: In conformance, let's work on writing down something concrete. 17:50:23 action: AZ to work on conformance proposal. 17:50:27 Cannot create action. Validation failed. (Invalid user for this repository?) 17:50:38 present- 17:50:45 RRSAgent, draft minutes 17:50:46 I have made the request to generate https://www.w3.org/2023/02/16-rdf-star-minutes.html TallTed 17:51:39 pchampin - please note bug in minutes generation. I should not be listed as present, only as regrets 17:52:23 action: Antoine-Zimmermann to work on conformance proposal 17:52:25 Created -> action #23 https://github.com/w3c/rdf-star-wg/issues/23 17:52:57 ora: Encrico will prepare an introduction for next week. 17:53:10 s/Encrico/Enrico/ 17:53:28 ora: adjorned 17:53:57 zakim, end meeting 17:53:57 As of this point the attendees have been enrico, AndyS, gkellogg, ktk, gtw, olaf, ora, rubensworks, pchampin, pfps, AZ, Dominik_T, Doerthe, TallTed, Souri 17:54:00 RRSAgent, please draft minutes 17:54:02 I have made the request to generate https://www.w3.org/2023/02/16-rdf-star-minutes.html Zakim 17:54:08 I am happy to have been of service, gkellogg; please remember to excuse RRSAgent. Goodbye 17:54:08 Zakim has left #rdf-star 17:54:11 zakim, draft minutes 17:54:15 olaf has left #rdf-star 17:54:17 rrsagent, please excuse us 17:54:17 I see 3 open action items saved in https://www.w3.org/2023/02/16-rdf-star-actions.rdf : 17:54:17 ACTION: chairs to contact I18N group to start discussion. [1] 17:54:17 recorded in https://www.w3.org/2023/02/16-rdf-star-irc#T17-16-45 17:54:17 ACTION: AZ to work on conformance proposal. [2] 17:54:17 recorded in https://www.w3.org/2023/02/16-rdf-star-irc#T17-50-23 17:54:17 ACTION: Antoine-Zimmermann to work on conformance proposal [3] 17:54:17 recorded in https://www.w3.org/2023/02/16-rdf-star-irc#T17-52-23