beckn / beckn/DSEP-Specification
DSEP Functional Documentation
- Dominant language
- No language data
- Stars
- 21
- Forks
- 20
- PR merge metrics
- No merged PRs in 30d
Description
## Enhance DSEP Functional Documentation
### Description
In our ongoing commitment to advancing decentralized skills and education networks, this issue is raised to propose enhancements to the existing DSEP Specification. The document aims to consolidate insights from various sources and discussions with subject matter experts (SMEs), providing an overview of the protocol's potential implementations.
The document includes updates such as additional notes, sample network policies, and workflow adjustments for a comprehensive understanding of the decentralized skills and education sector, including the additional API workflows which are detailed for reference purposes.
### Goals
- Incorporate real-world use cases within the Skills and Education sector.
- Capture workflows corresponding to identified use cases.
- Offer an end-to-end understanding of the possibilities within the decentralized skills and education domain.
- Define taxonomies relevant to the sector (if applicable).
### Expected Outcome
The document is expected to serve as a valuable resource, presenting both functional and technical insights for end-users. Stakeholders and SMEs are encouraged to review the document and provide feedback to ensure completeness and accuracy.
### Draft document to be reviewed
[DSEP Specification Draft Document](https://github.com/viraj89/DSEP-Specification/tree/draft/docs)
### Project Name
Beckn
### Organization Name
Beckn Open Collective
### Domain
Skilling and Education
### Skills Required
Domain expertise in Skilling and Education
Contributor guide
No contributing guide indexed for this repository
Research direction
Start by reviewing the DSEP Specification Draft Document in the linked repository's docs directory. Compare the existing material with the stated goals for use cases, workflows, end-to-end coverage, and taxonomies, then identify specific documentation gaps with the relevant stakeholders. Done means the agreed functional and technical updates are incorporated and the document is complete and accurate.
Written by the indexing model from the issue text.
Assessment
- Domain
- documentation
- Issue type
- Documentation
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100