Meeting minutes
Organizational
Kaz: Given the participation today, you can continue the discussion on the tooling until 30mins past
… then we can quickly check the progress on ordinary less-problematic topics
Ege: ok. Cristiano will join around 30mins past
(some more discussion about tooling, e.g., LinkML)
Minutes
Ege: looked at them
… didn't see any issues
approved
TD
<Ege> w3c/
Issue 2019
Issue 2019 - Removing errata rendering scripts
Ege: talked about the issue during the main call
… removing the JS code about Errata from the Errata file
PR 2023 - Fixes to Errata Documents
Ege: PR 2023 addressed it and merged
Issue 1753
<Ege> Issue 1753 - Informative text on text direction handling
PR 2026 - Informative steps to implement text direction parsing in Consumers
Ege: PR 2026 handles that issue
Ege: fully compliant to the latest I18n document
merged
PR 2004
PR 2004 - Update project management documentation
Ege: update for the project management document
Ege: now using one single table
… remove obsolete contents
Kaz: kind of big PR
… for today, all the changes look fine
… but for the future, would be better to make smaller PRs one by one :)
Ege: ok
merged
Issue 1972
Issue 1972 - unwanted any type for title
related PR 1684 - Fix shacl, context and ontology
Cristiano: old PR 1684, which has been merged, is causing a problem now
Ege shows the discussion in 2022 from PR 1684
Cristiano: that's still a possible workaround
Mahda: but that causes a problem now
Cristiano: we should think about nicer solution
… less-restrict with the SHACL validation
Ege: the correct solution would be modelling human-readable rdf:langString
Luca: annoying problem here is most of them have specific items
… need to specify information based on a default language
Ege: human-readable strings should be "rdf:langString"
… all other strings should be "xsd:string"
… the default language of the TD in @language should be only applied to "rdf:langString"
Kaz: maybe a good topic for joint discussion with the other WGs
… e.g., i18n, VC/DID, RDF, JSON-LD
Ege: not an issue about pure RDF, but might be useful
Kaz: specifically about RDF-based W3C spec
Cristiano: JSON-LD converter has the issue
Mahda: current workaround doesn't work due to the current tooling
Ege: what do you mean by "JSON-LD converter"?
Mahda: the mechanism being used within playground
… don't remember the detail at the moment, though
Cristiano: need to be addressed in JSON-lD
Kaz: yeah
… that's why I mentioned JSON-LD as one of the targets for joint discussion
Mahda: yeah
<cris> json-ldapi Issue 545 - compacting native types with a type specification in context
Cristiano: there is a GitHub Issue on json-ld-api repo
Ege: (record that issue as a related issue)
… maybe we can wait until TPAC since this is not critical at the moment
… but need to solve it before the next publication
Issue 2025
Issue 2025 - Extending the initial/reusable connection examples
Ege: not time today but need to discuss it
[adjourned]