← Prev in month
← Prev in thread
Starter Documents for SAML Version 2.1
Per the TC's submission requests [1], please find the attached ZIP file containing nine (9) starter documents plus a description of the overall structure for: OASIS Security Assertion Markup Language (SAML) Version 2.1 This is designed as a multi-part Work Product, with the following individual Work Product abbreviations: part1-overview part2-core part3-bindings part4-profiles part5-metadata part6-authn-context part7-sec-consider part8-conformance part9-glossary We expect this Work Product to be published at the following URIs: http://docs.oasis-open.org/security/saml/v2.1/csd01/part1-overview/saml-v2.1-csd01-part1-overview.html http://docs.oasis-open.org/security/saml/v2.1/csd01/part2-core/saml-v2.1-csd01-part2-core.html http://docs.oasis-open.org/security/saml/v2.1/csd01/part3-bindings/saml-v2.1-csd01-part3-bindings.html http://docs.oasis-open.org/security/saml/v2.1/csd01/part4-profiles/saml-v2.1-csd01-part4-profiles.html http://docs.oasis-open.org/security/saml/v2.1/csd01/part5-metadata/saml-v2.1-csd01-part5-metadata.html http://docs.oasis-open.org/security/saml/v2.1/csd01/part6-authn-context/saml-v2.1-csd01-part6-authn-context.html http://docs.oasis-open.org/security/saml/v2.1/csd01/part7-sec-consider/saml-v2.1-csd01-part7-sec-consider.html http://docs.oasis-open.org/security/saml/v2.1/csd01/part8-conformance/saml-v2.1-csd01-part8-conformance.html http://docs.oasis-open.org/security/saml/v2.1/csd01/part9-glossary/saml-v2.1-csd01-part9-glossary.html NOTE: These starter documents are all delivered with a common body, although for a multi-part Work Product not all Section headings will be needed in each Part. In particular, the Acknowledgments Appendix only need appear in the "Overview" Part, and the Conformance Section will likely be consolidated in the "Conformance" Part. Please let me know if you have any questions about this. Please let me know if anything here fails to meet your expectations. Further revisions to this Work Product must be maintained in Working Drafts, following procedures detailed in the OASIS TC Administration How-to Guide [2]. Working Drafts should be made available by uploading the document(s) to the TC's Kavi document repository, or (provisionally/temporarily) to the TC's Subversion (SVN) repository, if SVN has been activated for your TC [3]. TCs are encouraged to use ZIP packaging when the WD releases contain multiple files (and directories). One key requirement for a multi-part Work Product is that “the Work Product as a whole must be approved by a single Work Product Ballot”.[4] This means in particular that the TC must include all parts (preferably within a single ZIP file) for each approval/publication event, even if some parts may remain unchanged from the previous publication. For each WD revision, you will need to: 1) increment the Working Draft revision (number) from 01 to 02, 03, 04 etc., as successive Working Drafts are produced; the revision number needs to be updated at the top of the document in the stage identifier (Working Draft ##) and in the document identifier within the page footer. 2) supply the relevant publication/release/upload date for each successive Working Draft instance, using the prescribed date format: DD Month YYYY; the date needs to be updated at the top of the document (just below the stage identifier, Working Draft ##) and in the page footer. 3) provide suitable text for a document Abstract, updating this summary with successive revisions to provide an accurate description of the subject matter, goals, scope, etc. 4) keep the Acknowledgments (Appendix A) and Revision History (Appendix C) up-to-date with each WD revision. 5) consult the OASIS Naming Directives document when creating new artifacts that may be part of the Work Product (e.g., image files, XML schemas), observing the rules for name characters in files and proposed directories, and for proposed URIs/namespaces [5]. When the TC votes [6] to approve a Working Draft as a Committee Draft (CSD or CND), the Chair or other designated person must submit a "Committee Specification Draft Creation and Upload Request" accessible on the TC Administration Requests Page [7]. Upon receipt of this form, the TC Administrator will QC and process the Work Product for official publication in the OASIS Library (http://docs.oasis-open.org/) as a Committee Draft, including addition of the requisite cover page metadata and other boilerplate information. =========== References: [1] Requests were submitted as individual tickets for each part: https://tools.oasis-open.org/issues/browse/TCADMIN-1041 https://tools.oasis-open.org/issues/browse/TCADMIN-1042 https://tools.oasis-open.org/issues/browse/TCADMIN-1043 https://tools.oasis-open.org/issues/browse/TCADMIN-1044 https://tools.oasis-open.org/issues/browse/TCADMIN-1045 https://tools.oasis-open.org/issues/browse/TCADMIN-1046 https://tools.oasis-open.org/issues/browse/TCADMIN-1047 https://tools.oasis-open.org/issues/browse/TCADMIN-1048 [2] Developing Committee Specifications and Notes https://www.oasis-open.org/resources/tcadmin/developing-committee-specifications-and-notes Starting a Working Draft https://www.oasis-open.org/resources/tcadmin/starting-a-working-draft [3] SVN Version control, via Tools https://tools.oasis-open.org/ [4] https://www.oasis-open.org/policies-guidelines/tc-process#specQuality [5] OASIS Naming Directives http://docs.oasis-open.org/specGuidelines/ndr/namingDirectives.html [6] Approval of a WD as a CD (CSD or CND) https://www.oasis-open.org/resources/tcadmin/approving-a-committee-specification-or-note-draft https://www.oasis-open.org/policies-guidelines/tc-process#committeeDraft [7] TC Administration Requests Page, see Committee Specification Draft Creation / Upload Request https://www.oasis-open.org/resources/tc-admin-requests Best wishes, Paul -- Paul Knight - Tel: +1 781-861-1013 OASIS - Advancing open standards for the information society Document Process Analyst Attachment: saml-v2.1-wd01.zip Description: Zip archive
← Prev in month
← Prev in thread