Changes 1

.github/ISSUE_TEMPLATE/standard_change_request.md

@@ -0,0 +1,52 @@
+---
+name: "Standard Change Request"
+about: "Propose a change or addition to the DCI standard"
+title: "[Change Request] Short Description"
+labels: ["change request", "triage"]
+assignees: ""
+---
+
+### Summary
+
+A short summary of the proposed change.
+
+---
+
+### Affected Module(s)
+
+- [ ] Core Standard
+- [ ] Disability Registry
+- [ ] Farmer Registry
+- [ ] CRVS
+- [ ] Social Registry
+- [ ] Employment System
+- [ ] ID System
+- [ ] Early Warning System
+
+---
+
+### Description
+
+Clearly describe the issue or enhancement. Why is the change needed? What problem H7does it solve?
+
+---
+
+### Proposed Change
+
+Provide the exact changes you're proposing to the standard.
+
+---
+
+### Impact
+
+- [ ] Backward compatible
+- [ ] Requires version bump
+- [ ] Affects existing integrations
+
+Explain the impact on systems already using the current standard.
+
+---
+
+### Additional Context
+
+Add any references, links, or diagrams that help understand the request.C7

.gitignore

@@ -37,6 +37,7 @@ proguard/
 captures/
 
 # IntelliJ
+.idea
 *.iml
 .idea/workspace.xml
 .idea/codeStyles/Project.xml

README.md

@@ -1,18 +1,17 @@
 # API documentation
 
 The APIs are accessible through
-    1. DCI:  [standards](https://spdci.github.io/standards/release/index.html)
-    2. G2P Community: [specifications](https://g2p-connect.github.io/specs/release/index.html)
+    1. DCI:  [standards](https://standards.spdci.org/standards)
 
 ## Discussion forum 
 
 To initiate any discussion please visit [discussion page](https://github.com/orgs/spdci/discussions).
 
 **IMPORTANT NOTES:**
 1. Final release for consuming these APIs (yaml, html) are available in specs/release folder.
-2. Contribute to G2P Connect specification or DCI standards APIs through pull requests in  respective specs/src folder.
+2. Contribute to  DCI standards APIs through pull requests in  respective specs/src folder.
 3. specs/release folder files are auto generated and it's NOT recommended to edit these directly. 
-4. specs/release filder API files are for final consumption by solution providers to make their services compatible with G2P Connect / DCI standards.
+4. specs/release filder API files are for final consumption by solution providers to make their services compatible with  DCI standards.
 
 ### Reference Links
 1. Build [Instructions](./build/build_instructions.md)
@@ -36,29 +35,27 @@ To initiate any discussion please visit [discussion page](https://github.com/org
             ├── security
         ├── extensions
             ├── dci
-            ├── openId
-            ├── fhir
-            ├── cdpi
+            ├── dr
+            ├── fr
+            ├── ibr
+            ├── social
         ├── registry
             ├── schema
-                ├── core
-                ├── civil
-                ├── farmer
-                ├── disability
+                ├── dr
+                ├── fr
+                ├── ibr
+                ├── schema
+                ├── social
             ├── registry_core_api_v1.0.0.yaml
-            ├── registry_civil_api_v1.0.0.yaml
-            ├── registry_nid_api_v1.0.0.yaml
-            ├── registry_farmer_api_v1.0.0.yaml
-            ├── registry_disability_api_v1.0.0.yaml  
+            ├── social_api_v1.0.0.yaml
+            ├── dr_api_v1.0.0.yaml
+            ├── fr_api_v1.0.0.yaml
+            ├── ibr_api_v1.0.0.yaml  
         ├── mapper
             ├── schema
                 ├── core
                 ├── fa
-            ├── mapper_core_api_v1.0.0.yaml
-        ├── disbure
-            ├── schema
-                ├── core
-            ├── disburse_core_api_v1.0.0.yaml
+
 
 ## Change request 
 

build/build_apis.cmd

@@ -1,13 +1,32 @@
-# This file auto generates all g2p connect yaml files.
-# Assumes the command is run from the root folder i.e ./specs
+# This file auto generates all yaml files.
+# Assumes the command is run from the root folder i.e ./standards
 # For each new category, please make sure to add a reference link in this file for easy auto generation of yamls.
 
+# build auth APIs
 swagger-cli -f 2 -t yaml bundle ./src/authz/authz_core_api_v1.0.0.yaml -o ./release/yaml/authz_core_api_v1.0.0.yaml
-swagger-cli -f 2 -t yaml bundle ./src/registry/registry_core_api_v1.0.0.yaml -o ./release/yaml/registry_core_api_v1.0.0.yaml
-swagger-cli -f 2 -t yaml bundle ./src/mapper/mapper_core_api_v1.0.0.yaml -o ./release/yaml/mapper_core_api_v1.0.0.yaml
-swagger-cli -f 2 -t yaml bundle ./src/disburse/disburse_core_api_v1.0.0.yaml -o ./release/yaml/disburse_core_api_v1.0.0.yaml
-
 redocly build-docs ./release/yaml/authz_core_api_v1.0.0.yaml  -o ./release/html/authz_core_api_v1.0.0.html
+
+# build APIs
+swagger-cli -f 2 -t yaml bundle ./src/registry/registry_core_api_v1.0.0.yaml -o ./release/yaml/registry_core_api_v1.0.0.yaml
 redocly build-docs ./release/yaml/registry_core_api_v1.0.0.yaml  -o ./release/html/registry_core_api_v1.0.0.html
-redocly build-docs ./release/yaml/mapper_core_api_v1.0.0.yaml  -o ./release/html/mapper_core_api_v1.0.0.html
-redocly build-docs ./release/yaml/disburse_core_api_v1.0.0.yaml  -o ./release/html/disburse_core_api_v1.0.0.html
+
+swagger-cli -f 2 -t yaml bundle ./src/registry/ibr_api_v1.0.0.yaml -o ./release/yaml/ibr_api_v1.0.0.yaml
+redocly build-docs ./release/yaml/ibr_api_v1.0.0.yaml  -o ./release/html/ibr_api_v1.0.0.html
+
+swagger-cli -f 2 -t yaml bundle ./src/registry/social_api_v1.0.0.yaml -o ./release/yaml/social_api_v1.0.0.yaml
+redocly build-docs ./release/yaml/social_api_v1.0.0.yaml  -o ./release/html/social_api_v1.0.0.html
+
+
+# build locations APIs
+swagger-cli -f 2 -t yaml bundle ./src/locations/locations_core_api_v1.0.0.yaml -o ./release/yaml/locations_core_api_v1.0.0.yaml
+redocly build-docs ./release/yaml/locations_core_api_v1.0.0.yaml -o ./release/html/locations_core_api_v1.0.0.html
+
+# build jwks APIs
+swagger-cli -f 2 -t yaml bundle ./src/jwks/jwks_core_api_v1.0.0.yaml -o ./release/yaml/jwks_core_api_v1.0.0.yaml
+redocly build-docs ./release/yaml/jwks_core_api_v1.0.0.yaml  -o ./release/html/jwks_core_api_v1.0.0.html
+
+
+# swagger-cli -f 2 -t yaml bundle ./src/mapper/mapper_core_api_v1.0.0.yaml -o ./release/yaml/mapper_core_api_v1.0.0.yaml
+# swagger-cli -f 2 -t yaml bundle ./src/disburse/disburse_core_api_v1.0.0.yaml -o ./release/yaml/disburse_core_api_v1.0.0.yaml
+# redocly build-docs ./release/yaml/mapper_core_api_v1.0.0.yaml  -o ./release/html/mapper_core_api_v1.0.0.html
+# redocly build-docs ./release/yaml/disburse_core_api_v1.0.0.yaml  -o ./release/html/disburse_core_api_v1.0.0.html

build/build_instructions.md

@@ -66,3 +66,11 @@ bundled successfully in: ./release/html/registry_core_api_v1.0.0.html
 ```
 
 6. Commit the changes and push the updated code to git repo. Create pull requests for teams to collaborate and merge to main branch!
+
+## How this published on website 
+
+The github actions used to publish this as website, you can map branch / folder which to be published as webpages root path.
+
+Below link will help to understand how it works
+
+https://docs.github.com/en/pages/getting-started-with-github-pages/creating-a-github-pages-site

changelog.md

@@ -0,0 +1,26 @@
+# DCI Standards – Changelog
+
+All notable changes to this project are documented in this file.  
+This project follows [semantic versioning](https://semver.org/).
+
+# Release Notes
+
+## [1.0.0] – 2025-09-19
+
+### Decision Summary
+- 
+- 
+-
+
+---
+
+### Changes
+
+| Type            | Field / Item                  | Description                   | Ref / Notes |
+|---------------  |-------------------------------|------------------------------ |-------------|
+|  🟢 **Added**   |-------------------------------|------------------------------ |-------------|
+| 🔴 **Breaking** |-------------------------------|------------------------------ |-------------|
+| ❌ **Removed**  |-------------------------------|------------------------------ |-------------|
+| 🟡 **Updated**  |-------------------------------|------------------------------ |-------------|
+
+

errors.json

@@ -0,0 +1,175 @@
+{
+  "totals": {
+    "errors": 11,
+    "warnings": 0,
+    "ignored": 0
+  },
+  "version": "1.16.0",
+  "problems": [
+    {
+      "ruleId": "security-defined",
+      "severity": "error",
+      "message": "There is no `Authorization` security scheme defined.",
+      "location": [
+        {
+          "source": {
+            "ref": "src/registry/crvs_api_v1.0.0.yaml"
+          },
+          "pointer": "#/paths/~1registry~1search/post/security/0/Authorization",
+          "reportOnKey": true
+        }
+      ],
+      "suggest": []
+    },
+    {
+      "ruleId": "security-defined",
+      "severity": "error",
+      "message": "There is no `Authorization` security scheme defined.",
+      "location": [
+        {
+          "source": {
+            "ref": "src/registry/crvs_api_v1.0.0.yaml"
+          },
+          "pointer": "#/paths/~1registry~1on-search/post/security/0/Authorization",
+          "reportOnKey": true
+        }
+      ],
+      "suggest": []
+    },
+    {
+      "ruleId": "security-defined",
+      "severity": "error",
+      "message": "There is no `Authorization` security scheme defined.",
+      "location": [
+        {
+          "source": {
+            "ref": "src/registry/crvs_api_v1.0.0.yaml"
+          },
+          "pointer": "#/paths/~1registry~1subscribe/post/security/0/Authorization",
+          "reportOnKey": true
+        }
+      ],
+      "suggest": []
+    },
+    {
+      "ruleId": "security-defined",
+      "severity": "error",
+      "message": "There is no `Authorization` security scheme defined.",
+      "location": [
+        {
+          "source": {
+            "ref": "src/registry/crvs_api_v1.0.0.yaml"
+          },
+          "pointer": "#/paths/~1registry~1on-subscribe/post/security/0/Authorization",
+          "reportOnKey": true
+        }
+      ],
+      "suggest": []
+    },
+    {
+      "ruleId": "security-defined",
+      "severity": "error",
+      "message": "There is no `Authorization` security scheme defined.",
+      "location": [
+        {
+          "source": {
+            "ref": "src/registry/crvs_api_v1.0.0.yaml"
+          },
+          "pointer": "#/paths/~1registry~1notify/post/security/0/Authorization",
+          "reportOnKey": true
+        }
+      ],
+      "suggest": []
+    },
+    {
+      "ruleId": "security-defined",
+      "severity": "error",
+      "message": "There is no `Authorization` security scheme defined.",
+      "location": [
+        {
+          "source": {
+            "ref": "src/registry/crvs_api_v1.0.0.yaml"
+          },
+          "pointer": "#/paths/~1registry~1unsubscribe/post/security/0/Authorization",
+          "reportOnKey": true
+        }
+      ],
+      "suggest": []
+    },
+    {
+      "ruleId": "security-defined",
+      "severity": "error",
+      "message": "There is no `Authorization` security scheme defined.",
+      "location": [
+        {
+          "source": {
+            "ref": "src/registry/crvs_api_v1.0.0.yaml"
+          },
+          "pointer": "#/paths/~1registry~1on-unsubscribe/post/security/0/Authorization",
+          "reportOnKey": true
+        }
+      ],
+      "suggest": []
+    },
+    {
+      "ruleId": "security-defined",
+      "severity": "error",
+      "message": "There is no `Authorization` security scheme defined.",
+      "location": [
+        {
+          "source": {
+            "ref": "src/registry/crvs_api_v1.0.0.yaml"
+          },
+          "pointer": "#/paths/~1registry~1txn~1status/post/security/0/Authorization",
+          "reportOnKey": true
+        }
+      ],
+      "suggest": []
+    },
+    {
+      "ruleId": "security-defined",
+      "severity": "error",
+      "message": "There is no `Authorization` security scheme defined.",
+      "location": [
+        {
+          "source": {
+            "ref": "src/registry/crvs_api_v1.0.0.yaml"
+          },
+          "pointer": "#/paths/~1registry~1txn~1on-status/post/security/0/Authorization",
+          "reportOnKey": true
+        }
+      ],
+      "suggest": []
+    },
+    {
+      "ruleId": "security-defined",
+      "severity": "error",
+      "message": "There is no `Authorization` security scheme defined.",
+      "location": [
+        {
+          "source": {
+            "ref": "src/registry/crvs_api_v1.0.0.yaml"
+          },
+          "pointer": "#/paths/~1registry~1sync~1search/post/security/0/Authorization",
+          "reportOnKey": true
+        }
+      ],
+      "suggest": []
+    },
+    {
+      "ruleId": "security-defined",
+      "severity": "error",
+      "message": "There is no `Authorization` security scheme defined.",
+      "location": [
+        {
+          "source": {
+            "ref": "src/registry/crvs_api_v1.0.0.yaml"
+          },
+          "pointer": "#/paths/~1registry~1sync~1txn~1status/post/security/0/Authorization",
+          "reportOnKey": true
+        }
+      ],
+      "suggest": []
+    }
+  ]
+}