Meeting minutes
Review minutes
McCool: last time discussed JSONPath and XPath
McCool: didn't come to a final conclusion about XPath
no objections to publishing
Issues and PRs
McCool: terminology and use case cleanup in discovery
McCool: in Profiles, they intend to make self-describing mandatory with well-known URLs. It is just for HTTP
Farshid: Ben has some concerns about the limitation in use of well-known URLs in a system which exposes multiple TDs
McCool: we need to look into the spec to see if it prevent the use of base paths
McCool: one problem is that well-known path should be sufficient to find the final endpoint given the IP or hostname. So basepath is not useful.
… we could consider returning an array if multiple TDs are involved.
… we could end up with scalability issues if there are many TDs
XPath
https://
McCool: documenting the discussion on issue...
… https://
Moving terms to Architecture
https://
Toumura: Only Enriched TD is left
McCool: Any reason why Enriched TD is not moved as well?
… we can move that as well and leave no discovery terms in this spec
Toumura: will update the PR to move Enriched TD as well
Farshid: I've added a comment on the PR on arch-side about the open issue about discoverer term
McCool: Let's proceed with the PRs and we can discuss the term afterwards.
XPath
David: Concerned that JSONPath is not as powerful as XPath
TD/Thing ID
McCool: concern from the TD side about the use of TD.id as the identifier of TDs in discovery
PR242 (Add placeholder section for thing model)
https://
Farshid: adding the section with editorial note only
merged
Issue 219 (Define role of "Discoverer/Registerer")
https://
McCool: https://
… to check the term definition
<kaz> [adjourned]