Upstream question: what a relative path-valued field resolves against (§6.2)
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 25/100
- Issue type
- Feature
- Clarity
- Clearly specified
- Activity status
- Stale
- Tech stack
- csharp, markdown, yaml
- Domain
- backend, documentation
Research direction
Read docs/spec-conformance/2026-07-31-okf-spec-gap-report.md at S6.2-1 and the issue’s linked upstream discussion, GoogleCloudPlatform/knowledge-catalog#408; this work is blocked until upstream answers. If the answer changes the current interpretation, review FrontmatterResourceClassifier.KindOf in src/OKF4net/FrontmatterResource.cs and update the S6.2-1 entry. Done when the implementation and conformance note match the upstream resolution.
Written by the indexing model from the issue text.
Description
Extracted from ROADMAP.md (Later). Blocked on upstream: GoogleCloudPlatform/knowledge-catalog#408 (open since 2026-09-11).
§6.2 accepts "a relative path" for fields such as attester.resource, but never says what it is relative to. Our reading:
- a bare path is bundle-root-relative;
./and../are relative to the concept's directory.
This is the only reading under which the spec's own §6.3, §10.2 and Appendix A examples resolve. It is recorded as S6.2-1 in docs/spec-conformance/2026-07-31-okf-spec-gap-report.md (PR #91).
If upstream answers otherwise, FrontmatterResourceClassifier.KindOf (src/OKF4net/FrontmatterResource.cs) and the S6.2-1 entry change with it, and bundles written with bare paths would resolve differently.
- 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