Skip to content

Enhance lifecycle.md with abstract and version info - #3

Open
miqui wants to merge 1 commit into
OAI:mainfrom
miqui:patch-2
Open

Enhance lifecycle.md with abstract and version info#3
miqui wants to merge 1 commit into
OAI:mainfrom
miqui:patch-2

Conversation

@miqui

@miqui miqui commented Jul 30, 2026

Copy link
Copy Markdown

Add abstract and versioning details to lifecycle spec. A refactor to a format more compatible with other the other specs.

Add abstract and versioning details to lifecycle spec. A refactor to a format more compatible with other the other specs.

@handrews handrews left a comment

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I haven't thought about all of this in detail, but noted some oddities with starting this up from the template (which... I have no idea where that template came from TBH).

Comment thread src/lifecycle.md
# Lifecycle Specification

## Version History
## Abstract

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The abstract gets added by the build system, and its text is in spec.config.json. I have no idea why, but I assume this is a ReSpec thing.

Comment thread src/lifecycle.md
Comment on lines 40 to 49
## Definitions

### Lifecycle Object
### Lifecycle

A **Lifecycle Object** is ...

#### Fixed Fields

| Field Name | Type | Description |
| ---- | ---- | ---- |
| TODO | TODO | TODO |
TODO: A short, informal description of what a Lifecycle is conceptually —
not the field-by-field schema. The Fixed Fields for the Lifecycle Object
live under [Schema](#schema) below.

### Schema Object

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

We don't have this section in the OAS (or at least not anymore), so I went looking at Arazzo. I think based on how Arazzo uses it, defining "Lifecycle" in general terms here makes sense, but not "Schema Object".

Comment thread src/lifecycle.md
Comment on lines +56 to +63
### Versions

This document is the Lifecycle Specification version 1.0.0.
The Lifecycle Specification is versioned using a `major`.`minor`.`patch`
scheme. The `major`.`minor` portion of the version string (for example,
`1.0`) designates the Lifecycle feature set in effect. `patch` releases
address errors in, or provide clarifications to, this document without
changing the feature set; tooling SHOULD treat all patch releases within a
`major`.`minor` line as equivalent.

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Given the ongoing debate about the patch number, let's do the version stuff in its own PR so that people can debate that separately.

Comment thread src/lifecycle.md
[Relationship to the OpenAPI Specification](#relationship-to-the-openapi-specification)
above).

### Schema

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

We've changed this to Specification in the other documents.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants