TODO
- Dominant language
- Zig
- Stars
- 0
- Forks
- 0
- PR merge metrics
- No merged PRs in 30d
Description
Development will initially follow the procedures of the official spec (draft) based on the features available from the language or not (include cffi?).
**Reference:**
- https://www.ietf.org/archive/id/draft-ietf-sacm-coswid-22.html
**Libraries:**
- [ ] [CBor parser](https://github.com/r4gus/zbor)
- [ ] XML parser ([zig version](https://gist.github.com/kassane/b2ae56932c28bbdb23433c2052da8822) , [xml tokenize](https://github.com/andrewrk/xml) or [libxml2](https://github.com/mitchellh/zig-libxml2))
Contributor guide
No contributing guide indexed for this repository
Research direction
Start by reading the referenced CoSWID draft and the repository's current implementation scope. Then evaluate the listed CBOR and XML parser options, including whether CFFI is needed. The issue does not define a concrete implementation target or acceptance criteria, so the work is not done until that scope is agreed.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- zig
- Domain
- embedded-iot
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100