Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

ISO15118-20 Canonical EXI support

Open
#116 4 comments 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 6 days

Nobody has claimed this yet.

  • #126 by @jayharper — closed without merging

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
35/100
Issue type
Feature
Clarity
Needs clarification
Activity status
Quiet
Tech stack
python
Domain
networking

Research direction

Start by tracing the EXI encoding and decoding process described in the issue and compare its namespace and prefix handling with ISO15118-20 canonical EXI requirements. Confirm whether the missing data explains signing failures, then define support and validation for the relevant canonical encoding behavior.

Written by the indexing model from the issue text.

Description

I know that ISO15118-20 protocol should use canonical exi.
I wonder if you support this.
I checked the code and it seems that the EXI encoding/decoding process does not include namespace and prefix data.
Isn't that why signing fails in this situation?

Dominant language
Python
Stars
69
Forks
38
Avg merge
7d 8h
Merged PRs (30d)
6

Getting set up

  • No Dockerfile or Docker Compose file
  • Has a pull request template
  • No contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from EVerest/cbexigen

All issues in EVerest/cbexigen

Similar issues

More Python issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.