Meeting minutes
Agenda bashing
<FarshidT> Hosting contexts under w3.org: https://
https://
Resolution on April 28th
Prev minutes
<kaz> Apr-12
Minutes from last week - Ben Francis needed for Security
Wrt object security
McCool: Registration ID meant as local ID
Minutes approved
WD publication
<kaz> Issue 154 - Publish updated WD
glomb Two groups of comments: Editorial wrt http, non-editorial wrt server-side information
McCool Submit PR for it
McCool Would add implication for implementors
Farshid Server-side content negotiation still possible
Farshid: What is the use case for pagination in body?
McCool - Has advantages for object security.
McCool - Could you tweak headers?
Farshid: Will not have REST API more SOAP like.
McCool: In the header consisting w/ REST
Christian: Developers not using it.
Christian: How does "wire format" impair RDF processing?
Andrea: JSON-LD a way to express RDF
Cannot translate mixed payloads.
Mixing formats.
McCool: What about having JSON-LD envelope?
Farshid: What was the problem with having "outside" context?
Christian: Should present "envelope" based pagination.
See comments in issue
Andrea: JSON envelope was changed since it was incorrect.
Farshid already provided a summary on pagination discussion.
https://
McCool Comments
Spec. is http centric. New issue:
PR 152
https://
Farshid: Found a way identifying anonymous TDs (6.2.1.1, 6.2.1.2)
McCool Breaks canonicalization and signing
Farshid: Must "un-enrich"
To be described
Enrichment needed for anon. TDs otherwise not
McCool Should also be discussed in WoT-Security wrt UUID
Farshid will create issue about this.
PR 153
https://
Header based pagination
McCool JSONpath queries instead of envelope based pagination
Header based pagination -> optional
According to RFC8288
Not identical to LDP paging
McCool Merged for future proposal, only optional
PR 155
https://
Events API
Section Notification
McCool: Merge it to have a foundation for further discussions.
"Anon." identifier sent along