– DRAFT –
Data Shapes Working Group

Phase 2 subgroups statuses

elianaP: Reminder call for consensus: 1st version of rules, node expressions and compact syntax

nicholascar: profiling subgroup starting this week

nicholascar: request for profiling outline

<nicholascar> The PR starting a Profiling Doc Intro: w3c/data-shapes#489

<AndyS> s/nicholascar profiling/nicholascar: profiling/

<AndyS> me - Robert also if it is the same person as lastlien the scribe types, then the line can be "... TEXT" (3 dots)

edmond: UI group starting, doodle for meeting

VladimirAlexiev: compact syntax status; enough people?

ValidationReport conformance values

AndyS: update on validation reports; service keyword allowed?

HolgerK: questions with only a few people interested, e.g. service keyword
… how to deal with such situations.

<VladimirAlexiev> nicholascar: w3c/data-shapes#489 is PR starting a Profiling Doc Intro:

bergos: voting via comments

<VladimirAlexiev> I'm emailing Jesse Wright asking for update on SHACL-C WG: plans, schedule, participants...

bergos: communicate deadline; 1 week for comments

TallTed: ok to have issues last for weeks; no urgency for now
… difficult foe people to keep up with issues. More time necessary.

<AndyS> w3c/data-shapes#453

elianaP: decision - voting in the issue with clear deadline

What to do about current SHACL permalinks - https://www.w3.org/TR/shacl/?

nicholascar: permalinks - where will links point?
… mapping where links without versions will point?
… where will af links point?

AndyS: same as OWL; seems to point to overview.

simonstey: disclaimer for outdated spec

nicholascar: old shacl should point to shacl core

<nicholascar> Here is the spec list in Overview: https://w3c.github.io/data-shapes/shacl12-overview/#shacl-1-2

<nicholascar> Here is the Overview spec listing: https://raw.githack.com/w3c/data-shapes/profiling-updates/shacl12-profiling/index.html#shacl-specifications

Total SHACL namespaces

nicholascar: namespaces for shacl; should we use 1 namespace for all shacl assets (rules, ui, ...)

HolgerK: we already have 2 namespaces (shacl, sparql). Assumption that there will be more + mixed up.

<VladimirAlexiev> +1 for a single *basic* namespace. the SHACL ontology is not too large to warrant splitting into subspaces.

HolgerK: suggest to intro a new namespace.

HolgerK: expect to have dozens of namepaces; db vendors, geosparql, ...

<Zakim> TallTed, you wanted to suggest shsparql: instead of sparql:, which feels like squatting, since we don't control SPARQL itself

VladimirAlexiev: propose single namespace if possible; people get confused with many namespaces
… node expressions should be different namespace.
… vendors use their own namespace; e.g. dash.

bergos +1 for less namespaces
… but node expressions should be different namespace.

<VladimirAlexiev> +1 for "when we see a bunch of reusable functions forming up, put them in namespace different from sh: , because people may reuse them outside of SHACL"

Adding visual diagrams to specs

VladimirAlexiev: diagrams should be added to spec
… grammar diagram for property paths added

<VladimirAlexiev> w3c/data-shapes#166

<VladimirAlexiev> w3c/data-shapes#471

<VladimirAlexiev> w3c/data-shapes#487

<VladimirAlexiev> https://raw.githack.com/vladimiralexiev/data-shapes/issue-486-ValidationReport-UML/shacl12-core/index.html#validation-report

<VladimirAlexiev> w3c/data-shapes#483

VladimirAlexiev: diagrams help with understanding for readers.
… how to maintain diagrams?

AndyS: tools (for diagrams) outside of w3c control ok?
… dark mode support for respec?

VladimirAlexiev: svg diagrams

VladimirAlexiev: dark mode support for plantuml is there.

AndyS: dark mode needs to be dynamic.

<simonstey> rdf 1.2 has https://www.w3.org/TR/rdf12-concepts/rdf-graph.svg

VladimirAlexiev: we need svg.

<nicholascar> +1 to SVG!

<Robert> +1 for svgs

AndyS: partial diagrams might not help; take up space.

VladimirAlexiev: diagrams most useful for compact syntax.

HolgerK: include diagrams, but off by default.
… button to show diagrams. User can decide if diagrams are shown.

<YoucTagh> https://www.w3.org/TR/dcat-ucr/

<TallTed> I like disclosure triangle or similar. Best if accessible wherever such diagram would be if enabled, so user doesn't have to know about this disclosure option being in the introduction when they're looking at Section 4.5 or whatever.

<nicholascar> SSN has simple/full diagram options: https://www.w3.org/TR/vocab-ssn/#Observations

<simonstey> https://www.w3.org/TR/owl2-primer/

simonstey: volunteers to look into syntax highlighting until next meeting.
… use something that respec already provides.

nicholascar: markdown tools for syntax highlighting; used for turtle.

bergos: focus node highlighted. Active for json-ld.

VladimirAlexiev: only highlighting on shapes graph, not data graph.

<AndyS> Request for next time - status on wide review and CR

<elianaP> AndyS noted!