- From: Arne Hassel <arneh@inrupt.com>
- Date: Wed, 6 Mar 2019 18:52:31 +0100
- To: public-solid@w3.org
- Message-ID: <CA+JxfNmazuG6j_Jx21eiXe7rd4qtT9MO5+F7m8dSqWzpCfM=+A@mail.gmail.com>
Dear all, I have, on the behalf of the team at inrupt, added a rather complex issue to the agenda for tomorrow's meeting: Decisions regarding strict origin handling and implementation of acl:trustedApp <https://www.w3.org/community/solid/wiki/Meetings>. We're sorry to add it this late, we've discovered it last week and have been working hard to work out solutions and proposals that we think are sound to propose to the group. We hope that people who are interested in the issue are able to read up on the issue and its supporting material: * Details on decision point about strict origin checking and acl:trustedApp <https://www.w3.org/community/solid/wiki/Supporting_material:_Details_on_decision_point_about_strict_origin_checking_and_acl:trustedApp#Alternative_solutions> * Applications and access control with strict origin checking <https://www.w3.org/community/solid/wiki/Supporting_material:_Applications_and_access_control_with_strict_origin_checking> I will try to explain the issue tomorrow, but it is rather complex, and cannot guarantee that details won't slip up. Looking forward to a productive meeting tomorrow ^_^ BR, Arne Hassel Senior JavaScript developer at inrupt and Solid Core Contributor
Received on Wednesday, 6 March 2019 17:53:05 UTC