30 lines
1.1 KiB
Markdown
30 lines
1.1 KiB
Markdown
# Revision Plan
|
|
|
|
## Blocking changes
|
|
|
|
- Add explicit rejection behavior for unauthenticated portable trust assertions.
|
|
- Strengthen stale-data handling for expired assertions.
|
|
- Add a clearer abstract field or token for trust statement model identification.
|
|
- Clarify whether negative portable assertions require evidence reference, explanation code, or one of the two.
|
|
|
|
## High-value improvements
|
|
|
|
- Add one compact example assertion and one multi-issuer conflict example.
|
|
- Clarify revocation versus supersession.
|
|
- Decide whether trust events are first-class interoperable objects in v1 or primarily internal feeder records.
|
|
- Tighten abstract and terminology wording.
|
|
|
|
## Deferred items
|
|
|
|
- cross-issuer aggregation algorithms
|
|
- global reputation semantics
|
|
- large shared registries
|
|
- mandatory numeric scoring
|
|
|
|
## Draft order for next iteration
|
|
|
|
1. Tighten Sections 4 through 8 around portable assertion conformance.
|
|
2. Add explicit model identification and stale-data rules.
|
|
3. Add negative-assertion handling rules and examples.
|
|
4. Revisit Security, Privacy, IANA, and References for final consistency.
|