W3C PROV-O, Recommendation 30 April 2013; namespace http://www.w3.org/ns/prov# (section 1.3) | prov:Entity, prov:Activity, prov:Agent, prov:wasGeneratedBy, prov:wasDerivedFrom, prov:wasAttributedTo, prov:wasAssociatedWith, prov:actedOnBehalfOf (domain and range prov:Agent) are starting point terms (4.1); prov:Person, prov:SoftwareAgent, prov:hadPrimarySource (a sub-property of prov:wasDerivedFrom, prov:Entity to prov:Entity) are expanded terms (4.2); prov:Derivation (a subclass of prov:EntityInfluence, which qualifies prov:wasDerivedFrom), prov:Delegation (a subclass of prov:AgentInfluence, with prov:hadActivity and prov:agent, qualifying prov:actedOnBehalfOf) and prov:qualifiedDelegation (from a prov:Agent to a prov:Delegation) are qualified terms (4.3) | 1.3, 4.1, 4.2, 4.3 | A prov:Activity "occurs over a period of time" (4.1): an event of an item is an instant, so the class plan:Event specializes it as the audit already says and a time is data (plan:eventAt) and not prov:startedAtTime. prov:Derivation is an influence and not an entity, which is why plan:Trace specializes it and no other class does |
| OASIS SARIF 2.1.0 Plus Errata 01, OASIS Standard 28 August 2023 | The result level is warning, error, note or none, and none only where kind is not fail (3.27.10); kind is pass, open, informational, notApplicable, review or fail, fail by default (3.27.9); fingerprints and partialFingerprints are objects of strings keyed by a versioned name (3.27.16, 3.27.17); baselineState is new, unchanged, updated or absent, and a result management system might file an issue on new, edit it on updated and resolve it on absent (3.27.24, note 2); suppressions hold kind inSource or external and status accepted, underReview or rejected (3.27.23, 3.35); locations, ruleId and workItemUris are properties of a result (3.27.12, 3.27.5, 3.27.27); a physicalLocation holds an artifactLocation and a region with startLine (3.29, 3.30.5) | 3.27, 3.29, 3.30, 3.35 | The three severities are the levels that apply to a fail result and not all of level; none is not a severity. The default level where it is absent is warning, and a result's fingerprint is a SARIF term, so plan:fingerprint is the same idea under the library's own name |
W3C Web Annotation Data Model, Recommendation 23 February 2017, and Web Annotation Vocabulary, Recommendation 23 February 2017 (namespace http://www.w3.org/ns/oa#, vocabulary 1.1) | The motivations, instances of oa:Motivation, are assessing, bookmarking, classifying, commenting, describing, editing, highlighting, identifying, linking, moderating, questioning, replying and tagging (model 3.3.5; vocabulary 2.3.1 to 2.3.13, each IRI http://www.w3.org/ns/oa#<name>); there SHOULD be exactly one motivation for each annotation (3.3.5); a TextQuoteSelector has exactly one exact and at most one prefix and one suffix (model 4.2.4) | Model 3.3.5, 4.2.4; vocabulary 1.1, 2.3 | The first draft named three motivations; there are thirteen. The monorepo's record keeps one, as the text says a record SHOULD, and uses commenting by default and assessing for a build finding |
| IETF RFC 5545 (iCalendar), September 2009 | The STATUS of a VTODO is NEEDS-ACTION, COMPLETED, IN-PROCESS or CANCELLED (3.8.1.11); PERCENT-COMPLETE is an integer from 0 to 100 (3.8.1.8); PRIORITY is an integer from 0 to 9, 0 undefined and 1 highest (3.8.1.9); RELATED-TO takes the RELTYPE PARENT (the default), CHILD or SIBLING (3.8.4.5, 3.2.15) | 3.6.2, 3.8.1.8, 3.8.1.9, 3.8.1.11, 3.8.4.5, 3.2.15 | PRIORITY is the importance of a task and plan:Severity is how serious a problem is: they are two things (OSLC also keeps them apart) and Planning does not take PRIORITY for severity. A closed item is COMPLETED or CANCELLED by its reason, and the library's mapping of a reason to one of them is its own |
| IETF RFC 9253 (iCalendar relationships), August 2022, Standards Track, updates RFC 5545 | RELTYPE=DEPENDS-ON: the current component depends on the referenced one, so that "a task may be blocked waiting on the other" (section 5); the temporal types FINISHTOSTART, FINISHTOFINISH, STARTTOFINISH, STARTTOSTART sit in the predecessor and refer to the successor (section 4); RELATED-TO may be in any component and take a URI or a UID (9.1) | 4, 5, 9.1 | The direction is the reverse of plan:Blocks: the blocked item holds the DEPENDS-ON that names the blocker |
OASIS OSLC Change Management 3.0, OASIS Standard with Approved Errata 01, 6 July 2023 (Part 1 specification, Part 2 vocabulary, Part 3 constraints; namespace http://open-services.net/ns/cm#) | A oslc_cm:ChangeRequest with the properties dcterms:title, dcterms:description, dcterms:identifier, dcterms:subject, dcterms:contributor, dcterms:created, dcterms:modified (Part 3, 2.1); oslc_cm:state of the individuals Closed, Inprogress, Fixed, Approved, Reviewed, Verified (Part 2, 3.1) and the predicates closed, inProgress, fixed, approved, reviewed, verified (Part 1, 2.9); oslc_cm:priority High, Medium, Low, PriorityUnassigned (3.2); oslc_cm:severity Blocker, Critical, Major, Normal, Minor, SeverityUnassigned (3.3); oslc_cm:parent, oslc_cm:relatedChangeRequest; servers MAY have custom states and SHOULD relate them with skos:narrower (Part 2, 3) | Part 1 2.9; Part 2 2.1, 3; Part 3 2.1 | OSLC Change Management defines no history of events, so the events are Planning's own. The Part 2 text says its states are values of oslc_cm:status, and Part 1 says status is deprecated for state: the text disagrees with itself and Planning takes state. The severity Blocker is a level of severity and is not the monorepo's blocker flag |
| GitHub Flavored Markdown, version 0.29-gfm (2019-04-06) | The task list item extension (5.3): a list item whose first block is a paragraph that begins with a marker of optional spaces, [, a whitespace character or x or X, ], and at least one whitespace character; unchecked for whitespace, otherwise checked; nested without limit (examples 279, 280) | 5.2, 5.3 | The first draft read - [ ] and - [x]: the marker is the text above and not a list marker, X is checked, +, * and ordered markers hold, and the spec does not say how a checkbox is changed. GitHub's own page says to use a hyphen and a space and [x], which is narrower than the extension |
| GitHub Docs, REST API version 2026-03-10; issue linking and issue relations | The state of an issue is open or closed; the state_reason is completed, not_planned, duplicate, reopened or null, and duplicate_issue_id goes with duplicate (REST, update an issue); the closing keywords are close, closes, closed, fix, fixes, fixed, resolve, resolves, resolved, with KEYWORD #N or KEYWORD OWNER/REPOSITORY#N, in a pull request description or a commit message, and act on the default branch; sub-issues up to 100 for each parent and eight levels, and an issue may be marked blocked by or blocking another | REST issues; linking a pull request to an issue; adding sub-issues; creating issue dependencies | The reasons for closing are three and a fourth value reopened is the reason of the opposite change. Refs #N is not a closing keyword and is not named by the pages read |
git interpret-trailers (git-scm.com documentation) | A trailer is a key and a value with a colon as the separator, the key of ASCII letters, digits and hyphens, in a block after a blank line; only : is recognized by default (trailer.separators changes that) | Description; trailer.separators | The line Refs #N has no colon, so Git does not read it as a trailer by default; it is a convention of this repository (repoctl.config.ts), and Co-Authored-By: ... and Claude-Session: ... are trailers |
| IETF RFC 9562 (UUIDs), May 2024, Standards Track | UUIDv7: 48-bit big-endian unix_ts_ms, version 7, rand_a of 12 bits, variant 10, rand_b of 62 bits (5.7); counters in rand_a and rand_b and clock precision in rand_a keep order within a millisecond (6.2, methods 1 to 3); sortable as raw bytes and as text (6.11); a node id belongs in a UUIDv8 (6.4) | 4, 5.7, 6.2, 6.4, 6.11 | AnyFS's makeVersionId fills rand_a with a counter that starts at a random seed below 2048 in each new millisecond and grows by one (method 1) and rand_b with 62 random bits for each id, so that it is a version 7 as section 5.7 words it and holds no node identity (6.4) |
ULID specification (github.com/ulid/spec, README; no version number) | 128 bits: 48 bits of time in milliseconds since 1970 and 80 bits of randomness; 26 characters of Crockford base 32 (0123456789ABCDEFGHJKMNPQRSTVWXYZ); sorted as text; within one millisecond the order is not guaranteed; the largest is 7ZZZZZZZZZZZZZZZZZZZZZZZZZ | Components, Sorting, Canonical string representation, Overflow errors | The second precision of the monorepo's event time and the unordered millisecond of a ULID are the reasons the real fold orders by time and then id and the reason a new event there is made to come after the latest |
| IETF RFC 8785 (JSON Canonicalization Scheme), June 2020, Informational | Properties sorted recursively by name, arrays not reordered (3.2.3); data in the I-JSON subset (3.1) | 3.1, 3.2.3 | None; it is the model of the order of keys, not a requirement that the files be canonical JSON |
| JSON5 1.0.0, March 2018 | A superset of JSON with comments, unquoted keys and trailing commas | Abstract, comments | None |
| SKOS | Every code list is a concept | Terms held by rdf (not re-read in this pass) | Unchanged |
| RFC 2119, EARS, Gherkin | The form of this specification | Adopted by 0003-mizan (not re-read in this pass) | Unchanged |