Raw Minutes Chat for meeting #219 on 2018-11-05

["Mr. Stefan Hagen" <stefan@hagen.link>]

[16:51] andreas: Hinb Ernst Jan^, could you edit the members of Skype group 'DSS-X'? There are eight members !
[17:05] andreas: 1. Welcome by the Co-Chair (Andreas Kuehne)

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 #218 on 2018-10-22:
URL = https://www.oasis-open.org/committees/download.php/64133/chat_trace_dss-meeting-20181022-218.txt

6. DSS Core 2.0 Status of CSD02 

6.1 Github repo for specification work towards CSD02 and onwards

URL = https://github.com/oasis-tcs/dss-x-spec

6.1.1 Pull Requests

6.1.1.1 Initial commit of starting material from CSPRD01 #1

URL = https://github.com/oasis-tcs/dss-x-spec/pull/1

6.2 Public comments received for PRCSD01

1 "comment" was already considered and its resolution is ongoing (SwaggerHub).

20 comment representing issues are accessible via above filter link for the members of the TC:
https://issues.oasis-open.org/browse/DSSX-25?filter=14977

Additional list of comments on public comment list from Juan Carlos Cruellas:

URL = https://lists.oasis-open.org/archives/dss-x-comment/201811/msg00001.html

Status of issue resolution, CSD02 WD01 preparation and pipeline of filters specification (implementation and documentation)

7. Profiles

8. Next meeting

Suggested to meet again on 2018-NOV-19  (usual bi-weekly schedule again)
Note: Starting one hour earlier at 17:00 local time in Central Europe

9. AOB
[17:09] andreas: Ernst Jan
[17:09] andreas: Detlef
[17:09] andreas: Andreas present
[17:09] andreas: Stafan arraioves late.
[17:10] Stefan Hagen: Stefan there
[17:10] andreas: agebnda approved
[17:10] Stefan Hagen: Agenda approved
[17:10] andreas: minutes approved
[17:10] Stefan Hagen: Minutes approved unchanged  as published
[17:12] Stefan Hagen: 6.1.1.1
[17:12] Stefan Hagen: https://github.com/oasis-tcs/dss-x-spec/pull/1/commits/ea0406fd928435358bdeb2a11e93ac85ef8c3dc5
[17:13] Stefan Hagen: Discussion on files (are present in pull request but not merged)
[17:14] Stefan Hagen: All are ok with merging the pull request into the repo
[17:14] Stefan Hagen: Stefan moved, Ernst-Jan second
[17:14] Stefan Hagen: No objections, no further discussion, unanimous consent, motion carries
[17:15] Stefan Hagen: 6.2 Public comments received for PRCSD01
[17:15] Stefan Hagen: Andreas startet work on tickets related to schema files and left open the specification (prose) related issues for later
[17:15] Stefan Hagen: Stefan likes this
[17:17] Stefan Hagen: We should ensure all interested parties receive comments mails
[17:17] Stefan Hagen: https://lists.oasis-open.org/archives/dss-x-comment/201811/msg00001.html
[17:17] Stefan Hagen: Juan Carlos message (on my reply on his message)
[17:19] Stefan Hagen: AS a workaround probably look if a "month" folder shows up at https://lists.oasis-open.org/archives/dss-x-comment/ ..
[17:19] Stefan Hagen: Returning to 6.1.1.1
[17:19] Stefan Hagen: So, minimal suggested snippet:
[17:19] Stefan Hagen: https://github.com/oasis-tcs/dss-x-spec/pull/1/commits/ea0406fd928435358bdeb2a11e93ac85ef8c3dc5#diff-7a497badcd14db073972492c2ac26c5c
[17:20] Stefan Hagen: editor_revisions/workflow_prose/4-1-1-NsPrefixMapping_prose-snippet.md
[17:21] Stefan Hagen: Action on Stefan completed, to per sample, extract one of those pesky section 4 triplets of generic+JSON+XML verses where the schema file has to be matched and inserted
[17:21] Stefan Hagen: 4.1.1 Component NsPrefixMapping

The NsPrefixMapping component defines the mapping of namespace URIs to namespace prefixes. This is required to evaluate XPath expression when using transport syntaxes that dont support namespace.

Below follows a list of the sub-components that MAY be present within this component:

 The NamespaceURI element SHALL contain one instance of a URI.  [DSS-4.1.1-1].

 The NamespacePrefix element SHALL contain one instance of a string.  [DSS-4.1.1-2].

4.1.1.1 NsPrefixMapping  JSON Syntax

 The NsPrefixMappingType JSON object SHALL implement in JSON syntax the requirements defined in the NsPrefixMapping component.  [JDSS-4.1.1.1-1].

 Properties of the JSON object SHALL implement the sub-components of NsPrefixMapping using JSON-specific names mapped as shown in the table below.

|| Element || Implementing JSON member name || | NamespaceURI | uri | | NamespacePrefix | pre |

 [JDSS-4.1.1.1-2]. The NsPrefixMappingType JSON object is defined in the JSON schema [DSBJSON] and is provided below as a service to the reader.

$INSERT_JSON("dsb-NsPrefixMappingType")NOSJ_TRESNI$
4.1.1.2 NsPrefixMapping  XML Syntax

 The XML type NsPrefixMappingType SHALL implement the requirements defined in the NsPrefixMapping component.  [XDSS-4.1.1.2-1].

The NsPrefixMappingType XML element is defined in XML Schema [DSBXSD] and is provided below as a service to the reader.

$INSERT_XML("NsPrefixMappingType")LMX_TRESNI$
 Each child element of NsPrefixMappingType XML element SHALL implement in XML syntax the sub-component that has a name equal to its local name.  [XDSS-4.1.1.2-2].
[17:21] Stefan Hagen: <<< content of file
[17:21] Stefan Hagen: Inserted monkey patching marks $INSERT_JSON("dsb-NsPrefixMappingType")NOSJ_TRESNI$ and $INSERT_XML("NsPrefixMappingType")LMX_TRESNI$
[17:22] Stefan Hagen: Another low level offering, to maintain the sectioning on prose level thus the filename has the generic term and the section number:
[17:22] Stefan Hagen: 4-1-1-NsPrefixMapping_prose-snippet.md
[17:25] Stefan Hagen: Andreas currently the schema XML drives the process of mixing in
[17:25] Stefan Hagen: Stefan will take a look
[17:26] Stefan Hagen: Action on Stefan to (a) provide the missing snippets and (b) come up with working code to mix it in (ideally again based on XML schema ordering)
[17:27] Stefan Hagen: 7. Profiles
[17:27] Stefan Hagen: Detlef did not find enough time to work on local remote profile
[17:28] Stefan Hagen: Detlef wrote of a paper what needs to be changed in there
[17:29] Stefan Hagen: Detlef will make some small fixes to the paper and then inform the rest of the TC
[17:30] Stefan Hagen: Andreas has completed his part on writing a paper on changes of DSS in version 2.0 for the open identity summit
[17:31] Stefan Hagen: All discuss status of working drafts papers versus specifications
[17:31] Stefan Hagen: Ernst-Jan: Open access when published (the papers in discussion)?
[17:34] Stefan Hagen: Detlef wonders if aedes profiles is publicly available committee draft or so ?
[17:35] Stefan Hagen: Andreas uploaded in July 2018 the latest version to kavi
[17:35] andreas: https://www.oasis-open.org/apps/org/workgroup/dss-x/download.php/63412/oasis-dssx-2.0-profiles-ades%20WD%2003.zip
[17:35] Stefan Hagen: Detlef asked for a referenceble intermediate version
[17:35] Stefan Hagen: @Andreas Thank you
[17:38] Stefan Hagen: All discuss when and how to progress with the profile (pending core v2 stabilisation)
[17:39] Stefan Hagen: Andreas kindly requests an action on him to compare the profile against core schema v2 and signal that everything is fine with next core
[17:41] Stefan Hagen: All discuss liaison with STS
[17:42] Stefan Hagen: No more news on profiles
[17:42] Stefan Hagen: 8. Next meeting

Suggested to meet again on 2018-NOV-19  (usual bi-weekly schedule again)
Note: Starting one hour earlier at 17:00 local time in Central Europe

9. AOB
[17:43] Stefan Hagen: All agree
[17:43] Stefan Hagen: Any AOB?
[17:44] Stefan Hagen: Andreas presented DSS and OASIS during an ENISA meeting (mainly Cloud signature Consortium members present)
[17:51] Stefan Hagen: From the consortium website: The Plan (section) states """
[17:51] Stefan Hagen: End of 2015: kick-off
Adobe promotes an industrial cooperation initiative on the development of common technical specifications for Cloud Signature.
June 28th, 2016: launch
As eIDAS rules enter into force on July 1st, 2016, the Cloud Signature Consortium publicly announces its mission and starts its activity.
February 2017: release
Specifications to standardize the three-corner model between solution, technology and service providers will be released.
2017: implementation
During 2017, Consortium Members release their Cloud Signature services based on the technical specifications.
[17:51] Stefan Hagen: """
[17:51] Stefan Hagen: So the published plan is outdated
[17:53] Stefan Hagen: Ernst Jan: Interest in smart card might vary locally: Germany, Estonia etc quite high distribution of smart card based IDs but elsewhere like in Netherlands might not make much sense commercially to pick up the DSS local signature profle
[17:53] Stefan Hagen: All discuss
[17:58] Stefan Hagen: Detlef and Andreas suggest to track future possible plug tests STF 539 or STF 524
[17:58] Stefan Hagen: Andreas suggests to also add a minimal adaptive profile to map some names to other names and the profile is ready
[17:59] Stefan Hagen: Ernst Jan suggests interoperability issue in a separate topic later (future meetings)
[17:59] Stefan Hagen: All agree
[18:01] Stefan Hagen: Meeting adjourned