-
Notifications
You must be signed in to change notification settings - Fork 0
Expand file tree
/
Copy pathNOTICE
More file actions
98 lines (72 loc) · 3.43 KB
/
NOTICE
File metadata and controls
98 lines (72 loc) · 3.43 KB
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
GAAIM — Generally Accepted AI Metrics
Copyright (c) 2026 Edson Technologies, Inc.
This specification is published under the following licenses:
Specification text: CC-BY-SA 4.0 (see LICENSE-SPEC)
Code and schemas: Apache License 2.0 (see LICENSE-CODE)
-----------------------------------------------------------------------
ATTRIBUTIONS
-----------------------------------------------------------------------
This specification builds on and references the following open standards
and prior work:
CloudEvents 1.0
https://cloudevents.io/
Licensed under Apache 2.0, Cloud Native Computing Foundation.
GAAIM defines its event envelope as a CloudEvents 1.0 profile.
JSON Canonicalization Scheme (JCS) — RFC 8785
https://www.rfc-editor.org/rfc/rfc8785
Authors: A. Rundgren, B. Jordan, S. Erdtman
GAAIM canonical serialization is based on JCS with specified
GAAIM-specific exclusions.
Edwards-Curve Digital Signature Algorithm (EdDSA) — RFC 8032
https://www.rfc-editor.org/rfc/rfc8032
Authors: S. Josefsson, I. Liusvaara
Ed25519 is the Mandatory-to-Implement signature algorithm for
GAAIM v0.1-draft.
Key Words for Use in RFCs to Indicate Requirement Levels — RFC 2119
(updated by RFC 8174)
https://www.rfc-editor.org/info/bcp14
Author: S. Bradner
Normative language conventions used throughout this specification.
NIST FIPS 186-5 — Digital Signature Standard
U.S. National Institute of Standards and Technology, 2023
Standardization of Ed25519 (EdDSA).
ULID Specification
https://github.com/ulid/spec
Author: Alizain Feerasta
One of the two supported event-identifier formats.
UUID Version 7 — RFC 9562 §5.7
https://www.rfc-editor.org/rfc/rfc9562
The other supported event-identifier format.
W3C Trace Context
https://www.w3.org/TR/trace-context/
Referenced for `traceid` and correlation context.
-----------------------------------------------------------------------
INFORMATIVE REFERENCES
-----------------------------------------------------------------------
The following projects informed the design of GAAIM but are not
required by the specification:
Sigstore — https://www.sigstore.dev/
in-toto — https://in-toto.io/
SLSA — https://slsa.dev/
C2PA — https://c2pa.org/
HL7 FHIR — https://hl7.org/fhir/ (Core + Profiles architecture precedent)
OpenID Connect — https://openid.net/specs/openid-connect-core-1_0.html
(Core + Profiles architecture precedent)
See §12.3 of the specification for a detailed comparison against
in-toto, SLSA, and C2PA.
-----------------------------------------------------------------------
TRADEMARKS
-----------------------------------------------------------------------
"GAAIM" and the GAAIM wordmark are unregistered trademarks of Edson
Technologies, Inc. If governance is contributed to a neutral standards
body in the future, trademark assignment would accompany that
contribution.
"ForgeTrack" is a trademark of Edson Technologies, Inc.
All other trademarks are the property of their respective owners.
-----------------------------------------------------------------------
CONTACT
-----------------------------------------------------------------------
Specification: https://github.com/GAAIM-standard/spec
Website: https://gaaim.org
Publisher: Edson Technologies, Inc. (https://edson.tech)
Implementation: ForgeTrack (https://forgetrack.io)