Meeting minutes
Agenda
<kaz> agenda for today
Ege: (goes over today's agenda)
… maybe we should prioritize the agenda on Thing Description, the PRs regarding the 1.1 publication are very important
… anything else?
Koster: We should have the resource questions resolved, and then afterward discuss TPAC, I agree
Minutes Review
<kaz> Sep-20
Ege: I went through the minutes, they look fine, thank you for fixing the remaining issues
… does anyone else have anything to fix?
No comments, minutes are approved
Thing Description 1.1
PR 1844
<kaz> PR 1844 - Update schema to not allow empty op array
Ege: There was a discussion if we should allow the op value be an empty array
… Luca mentioned that in other places an empty array is allowed
… I went through all the array types in TD and there is some inconsistency
… however, some values cannot be fixed, e.g., required, since it is defined this way by JSON Schema
… there was also an discussion with Thomas Jaeckle in the PR
… where he explained that in their software, they are adding something to an empty array in TM and always start with an empty one
… so we cannot mandate that the array should always be non-empty
<cris__> +1
Ege: so based on the discussion, my suggestion would be to only change op for now and then go through all of the other fields again in the next charter and document it for now
… Luca also has agreed to that
… so we can create an issue now and then follow up on the topic later
… the PR itself only changes the JSON Schema by the way
… any comments?
… then I will merge the PR
… (adds a comment and merges the PR)
… (creates an issue to follow up on in the next charter)
PR 1881
<kaz> PR 1881 - TD ontology fix v2
Ege: This is another PR that is only making changes to the ontology
… fixes an issue spotted by Sebastian
… about the base URI
… but he made the changes to the resulting index.html document
… which is why Cristiano applied a proper fix to the ontology
… maybe you can explain Cristiano? As I see the comments are mostly resolved yet
Cristiano: The PR does two things:
… changing AnnotationProperties to DataProperties
… these are changes Mahda and I agreed on in a previous PR
… DatatypeProperty have certain advantages over AnnotationProperties
… my question is now, how to include the schema:rangeIncludes property
… as raised by Mahda
… I did not add it yet since I was not sure
… as it needs to be a URI
Ege: I think profile already includes a URI
… the double anyUri or Array of anyURI is a bit annoying
… for now we cannot change it, though
<kaz> (Ege goes through the Editor's draft: https://
Cristiano: I think I also spotted some other properties that feature this rangeIncludes
… if we don't add them it is not an error, if we add it and it should be wrong, then it would cause problems for others, though
… in the cancellation property, there is a similar problem
… there we also have no rangeIncludes
… would not be the first one that does not include it
… but it is an objectProperty
Cristiano: To address Mahda's comments, we would need to add a rangeIncludes URI, but it is not actually correct, since we have some arrays in some places
(Mahda has joined in the meantime, Cristiano gives a summary of the discussion so far)
Mahra: Why can't we simply put the range as an anyUri?
Cristiano: It is not a URI, though
… however, then we are not modelling the array case
<kaz> Table 3 - Vocabulary Terms in Thing Level
Cristiano: also, a URI is not necessarily a URL
Mahra: I then need to check how to model this if have two types
Cristiano: Can we merge it for now?
Mahra: Sure, syntactically it is fine, but not semantically, since you need both domain and range. We can merge it now and add a Todo to follow up on it later
Ege: (adds a comment to the PR)
Cristiano: The PR also adds the possibility to render the AnnotationProperties correctly by the way
… adding an Annotation Property section
… for the TD I left two Annotation Properties, let's leave them there for now and maybe change them later
Ege: There should be another header in the ontology document as well right?
… (goes through the PR diff and finds it eventually)
Ege: Any objections to merging this?
… I will quickly add a follow-up issue and assign it to Mahda
… (merges the PR, creates the issue)
<kaz> (Mahda leaves)
Resources and Namespaces
<kaz> NAMESPACES.md
Ege: We have the NAMESPACES.md file to describe the current and the desired state regarding namespaces
… for the desired state we will wait until everything has been moved to the wot-resources repository
… in the main call we had a resolution to create the repository for resources
… in the TD repository, we will be using the publication folder tentatively for resources
… the question is which kind of folder structure we want – should we follow the one from the master branch or create a different one?
Cristiano: I don't have a strong preference
Ege: There is the question where the static versions of the files should go
Cristiano: If the WoT resources are static or a vault, we should only have one file
… otherwise there will be confusion
… of course there might be a bit of confusion that the same file is available under two URLs, but we should add some documentation then
Ege: (adds a comment to NAMESPACES.md explaining that some of the same changed files are used for both TD 1.0 and 1.1)
… is anyone opposed to quickly adding this note?
No objections are raised, Ege commits the changes to the main branch
Ege: That means we can merge this PR (1862) now, moving the context and JSON schema file to the publication/rec folder
… any objections to merging the PR?
Kaz: Tentatively, this is fine, but for TD 2.0 we should think about a URL like www.w3.org/ns/wot/ as the base URI without the date and maybe add an alias
Ege: I agree, already looks a bit funny that we are using a URL with an outdated year
… (adds a comment and merges the PR)
<kaz> PR 1863 - Add tentative rec11 resources
Ege: Similar changes are applied for TD 1.1 in PR 1863
… here, we also need to update the schema since we just changed them
Jan: wondering about "1.1" from "td-context-1.1.jsonld"
Ege: that means not WoT Thing Description 1.1 but JSON-LD 1.1.
Jan: maybe there could be a script to check for consistency
Ege: note that the 1.1 in the context file name refers to JSON LD 1.1
Ege: any more comments?
Ege: any objections to merging #1863?
… merged
PR# 1886 REC version preparation
Ege: an errata link is required
Kaz: the errata URL is required for 1.0 also, and links to github issues
Ege: the errata is in the main branch, and doesn't change with version
Kaz: we can use errata11 for example
… this is the basic problem with reusing the repository
Ege: we would need to version the github issues also
Kaz: 1.1 is a minor update so can use the same repository
Kaz: note that https://
… will talk with webmaster
Ege: how do we manage references to other specs?
Kaz: we will preassign URLs and know what they are
… we will know the publication dates
Ege: creating an issue for versioned errata documents
Kaz: probably we should
Ege: we should use the non-versioned file name for the most recent file
… this is the complication with the automatically redirected URLs
… I will look into it after this call
binding templates
vocabulary creation guide PR #298
<kaz> PR 298 - Add additional explanations to vocabulary creation guide
Ege: I have reviewed and it looks good
Cristiano: mjk should review to see if it answers questions
Ege: can we merge #282?
… merge conflict, needs rebase
PR #209 bacnet binding
Ege: is there anything to explain and review?
Koster: no new content until we add the resources files
Ege: a new author is added, should we add to codeowners?
… we will wait until the PR is merged to add the 3rd editor to the codeowners file
Kaz: OK to add the third editor at this time, but need to address the general case of third party contributors ird party contributors
<kaz> (Kaz has sent an invitation to fennibay for joining the wotwg-editors team)
PR #296 - align JSON Schema for Modbus binding
<kaz> PR 296 - Modbus: align the schema with the current ontology
Cristiano: if there are any other misalignments, please let me know
Ege: AOB for today?
… adjourned