OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.

 


Help: OASIS Mailing Lists Help | MarkMail Help

dss-x message

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]


Subject: Raw Minutes Chat for meeting #210 on 2018-05-28


[18:01] Room information was updated by: Stefan Hagen
DSS-X Conference Call #210 (Conference Call)
Monday, 28 May 2018, 04:00pm to 05:00pm UTC

Agenda Draft:
1. Welcome by the chair (Stefan Hagen)

2. Minutes taker
All write into the chat, Stefan assembles and uploads into document area.

3. Roll call

4. Approval of the agenda

5. Approval of minutes from previous calls
5.1 Minutes from call #209 on 2018-05-14:
URL = https://www.oasis-open.org/committees/download.php/63086/chat_trace_dss-meeting-20180514-209.txt

6. Roadmap for 2018
6.1 Milestone DSS 2.0 Core/Base/MVP CSD01/CS01 stage
6.2 Milestone DSS 2.0 Popular Profiles CSD01 stage
6.3 Milestone DSS 2.0 other normative stages
6.4 Milestone DSS 2.0 supportive but supplementary non-normative materials

7. Core 2.0 issues discussion
7.1 Maintenance tasks

7.2 Topology of schemas - structure and relation

7.3 Editorial topics

7.4 Possible motion to progress core to CSD01 and request public review

8. Profiles

9. Next meeting
Suggested to meet again on 2018-JUN-11  (usual bi-weekly schedule)

10. AOB
[18:03] Stefan Hagen: Voting Members: 3 of 4 (75%) (used for quorum calculation)
[18:03] Stefan Hagen: 1. Welcome by the chair (Stefan Hagen)
[18:04] Stefan Hagen: 2. Minutes taker
All write into the chat, Stefan assembles and uploads into document area.
[18:04] Stefan Hagen: 3. Roll call
[18:04] Stefan Hagen: Andreas, Ernst-Jan, and Stefan -> Quorate
[18:04] Stefan Hagen: 4. Approval of the agenda
[18:05] Stefan Hagen: Discuss JSON object key names
[18:06] Stefan Hagen: Agenda approved as amended
[18:06] Stefan Hagen: 5. Approval of minutes from previous calls
5.1 Minutes from call #209 on 2018-05-14:
URL = https://www.oasis-open.org/committees/download.php/63086/chat_trace_dss-meeting-20180514-209.txt
[18:06] Stefan Hagen: Minutes approved unchanged as published
[18:07] Stefan Hagen: 6. Roadmap for 2018
6.1 Milestone DSS 2.0 Core/Base/MVP CSD01/CS01 stage
6.2 Milestone DSS 2.0 Popular Profiles CSD01 stage
6.3 Milestone DSS 2.0 other normative stages
6.4 Milestone DSS 2.0 supportive but supplementary non-normative materials
[18:09] Stefan Hagen: Stefan answered a mail from Juan Carlos / ETSI to allow for optimal synchronisation or publication and reference stages - not much more than ready when it is in essence, due to a) long periods enforced by TC process (comment and ballot) and b) already ongoing commenting and requesting from ETSI committee members / profile writers; Should not be a clever idea, to skip these to win time, because changes after CS01  or CSD01 that are substantial (or material how OASIS names it) are a bad deal
[18:11] Stefan Hagen: During the day a request from ETSI came for a meeting to even better synchronize
[18:14] Stefan Hagen: 7. Core 2.0 issues discussion
7.1 Maintenance tasks
[18:15] Stefan Hagen: SignatureActivationDate discussion on list - new profile or leave where it is - Andreas suggests to drop it from core and push to signing related profile
[18:16] Stefan Hagen: EJvN mentions that this element is the essence of remote signing because it has to include the private key (as reference)
[18:16] Stefan Hagen: Andreas explains that the request is more centred on many endpoint variations
[18:16] Stefan Hagen: EJvN assumes similar to local signature profile
[18:17] Stefan Hagen: All think the use case is very complex and might bloat the core and would be hard to tell if just one SAD would be enough
[18:18] Stefan Hagen: 7.2 Topology of schemas - structure and relation
[18:19] Stefan Hagen: Key naming request from STF on verification by Juan Carlos (relayed) seems to be a problem of some implementers that claim to have problems with the non identical key names (when compared to XML)
[18:20] Stefan Hagen: Andreas assumed it makes sense to more align with JWT etc. to enhance match with the JSON world with the JSON dialect and not enforce mapping on every implementer and then miss the homogenising influence a specification should have
[18:23] Stefan Hagen: EJvN: Structure not exactly 1 to 1 between XML and JSON, then offering identical names MAY be misleading as it suggests complete 1 to 1 availability - least surprise principle
[18:25] Stefan Hagen: All agree to further use the JSON adapted shorter key names
[18:26] Stefan Hagen: Andreas will pull in addition feedback from JSON developers in the field
[18:27] Stefan Hagen: 7.3 Editorial topics
[18:27] Stefan Hagen: Andreas suggests the current revision (dropped SADness) is the candidate, all should show some love
[18:28] Stefan Hagen: All promise to review and give instant feedback so we can move during next or next to next meeting
[18:32] Stefan Hagen: 7.4 Possible motion to progress core to CSD01 and request public review
[18:32] Stefan Hagen: Postponed to next meeting
[18:32] Stefan Hagen: 8. Profiles
[18:32] Stefan Hagen: No news from EJvN and no feedback on EJvN's comments
[18:33] Stefan Hagen: All think next meeting will be feedback and discussion
[18:33] Stefan Hagen: Andreas: Current state of our ADES profile he forward to the relevant woringgroup in ETSI but no response received so far
[18:33] Stefan Hagen: 9. Next meeting
Suggested to meet again on 2018-JUN-11  (usual bi-weekly schedule)
[18:34] Stefan Hagen: Works for everyone
[18:34] Stefan Hagen: 10. AOB
[18:34] Stefan Hagen: None
[18:34] Stefan Hagen: Meeting adjourned


[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]