Merge pull request #80 from openid/adopt-draft-naming

changed draft name and added revision number

.github/workflows/Build-oid4vc-haip-sd-jwt-vc.yml

@@ -1,35 +1,35 @@
-name: draft-oid4vc-haip-sd-jwt-vc document push
+name: openid4vc-high-assurance-interoperability-profile-sd-jwt-vc document push
 on:
   push:
-    branches: [ main ]
-  pull_request:
-    branches: [ main ]
+    paths:
+      - 'openid4vc*.md'
 
 jobs:
-    compile-draft-oid4vc-haip-sd-jwt-vc:
+    compile-openid4vc-high-assurance-interoperability-profile-sd-jwt-vc:
         name: Compile site assets
         runs-on: ubuntu-latest
         steps:
           - uses: actions/checkout@v3
           - name: Run the build process with Docker
-            run: |     
+            run: |  
+                ls
                 docker run \
                 -v /${{ github.workspace }}:/data danielfett/markdown2rfc \
-                draft-oid4vc-haip-sd-jwt-vc.md
+                openid4vc-high-assurance-interoperability-profile-sd-jwt-vc-1_0.md
           - name: rename
             run: |
-                mv ./draft-oid4vc-haip-sd-jwt-vc*.html ./draft-oid4vc-haip-sd-jwt-vc-wg-draft.html
+                mv ./openid4vc-high-assurance-interoperability-profile-sd-jwt-vc*.html ./openid4vc-high-assurance-interoperability-profile-sd-jwt-vc-wg-draft.html
           - uses: actions/upload-artifact@v3
             with:
                 # Artifact name
                 name: output # optional
                 # Destination path
-                path: ./draft-oid4vc-haip-sd-jwt-vc*.html # optional
+                path: ./openid4vc-high-assurance-interoperability-profile-sd-jwt-vc*.html # optional
 
     publish-to-pages:
       name: Publish to GitHub Pages
       if: github.ref == 'refs/heads/main'
-      needs: compile-draft-oid4vc-haip-sd-jwt-vc
+      needs: compile-openid4vc-high-assurance-interoperability-profile-sd-jwt-vc
       runs-on: ubuntu-latest
       permissions:
         pages: write

draft-oid4vc-haip-sd-jwt-vc.md → openid4vc-high-assurance-interoperability-profile-sd-jwt-vc-1_0.md

@@ -1,13 +1,13 @@
 %%%
-title = "OpenID4VC High Assurance Interoperability Profile with SD-JWT VC"
-abbrev = "oid4vc-haip-sd-jwt-vc"
+title = "OpenID4VC High Assurance Interoperability Profile with SD-JWT VC - draft 00"
+abbrev = "openid4vc-high-assurance-interoperability-profile-sd-jwt-vc"
 ipr = "none"
-workgroup = "OpenID Connect"
+workgroup = "Digital Credentials Protocols"
 keyword = ["security", "openid4vc", "sd-jwt", "sd-jwt-vc"]
 
 [seriesInfo]
 name = "Internet-Draft"
-value = "draft-oid4vc-haip-sd-jwt-vc-latest"
+value = "openid4vc-high-assurance-interoperability-profile-sd-jwt-vc-1_0-00"
 status = "standard"
 
 [[author]]
@@ -34,7 +34,6 @@ This document defines a profile of OpenID for Verifiable Credentials in combinat
 
 {mainmatter}
 
-
 # Introduction
 
 This document defines a set of requirements for the existing specifications to enable interoperability among Issuers, Wallets and Verifiers of Credentials where a high level of security and privacy is required. This document is an interoperability profile that can be used by implementations in various contexts, be it a certain industry or a certain regulatory environment.
@@ -488,3 +487,15 @@ Note: When using this profile with other cryptosuites, it is recommended to be e
 # JSON Schema for the supported Presentation Definition properties {#presentation-definition-schema}
 
 <{{schemas/presentation_definition.json}}
+
+# Acknowledgements {#Acknowledgements}
+
+We would like to thank Paul Bastian, Christian Bormann, Mike Jones, Oliver Terbu, Daniel Fett, and Giuseppe De Marco for their valuable feedback and contributions to this specification.
+
+# Notices
+
+Copyright (c) 2023 The OpenID Foundation.
+
+The OpenID Foundation (OIDF) grants to any Contributor, developer, implementer, or other interested party a non-exclusive, royalty free, worldwide copyright license to reproduce, prepare derivative works from, distribute, perform and display, this Implementers Draft or Final Specification solely for the purposes of (i) developing specifications, and (ii) implementing Implementers Drafts and Final Specifications based on such documents, provided that attribution be made to the OIDF as the source of the material, but that such attribution does not indicate an endorsement by the OIDF.
+
+The technology described in this specification was made available from contributions from various sources, including members of the OpenID Foundation and others. Although the OpenID Foundation has taken steps to help ensure that the technology is available for distribution, it takes no position regarding the validity or scope of any intellectual property or other rights that might be claimed to pertain to the implementation or use of the technology described in this specification or the extent to which any license under such rights might or might not be available; neither does it represent that it has made any independent effort to identify any such rights. The OpenID Foundation and the contributors to this specification make no (and hereby expressly disclaim any) warranties (express, implied, or otherwise), including implied warranties of merchantability, non-infringement, fitness for a particular purpose, or title, related to this specification, and the entire risk as to implementing this specification is assumed by the implementer. The OpenID Intellectual Property Rights policy requires contributors to offer a patent promise not to assert certain patent claims against other contributors and against implementers. The OpenID Foundation invites any interested party to bring to its attention any copyrights, patents, patent applications, or other proprietary rights that MAY cover technology that MAY be required to practice this specification.