Upstream question: concept id character set (ASCII-only vs Unicode)
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 5/5
- Estimated time
- Over a week
- Newbie friendliness
- 25/100
Research direction
Read docs/outreach/upstream-issues/2026-07-31-concept-id-character-set-clarification.md and the Later entry in ROADMAP.md; the decision is explicitly blocked on upstream clarification. If it is resolved, assess ConceptId.ValidateSegment, ConceptId.Slugify, and the golden fixtures as part of a design pass for cross-platform Unicode normalization. Done means an agreed character-set policy and compatible validation and fixtures; no change is ready to make today.
Written by the indexing model from the issue text.
Description
Extracted from ROADMAP.md (Later). Blocked on upstream.
§2 does not restrict the characters a concept id may contain. ConceptId.ValidateSegment currently restricts them to ASCII. Allowing full Unicode is an open, deliberately deferred decision, raised upstream: see docs/outreach/upstream-issues/2026-07-31-concept-id-character-set-clarification.md.
This blocks nothing today, because ConceptId.Slugify folds non-ASCII characters to '-'. Broadening ValidateSegment would need its own design pass: cross-platform Unicode normalization, and the impact on golden fixtures.
- Dominant language
- C#
- Stars
- 4
- Forks
- 1
- Avg merge
- 1d 4h
- Merged PRs (30d)
- 32
Getting set up
- No Dockerfile or Docker Compose file
- Has a pull request template
- Read the contributing guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from jchable/okf4net
-
documentation
Difficulty 2/5 1-3 hours Newbie friendliness 85/100
Maintainers usually reply within 1 day
-
.NET bug
Difficulty 2/5 1-3 hours Newbie friendliness 85/100
Maintainers usually reply within 1 day
-
test
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
Maintainers usually reply within 1 day
-
documentation good first issue
Difficulty 1/5 1-3 hours Newbie friendliness 90/100
Maintainers usually reply within 1 day
-
documentation good first issue
Difficulty 1/5 Under an hour Newbie friendliness 82/100
Maintainers usually reply within 1 day
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
-
area/backend type/bug
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
umbraco/Umbraco-CMS#24668 · 1 comment ·
Maintainers usually reply within 1 day
-
Pri3
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
MicrosoftDocs/windows-dev-docs#6205 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
Maintainers usually reply within 1 day
-
area-ai untriaged
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
dotnet/extensions#7956 ·
Maintainers usually reply within 1 day