schemas: add WORK-IN-PROGRESS placeholders, don't mention patch numbers, update terminology by handrews · Pull Request #4146 · OAI/OpenAPI-Specification

handrews · 2024-10-18T19:00:12Z

I'd like to merge this and address it in the build scripts rather than resuming publication of schemas with absent dates and misleading patch release guidance.

Replace all dates with WORK-IN-PROGRESS
Append a date segement (as WORK-IN-PROGRESS) where missing
Adjust refs and other fields to WORK-IN-PROGRESS
Remove mention of specific patch releases
Use capital-D Document and Description according to new rules

* Replace all dates with WORK-IN-PROGRESS * Append a date segement (as WORK-IN-PROGRESS) where missing * Adjust refs and other fields to WORK-IN-PROGRESS * Remove mention of specific patch releases * Use capital-D Document and Description according to new rules

handrews · 2024-10-19T18:19:27Z

@ralfhandl As I noted in my comments on #4139, I am aware that this is more complex. I also noted there (and apparently forgot to note here, for which I apologize- if you read this first it was no doubt confusing) that it's probably fine to just change all of the dates at once for now. Certainly the first time we publish things we'll have changes to schema and need to set initial dates on dialect/base and meta/base. We'll also need to update base-schema to point to the new schema every time any of the other three are iterated.

So for now, a global search-and-replace is fine. We can then refine it. The rules are fairly straightforward:

Changes to anything require a change in base-schema
Changes to meta-base require a change to dialect-base

I think this will be easier to manage once we fix the branching. We need a schema-dev branch analogous to the dev branch so that we can manage schemas in parallel. They can't just be on the dev branch because they don't change at the same rate. But particularly with 3.1+, it's best that we be able to make a series of changes and decide when to publish to main, just like we do with the spec. It's just that the threshold for publishing should be much lower.

But doing this will make it easier to manage which of the various schema dates need updating.

Keep in mind also that you can search/replace schema/WORK-IN-PROGRESS, schema-base/WORK-IN-PROGRESSdialect/base/WORK-IN-PROGRESS, and meta/base/WORK-IN-PROGRESS separately, as none of them are substrings of each other.

Questions answered

ralfhandl · 2024-10-21T12:29:54Z

If we remove the ready-to-use id or $id from the YAML files, we should add a link to https://spec.openapis.org/ to each of the README.md files.

handrews · 2024-10-22T01:14:20Z

I realized that we can't both host a schema ending in /baseand have a directory of schemas like /base/2024-10-18. Absent any better idea, I just replaced base with WORK-IN-PROGRESS instead of appending it.

Note that the vocabulary URI (not to be confused with the vocabulary metaschema URI) does not get a date as it is about the semantics, which aren't going to change within a minor release line even if we correct or add commentary to the corresponding metaschema.

It's not ideal to have this base alongside 2024-10-18, and I'm open to other date-including patterns.

ralfhandl · 2024-10-22T07:12:06Z

Resolved conflicts and aligned the two README.md files.

To be consistent with the other YAML files

handrews · 2024-10-18T19:00:12Z

I'd like to merge this and address it in the build scripts rather than resuming publication of schemas with absent dates and misleading patch release guidance.

Replace all dates with WORK-IN-PROGRESS
Append a date segement (as WORK-IN-PROGRESS) where missing
Adjust refs and other fields to WORK-IN-PROGRESS
Remove mention of specific patch releases
Use capital-D Document and Description according to new rules

* Replace all dates with WORK-IN-PROGRESS * Append a date segement (as WORK-IN-PROGRESS) where missing * Adjust refs and other fields to WORK-IN-PROGRESS * Remove mention of specific patch releases * Use capital-D Document and Description according to new rules

handrews · 2024-10-19T18:19:27Z

@ralfhandl As I noted in my comments on #4139, I am aware that this is more complex. I also noted there (and apparently forgot to note here, for which I apologize- if you read this first it was no doubt confusing) that it's probably fine to just change all of the dates at once for now. Certainly the first time we publish things we'll have changes to schema and need to set initial dates on dialect/base and meta/base. We'll also need to update base-schema to point to the new schema every time any of the other three are iterated.

So for now, a global search-and-replace is fine. We can then refine it. The rules are fairly straightforward:

Changes to anything require a change in base-schema
Changes to meta-base require a change to dialect-base

I think this will be easier to manage once we fix the branching. We need a schema-dev branch analogous to the dev branch so that we can manage schemas in parallel. They can't just be on the dev branch because they don't change at the same rate. But particularly with 3.1+, it's best that we be able to make a series of changes and decide when to publish to main, just like we do with the spec. It's just that the threshold for publishing should be much lower.

But doing this will make it easier to manage which of the various schema dates need updating.

Keep in mind also that you can search/replace schema/WORK-IN-PROGRESS, schema-base/WORK-IN-PROGRESSdialect/base/WORK-IN-PROGRESS, and meta/base/WORK-IN-PROGRESS separately, as none of them are substrings of each other.

Questions answered

ralfhandl · 2024-10-21T12:29:54Z

If we remove the ready-to-use id or $id from the YAML files, we should add a link to https://spec.openapis.org/ to each of the README.md files.

handrews · 2024-10-22T01:14:20Z

I realized that we can't both host a schema ending in /baseand have a directory of schemas like /base/2024-10-18. Absent any better idea, I just replaced base with WORK-IN-PROGRESS instead of appending it.

Note that the vocabulary URI (not to be confused with the vocabulary metaschema URI) does not get a date as it is about the semantics, which aren't going to change within a minor release line even if we correct or add commentary to the corresponding metaschema.

It's not ideal to have this base alongside 2024-10-18, and I'm open to other date-including patterns.

ralfhandl · 2024-10-22T07:12:06Z

Resolved conflicts and aligned the two README.md files.

To be consistent with the other YAML files

handrews · 2024-10-18T19:00:12Z

I'd like to merge this and address it in the build scripts rather than resuming publication of schemas with absent dates and misleading patch release guidance.

Replace all dates with WORK-IN-PROGRESS
Append a date segement (as WORK-IN-PROGRESS) where missing
Adjust refs and other fields to WORK-IN-PROGRESS
Remove mention of specific patch releases
Use capital-D Document and Description according to new rules

* Replace all dates with WORK-IN-PROGRESS * Append a date segement (as WORK-IN-PROGRESS) where missing * Adjust refs and other fields to WORK-IN-PROGRESS * Remove mention of specific patch releases * Use capital-D Document and Description according to new rules

handrews · 2024-10-19T18:19:27Z

@ralfhandl As I noted in my comments on #4139, I am aware that this is more complex. I also noted there (and apparently forgot to note here, for which I apologize- if you read this first it was no doubt confusing) that it's probably fine to just change all of the dates at once for now. Certainly the first time we publish things we'll have changes to schema and need to set initial dates on dialect/base and meta/base. We'll also need to update base-schema to point to the new schema every time any of the other three are iterated.

So for now, a global search-and-replace is fine. We can then refine it. The rules are fairly straightforward:

Changes to anything require a change in base-schema
Changes to meta-base require a change to dialect-base

I think this will be easier to manage once we fix the branching. We need a schema-dev branch analogous to the dev branch so that we can manage schemas in parallel. They can't just be on the dev branch because they don't change at the same rate. But particularly with 3.1+, it's best that we be able to make a series of changes and decide when to publish to main, just like we do with the spec. It's just that the threshold for publishing should be much lower.

But doing this will make it easier to manage which of the various schema dates need updating.

Keep in mind also that you can search/replace schema/WORK-IN-PROGRESS, schema-base/WORK-IN-PROGRESSdialect/base/WORK-IN-PROGRESS, and meta/base/WORK-IN-PROGRESS separately, as none of them are substrings of each other.

Questions answered

ralfhandl · 2024-10-21T12:29:54Z

If we remove the ready-to-use id or $id from the YAML files, we should add a link to https://spec.openapis.org/ to each of the README.md files.

handrews · 2024-10-22T01:14:20Z

I realized that we can't both host a schema ending in /baseand have a directory of schemas like /base/2024-10-18. Absent any better idea, I just replaced base with WORK-IN-PROGRESS instead of appending it.

Note that the vocabulary URI (not to be confused with the vocabulary metaschema URI) does not get a date as it is about the semantics, which aren't going to change within a minor release line even if we correct or add commentary to the corresponding metaschema.

It's not ideal to have this base alongside 2024-10-18, and I'm open to other date-including patterns.

ralfhandl · 2024-10-22T07:12:06Z

Resolved conflicts and aligned the two README.md files.

To be consistent with the other YAML files

handrews · 2024-10-18T19:00:12Z

I'd like to merge this and address it in the build scripts rather than resuming publication of schemas with absent dates and misleading patch release guidance.

Replace all dates with WORK-IN-PROGRESS
Append a date segement (as WORK-IN-PROGRESS) where missing
Adjust refs and other fields to WORK-IN-PROGRESS
Remove mention of specific patch releases
Use capital-D Document and Description according to new rules

* Replace all dates with WORK-IN-PROGRESS * Append a date segement (as WORK-IN-PROGRESS) where missing * Adjust refs and other fields to WORK-IN-PROGRESS * Remove mention of specific patch releases * Use capital-D Document and Description according to new rules

handrews · 2024-10-19T18:19:27Z

@ralfhandl As I noted in my comments on #4139, I am aware that this is more complex. I also noted there (and apparently forgot to note here, for which I apologize- if you read this first it was no doubt confusing) that it's probably fine to just change all of the dates at once for now. Certainly the first time we publish things we'll have changes to schema and need to set initial dates on dialect/base and meta/base. We'll also need to update base-schema to point to the new schema every time any of the other three are iterated.

So for now, a global search-and-replace is fine. We can then refine it. The rules are fairly straightforward:

Changes to anything require a change in base-schema
Changes to meta-base require a change to dialect-base

I think this will be easier to manage once we fix the branching. We need a schema-dev branch analogous to the dev branch so that we can manage schemas in parallel. They can't just be on the dev branch because they don't change at the same rate. But particularly with 3.1+, it's best that we be able to make a series of changes and decide when to publish to main, just like we do with the spec. It's just that the threshold for publishing should be much lower.

But doing this will make it easier to manage which of the various schema dates need updating.

Keep in mind also that you can search/replace schema/WORK-IN-PROGRESS, schema-base/WORK-IN-PROGRESSdialect/base/WORK-IN-PROGRESS, and meta/base/WORK-IN-PROGRESS separately, as none of them are substrings of each other.

Questions answered

ralfhandl · 2024-10-21T12:29:54Z

If we remove the ready-to-use id or $id from the YAML files, we should add a link to https://spec.openapis.org/ to each of the README.md files.

handrews · 2024-10-22T01:14:20Z

I realized that we can't both host a schema ending in /baseand have a directory of schemas like /base/2024-10-18. Absent any better idea, I just replaced base with WORK-IN-PROGRESS instead of appending it.

Note that the vocabulary URI (not to be confused with the vocabulary metaschema URI) does not get a date as it is about the semantics, which aren't going to change within a minor release line even if we correct or add commentary to the corresponding metaschema.

It's not ideal to have this base alongside 2024-10-18, and I'm open to other date-including patterns.

ralfhandl · 2024-10-22T07:12:06Z

Resolved conflicts and aligned the two README.md files.

To be consistent with the other YAML files

handrews · 2024-10-18T19:00:12Z

I'd like to merge this and address it in the build scripts rather than resuming publication of schemas with absent dates and misleading patch release guidance.

Replace all dates with WORK-IN-PROGRESS
Append a date segement (as WORK-IN-PROGRESS) where missing
Adjust refs and other fields to WORK-IN-PROGRESS
Remove mention of specific patch releases
Use capital-D Document and Description according to new rules

* Replace all dates with WORK-IN-PROGRESS * Append a date segement (as WORK-IN-PROGRESS) where missing * Adjust refs and other fields to WORK-IN-PROGRESS * Remove mention of specific patch releases * Use capital-D Document and Description according to new rules

handrews · 2024-10-19T18:19:27Z

@ralfhandl As I noted in my comments on #4139, I am aware that this is more complex. I also noted there (and apparently forgot to note here, for which I apologize- if you read this first it was no doubt confusing) that it's probably fine to just change all of the dates at once for now. Certainly the first time we publish things we'll have changes to schema and need to set initial dates on dialect/base and meta/base. We'll also need to update base-schema to point to the new schema every time any of the other three are iterated.

So for now, a global search-and-replace is fine. We can then refine it. The rules are fairly straightforward:

Changes to anything require a change in base-schema
Changes to meta-base require a change to dialect-base

I think this will be easier to manage once we fix the branching. We need a schema-dev branch analogous to the dev branch so that we can manage schemas in parallel. They can't just be on the dev branch because they don't change at the same rate. But particularly with 3.1+, it's best that we be able to make a series of changes and decide when to publish to main, just like we do with the spec. It's just that the threshold for publishing should be much lower.

But doing this will make it easier to manage which of the various schema dates need updating.

Keep in mind also that you can search/replace schema/WORK-IN-PROGRESS, schema-base/WORK-IN-PROGRESSdialect/base/WORK-IN-PROGRESS, and meta/base/WORK-IN-PROGRESS separately, as none of them are substrings of each other.

Questions answered

ralfhandl · 2024-10-21T12:29:54Z

If we remove the ready-to-use id or $id from the YAML files, we should add a link to https://spec.openapis.org/ to each of the README.md files.

handrews · 2024-10-22T01:14:20Z

I realized that we can't both host a schema ending in /baseand have a directory of schemas like /base/2024-10-18. Absent any better idea, I just replaced base with WORK-IN-PROGRESS instead of appending it.

Note that the vocabulary URI (not to be confused with the vocabulary metaschema URI) does not get a date as it is about the semantics, which aren't going to change within a minor release line even if we correct or add commentary to the corresponding metaschema.

It's not ideal to have this base alongside 2024-10-18, and I'm open to other date-including patterns.

ralfhandl · 2024-10-22T07:12:06Z

Resolved conflicts and aligned the two README.md files.

To be consistent with the other YAML files

handrews · 2024-10-18T19:00:12Z

I'd like to merge this and address it in the build scripts rather than resuming publication of schemas with absent dates and misleading patch release guidance.

Replace all dates with WORK-IN-PROGRESS
Append a date segement (as WORK-IN-PROGRESS) where missing
Adjust refs and other fields to WORK-IN-PROGRESS
Remove mention of specific patch releases
Use capital-D Document and Description according to new rules

* Replace all dates with WORK-IN-PROGRESS * Append a date segement (as WORK-IN-PROGRESS) where missing * Adjust refs and other fields to WORK-IN-PROGRESS * Remove mention of specific patch releases * Use capital-D Document and Description according to new rules

handrews · 2024-10-19T18:19:27Z

@ralfhandl As I noted in my comments on #4139, I am aware that this is more complex. I also noted there (and apparently forgot to note here, for which I apologize- if you read this first it was no doubt confusing) that it's probably fine to just change all of the dates at once for now. Certainly the first time we publish things we'll have changes to schema and need to set initial dates on dialect/base and meta/base. We'll also need to update base-schema to point to the new schema every time any of the other three are iterated.

So for now, a global search-and-replace is fine. We can then refine it. The rules are fairly straightforward:

Changes to anything require a change in base-schema
Changes to meta-base require a change to dialect-base

I think this will be easier to manage once we fix the branching. We need a schema-dev branch analogous to the dev branch so that we can manage schemas in parallel. They can't just be on the dev branch because they don't change at the same rate. But particularly with 3.1+, it's best that we be able to make a series of changes and decide when to publish to main, just like we do with the spec. It's just that the threshold for publishing should be much lower.

But doing this will make it easier to manage which of the various schema dates need updating.

Keep in mind also that you can search/replace schema/WORK-IN-PROGRESS, schema-base/WORK-IN-PROGRESSdialect/base/WORK-IN-PROGRESS, and meta/base/WORK-IN-PROGRESS separately, as none of them are substrings of each other.

Questions answered

ralfhandl · 2024-10-21T12:29:54Z

If we remove the ready-to-use id or $id from the YAML files, we should add a link to https://spec.openapis.org/ to each of the README.md files.

handrews · 2024-10-22T01:14:20Z

I realized that we can't both host a schema ending in /baseand have a directory of schemas like /base/2024-10-18. Absent any better idea, I just replaced base with WORK-IN-PROGRESS instead of appending it.

Note that the vocabulary URI (not to be confused with the vocabulary metaschema URI) does not get a date as it is about the semantics, which aren't going to change within a minor release line even if we correct or add commentary to the corresponding metaschema.

It's not ideal to have this base alongside 2024-10-18, and I'm open to other date-including patterns.

ralfhandl · 2024-10-22T07:12:06Z

Resolved conflicts and aligned the two README.md files.

To be consistent with the other YAML files

handrews · 2024-10-18T19:00:12Z

I'd like to merge this and address it in the build scripts rather than resuming publication of schemas with absent dates and misleading patch release guidance.

Replace all dates with WORK-IN-PROGRESS
Append a date segement (as WORK-IN-PROGRESS) where missing
Adjust refs and other fields to WORK-IN-PROGRESS
Remove mention of specific patch releases
Use capital-D Document and Description according to new rules

* Replace all dates with WORK-IN-PROGRESS * Append a date segement (as WORK-IN-PROGRESS) where missing * Adjust refs and other fields to WORK-IN-PROGRESS * Remove mention of specific patch releases * Use capital-D Document and Description according to new rules

handrews · 2024-10-19T18:19:27Z

@ralfhandl As I noted in my comments on #4139, I am aware that this is more complex. I also noted there (and apparently forgot to note here, for which I apologize- if you read this first it was no doubt confusing) that it's probably fine to just change all of the dates at once for now. Certainly the first time we publish things we'll have changes to schema and need to set initial dates on dialect/base and meta/base. We'll also need to update base-schema to point to the new schema every time any of the other three are iterated.

So for now, a global search-and-replace is fine. We can then refine it. The rules are fairly straightforward:

Changes to anything require a change in base-schema
Changes to meta-base require a change to dialect-base

I think this will be easier to manage once we fix the branching. We need a schema-dev branch analogous to the dev branch so that we can manage schemas in parallel. They can't just be on the dev branch because they don't change at the same rate. But particularly with 3.1+, it's best that we be able to make a series of changes and decide when to publish to main, just like we do with the spec. It's just that the threshold for publishing should be much lower.

But doing this will make it easier to manage which of the various schema dates need updating.

Keep in mind also that you can search/replace schema/WORK-IN-PROGRESS, schema-base/WORK-IN-PROGRESSdialect/base/WORK-IN-PROGRESS, and meta/base/WORK-IN-PROGRESS separately, as none of them are substrings of each other.

Questions answered

ralfhandl · 2024-10-21T12:29:54Z

If we remove the ready-to-use id or $id from the YAML files, we should add a link to https://spec.openapis.org/ to each of the README.md files.

handrews · 2024-10-22T01:14:20Z

I realized that we can't both host a schema ending in /baseand have a directory of schemas like /base/2024-10-18. Absent any better idea, I just replaced base with WORK-IN-PROGRESS instead of appending it.

Note that the vocabulary URI (not to be confused with the vocabulary metaschema URI) does not get a date as it is about the semantics, which aren't going to change within a minor release line even if we correct or add commentary to the corresponding metaschema.

It's not ideal to have this base alongside 2024-10-18, and I'm open to other date-including patterns.

ralfhandl · 2024-10-22T07:12:06Z

Resolved conflicts and aligned the two README.md files.

To be consistent with the other YAML files

handrews · 2024-10-18T19:00:12Z

I'd like to merge this and address it in the build scripts rather than resuming publication of schemas with absent dates and misleading patch release guidance.

Replace all dates with WORK-IN-PROGRESS
Append a date segement (as WORK-IN-PROGRESS) where missing
Adjust refs and other fields to WORK-IN-PROGRESS
Remove mention of specific patch releases
Use capital-D Document and Description according to new rules

* Replace all dates with WORK-IN-PROGRESS * Append a date segement (as WORK-IN-PROGRESS) where missing * Adjust refs and other fields to WORK-IN-PROGRESS * Remove mention of specific patch releases * Use capital-D Document and Description according to new rules

handrews · 2024-10-19T18:19:27Z

@ralfhandl As I noted in my comments on #4139, I am aware that this is more complex. I also noted there (and apparently forgot to note here, for which I apologize- if you read this first it was no doubt confusing) that it's probably fine to just change all of the dates at once for now. Certainly the first time we publish things we'll have changes to schema and need to set initial dates on dialect/base and meta/base. We'll also need to update base-schema to point to the new schema every time any of the other three are iterated.

So for now, a global search-and-replace is fine. We can then refine it. The rules are fairly straightforward:

Changes to anything require a change in base-schema
Changes to meta-base require a change to dialect-base

I think this will be easier to manage once we fix the branching. We need a schema-dev branch analogous to the dev branch so that we can manage schemas in parallel. They can't just be on the dev branch because they don't change at the same rate. But particularly with 3.1+, it's best that we be able to make a series of changes and decide when to publish to main, just like we do with the spec. It's just that the threshold for publishing should be much lower.

But doing this will make it easier to manage which of the various schema dates need updating.

Keep in mind also that you can search/replace schema/WORK-IN-PROGRESS, schema-base/WORK-IN-PROGRESSdialect/base/WORK-IN-PROGRESS, and meta/base/WORK-IN-PROGRESS separately, as none of them are substrings of each other.

Questions answered

ralfhandl · 2024-10-21T12:29:54Z

If we remove the ready-to-use id or $id from the YAML files, we should add a link to https://spec.openapis.org/ to each of the README.md files.

handrews · 2024-10-22T01:14:20Z

I realized that we can't both host a schema ending in /baseand have a directory of schemas like /base/2024-10-18. Absent any better idea, I just replaced base with WORK-IN-PROGRESS instead of appending it.

Note that the vocabulary URI (not to be confused with the vocabulary metaschema URI) does not get a date as it is about the semantics, which aren't going to change within a minor release line even if we correct or add commentary to the corresponding metaschema.

It's not ideal to have this base alongside 2024-10-18, and I'm open to other date-including patterns.

ralfhandl · 2024-10-22T07:12:06Z

Resolved conflicts and aligned the two README.md files.

To be consistent with the other YAML files

handrews added the Schema changes related to the schema(s) label Oct 18, 2024

handrews requested review from a team as code owners October 18, 2024 19:00

handrews mentioned this pull request Oct 18, 2024
Workflow to publish schemas #4139
Closed
6 tasks

handrews changed the title ~~schemas: add WORK-IN-PROGRESS placeholders, don't mention patch numbers, fix terminology~~schemas: add WORK-IN-PROGRESS placeholders, don't mention patch numbers, update terminologyOct 18, 2024

handrews requested review from karenetheridge and ralfhandl October 18, 2024 21:03

ralfhandl previously requested changes Oct 19, 2024
View reviewed changes

ralfhandl self-requested a review October 21, 2024 10:11

handrews added 2 commits October 21, 2024 10:03

Update the schema READMEs for current practice
8e23d02

"base" can't be both a file and a directory
c0f07c9

Merge remote-tracking branch 'upstream/main' into pr/4146
cc1995d

ralfhandl requested changes Oct 22, 2024
View reviewed changes

Comment threadschemas/v3.1/README.md Outdated
Comment threadschemas/v3.0/README.md Outdated
Comment threadschemas/v3.1/README.md Outdated
Comment threadschemas/v3.1/schema.yaml Outdated

This was referenced Oct 22, 2024
Open Community (TDC) Meeting, Thursday 24 October 2024 #4140
Closed
v3.0.4 schema updates #4132
Closed

handrewsand others added 2 commits October 22, 2024 08:26

Link to issue tracking "latest" schema access
b928227

Update schemas/v3.1/schema.yaml
520a7c3
To be consistent with the other YAML files

ralfhandl approved these changes Oct 22, 2024
View reviewed changes

ralfhandl requested a review from a teamOctober 22, 2024 16:16

lornajane approved these changes Oct 24, 2024
View reviewed changes

miqui merged commit cc25d27 into OAI:mainOct 24, 2024

This was referenced Oct 25, 2024
Schema Publish workflow #4162
Merged
Open Community (TDC) Meeting, Thursday 31 October 2024 #4155
Closed

handrews deleted the schema-ids branch March 29, 2025 17:24

handrews added the Schema changes related to the schema(s) label Oct 18, 2024

handrews requested review from a team as code owners October 18, 2024 19:00

handrews mentioned this pull request Oct 18, 2024
Workflow to publish schemas #4139
Closed
6 tasks

handrews changed the title ~~schemas: add WORK-IN-PROGRESS placeholders, don't mention patch numbers, fix terminology~~schemas: add WORK-IN-PROGRESS placeholders, don't mention patch numbers, update terminologyOct 18, 2024

handrews requested review from karenetheridge and ralfhandl October 18, 2024 21:03

ralfhandl previously requested changes Oct 19, 2024
View reviewed changes

ralfhandl self-requested a review October 21, 2024 10:11

handrews added 2 commits October 21, 2024 10:03

Update the schema READMEs for current practice
8e23d02

"base" can't be both a file and a directory
c0f07c9

Merge remote-tracking branch 'upstream/main' into pr/4146
cc1995d

ralfhandl requested changes Oct 22, 2024
View reviewed changes

Comment threadschemas/v3.1/README.md Outdated
Comment threadschemas/v3.0/README.md Outdated
Comment threadschemas/v3.1/README.md Outdated
Comment threadschemas/v3.1/schema.yaml Outdated

This was referenced Oct 22, 2024
Open Community (TDC) Meeting, Thursday 24 October 2024 #4140
Closed
v3.0.4 schema updates #4132
Closed

handrewsand others added 2 commits October 22, 2024 08:26

Link to issue tracking "latest" schema access
b928227

Update schemas/v3.1/schema.yaml
520a7c3
To be consistent with the other YAML files

ralfhandl approved these changes Oct 22, 2024
View reviewed changes

ralfhandl requested a review from a teamOctober 22, 2024 16:16

lornajane approved these changes Oct 24, 2024
View reviewed changes

miqui merged commit cc25d27 into OAI:mainOct 24, 2024

This was referenced Oct 25, 2024
Schema Publish workflow #4162
Merged
Open Community (TDC) Meeting, Thursday 31 October 2024 #4155
Closed

handrews deleted the schema-ids branch March 29, 2025 17:24

handrews added the Schema changes related to the schema(s) label Oct 18, 2024

handrews requested review from a team as code owners October 18, 2024 19:00

handrews mentioned this pull request Oct 18, 2024
Workflow to publish schemas #4139
Closed
6 tasks

handrews changed the title ~~schemas: add WORK-IN-PROGRESS placeholders, don't mention patch numbers, fix terminology~~schemas: add WORK-IN-PROGRESS placeholders, don't mention patch numbers, update terminologyOct 18, 2024

handrews requested review from karenetheridge and ralfhandl October 18, 2024 21:03

ralfhandl previously requested changes Oct 19, 2024
View reviewed changes

ralfhandl self-requested a review October 21, 2024 10:11

handrews added 2 commits October 21, 2024 10:03

Update the schema READMEs for current practice
8e23d02

"base" can't be both a file and a directory
c0f07c9

Merge remote-tracking branch 'upstream/main' into pr/4146
cc1995d

ralfhandl requested changes Oct 22, 2024
View reviewed changes

Comment threadschemas/v3.1/README.md Outdated
Comment threadschemas/v3.0/README.md Outdated
Comment threadschemas/v3.1/README.md Outdated
Comment threadschemas/v3.1/schema.yaml Outdated

This was referenced Oct 22, 2024
Open Community (TDC) Meeting, Thursday 24 October 2024 #4140
Closed
v3.0.4 schema updates #4132
Closed

handrewsand others added 2 commits October 22, 2024 08:26

Link to issue tracking "latest" schema access
b928227

Update schemas/v3.1/schema.yaml
520a7c3
To be consistent with the other YAML files

ralfhandl approved these changes Oct 22, 2024
View reviewed changes

ralfhandl requested a review from a teamOctober 22, 2024 16:16

lornajane approved these changes Oct 24, 2024
View reviewed changes

miqui merged commit cc25d27 into OAI:mainOct 24, 2024

This was referenced Oct 25, 2024
Schema Publish workflow #4162
Merged
Open Community (TDC) Meeting, Thursday 31 October 2024 #4155
Closed

handrews deleted the schema-ids branch March 29, 2025 17:24

handrews added the Schema changes related to the schema(s) label Oct 18, 2024

handrews requested review from a team as code owners October 18, 2024 19:00

handrews mentioned this pull request Oct 18, 2024
Workflow to publish schemas #4139
Closed
6 tasks

handrews changed the title ~~schemas: add WORK-IN-PROGRESS placeholders, don't mention patch numbers, fix terminology~~schemas: add WORK-IN-PROGRESS placeholders, don't mention patch numbers, update terminologyOct 18, 2024

handrews requested review from karenetheridge and ralfhandl October 18, 2024 21:03

ralfhandl previously requested changes Oct 19, 2024
View reviewed changes

ralfhandl self-requested a review October 21, 2024 10:11

handrews added 2 commits October 21, 2024 10:03

Update the schema READMEs for current practice
8e23d02

"base" can't be both a file and a directory
c0f07c9

Merge remote-tracking branch 'upstream/main' into pr/4146
cc1995d

ralfhandl requested changes Oct 22, 2024
View reviewed changes

Comment threadschemas/v3.1/README.md Outdated
Comment threadschemas/v3.0/README.md Outdated
Comment threadschemas/v3.1/README.md Outdated
Comment threadschemas/v3.1/schema.yaml Outdated

This was referenced Oct 22, 2024
Open Community (TDC) Meeting, Thursday 24 October 2024 #4140
Closed
v3.0.4 schema updates #4132
Closed

handrewsand others added 2 commits October 22, 2024 08:26

Link to issue tracking "latest" schema access
b928227

Update schemas/v3.1/schema.yaml
520a7c3
To be consistent with the other YAML files

ralfhandl approved these changes Oct 22, 2024
View reviewed changes

ralfhandl requested a review from a teamOctober 22, 2024 16:16

lornajane approved these changes Oct 24, 2024
View reviewed changes

miqui merged commit cc25d27 into OAI:mainOct 24, 2024

This was referenced Oct 25, 2024
Schema Publish workflow #4162
Merged
Open Community (TDC) Meeting, Thursday 31 October 2024 #4155
Closed

handrews deleted the schema-ids branch March 29, 2025 17:24

handrews added the Schema changes related to the schema(s) label Oct 18, 2024

handrews requested review from a team as code owners October 18, 2024 19:00

handrews mentioned this pull request Oct 18, 2024
Workflow to publish schemas #4139
Closed
6 tasks

handrews changed the title ~~schemas: add WORK-IN-PROGRESS placeholders, don't mention patch numbers, fix terminology~~schemas: add WORK-IN-PROGRESS placeholders, don't mention patch numbers, update terminologyOct 18, 2024

handrews requested review from karenetheridge and ralfhandl October 18, 2024 21:03

ralfhandl previously requested changes Oct 19, 2024
View reviewed changes

ralfhandl self-requested a review October 21, 2024 10:11

handrews added 2 commits October 21, 2024 10:03

Update the schema READMEs for current practice
8e23d02

"base" can't be both a file and a directory
c0f07c9

Merge remote-tracking branch 'upstream/main' into pr/4146
cc1995d

ralfhandl requested changes Oct 22, 2024
View reviewed changes

Comment threadschemas/v3.1/README.md Outdated
Comment threadschemas/v3.0/README.md Outdated
Comment threadschemas/v3.1/README.md Outdated
Comment threadschemas/v3.1/schema.yaml Outdated

This was referenced Oct 22, 2024
Open Community (TDC) Meeting, Thursday 24 October 2024 #4140
Closed
v3.0.4 schema updates #4132
Closed

handrewsand others added 2 commits October 22, 2024 08:26

Link to issue tracking "latest" schema access
b928227

Update schemas/v3.1/schema.yaml
520a7c3
To be consistent with the other YAML files

ralfhandl approved these changes Oct 22, 2024
View reviewed changes

ralfhandl requested a review from a teamOctober 22, 2024 16:16

lornajane approved these changes Oct 24, 2024
View reviewed changes

miqui merged commit cc25d27 into OAI:mainOct 24, 2024

This was referenced Oct 25, 2024
Schema Publish workflow #4162
Merged
Open Community (TDC) Meeting, Thursday 31 October 2024 #4155
Closed

handrews deleted the schema-ids branch March 29, 2025 17:24

handrews added the Schema changes related to the schema(s) label Oct 18, 2024

handrews requested review from a team as code owners October 18, 2024 19:00

handrews mentioned this pull request Oct 18, 2024
Workflow to publish schemas #4139
Closed
6 tasks

handrews changed the title ~~schemas: add WORK-IN-PROGRESS placeholders, don't mention patch numbers, fix terminology~~schemas: add WORK-IN-PROGRESS placeholders, don't mention patch numbers, update terminologyOct 18, 2024

handrews requested review from karenetheridge and ralfhandl October 18, 2024 21:03

ralfhandl previously requested changes Oct 19, 2024
View reviewed changes

ralfhandl self-requested a review October 21, 2024 10:11

handrews added 2 commits October 21, 2024 10:03

Update the schema READMEs for current practice
8e23d02

"base" can't be both a file and a directory
c0f07c9

Merge remote-tracking branch 'upstream/main' into pr/4146
cc1995d

ralfhandl requested changes Oct 22, 2024
View reviewed changes

Comment threadschemas/v3.1/README.md Outdated
Comment threadschemas/v3.0/README.md Outdated
Comment threadschemas/v3.1/README.md Outdated
Comment threadschemas/v3.1/schema.yaml Outdated

This was referenced Oct 22, 2024
Open Community (TDC) Meeting, Thursday 24 October 2024 #4140
Closed
v3.0.4 schema updates #4132
Closed

handrewsand others added 2 commits October 22, 2024 08:26

Link to issue tracking "latest" schema access
b928227

Update schemas/v3.1/schema.yaml
520a7c3
To be consistent with the other YAML files

ralfhandl approved these changes Oct 22, 2024
View reviewed changes

ralfhandl requested a review from a teamOctober 22, 2024 16:16

lornajane approved these changes Oct 24, 2024
View reviewed changes

miqui merged commit cc25d27 into OAI:mainOct 24, 2024

This was referenced Oct 25, 2024
Schema Publish workflow #4162
Merged
Open Community (TDC) Meeting, Thursday 31 October 2024 #4155
Closed

handrews deleted the schema-ids branch March 29, 2025 17:24

handrews added the Schema changes related to the schema(s) label Oct 18, 2024

handrews requested review from a team as code owners October 18, 2024 19:00

handrews mentioned this pull request Oct 18, 2024
Workflow to publish schemas #4139
Closed
6 tasks

handrews changed the title ~~schemas: add WORK-IN-PROGRESS placeholders, don't mention patch numbers, fix terminology~~schemas: add WORK-IN-PROGRESS placeholders, don't mention patch numbers, update terminologyOct 18, 2024

handrews requested review from karenetheridge and ralfhandl October 18, 2024 21:03

ralfhandl previously requested changes Oct 19, 2024
View reviewed changes

ralfhandl self-requested a review October 21, 2024 10:11

handrews added 2 commits October 21, 2024 10:03

Update the schema READMEs for current practice
8e23d02

"base" can't be both a file and a directory
c0f07c9

Merge remote-tracking branch 'upstream/main' into pr/4146
cc1995d

ralfhandl requested changes Oct 22, 2024
View reviewed changes

Comment threadschemas/v3.1/README.md Outdated
Comment threadschemas/v3.0/README.md Outdated
Comment threadschemas/v3.1/README.md Outdated
Comment threadschemas/v3.1/schema.yaml Outdated

This was referenced Oct 22, 2024
Open Community (TDC) Meeting, Thursday 24 October 2024 #4140
Closed
v3.0.4 schema updates #4132
Closed

handrewsand others added 2 commits October 22, 2024 08:26

Link to issue tracking "latest" schema access
b928227

Update schemas/v3.1/schema.yaml
520a7c3
To be consistent with the other YAML files

ralfhandl approved these changes Oct 22, 2024
View reviewed changes

ralfhandl requested a review from a teamOctober 22, 2024 16:16

lornajane approved these changes Oct 24, 2024
View reviewed changes

miqui merged commit cc25d27 into OAI:mainOct 24, 2024

This was referenced Oct 25, 2024
Schema Publish workflow #4162
Merged
Open Community (TDC) Meeting, Thursday 31 October 2024 #4155
Closed

handrews deleted the schema-ids branch March 29, 2025 17:24

handrews added the Schema changes related to the schema(s) label Oct 18, 2024

handrews requested review from a team as code owners October 18, 2024 19:00

handrews mentioned this pull request Oct 18, 2024
Workflow to publish schemas #4139
Closed
6 tasks

handrews changed the title ~~schemas: add WORK-IN-PROGRESS placeholders, don't mention patch numbers, fix terminology~~schemas: add WORK-IN-PROGRESS placeholders, don't mention patch numbers, update terminologyOct 18, 2024

handrews requested review from karenetheridge and ralfhandl October 18, 2024 21:03

ralfhandl previously requested changes Oct 19, 2024
View reviewed changes

ralfhandl self-requested a review October 21, 2024 10:11

handrews added 2 commits October 21, 2024 10:03

Update the schema READMEs for current practice
8e23d02

"base" can't be both a file and a directory
c0f07c9

Merge remote-tracking branch 'upstream/main' into pr/4146
cc1995d

ralfhandl requested changes Oct 22, 2024
View reviewed changes

Comment threadschemas/v3.1/README.md Outdated
Comment threadschemas/v3.0/README.md Outdated
Comment threadschemas/v3.1/README.md Outdated
Comment threadschemas/v3.1/schema.yaml Outdated

This was referenced Oct 22, 2024
Open Community (TDC) Meeting, Thursday 24 October 2024 #4140
Closed
v3.0.4 schema updates #4132
Closed

handrewsand others added 2 commits October 22, 2024 08:26

Link to issue tracking "latest" schema access
b928227

Update schemas/v3.1/schema.yaml
520a7c3
To be consistent with the other YAML files

ralfhandl approved these changes Oct 22, 2024
View reviewed changes

ralfhandl requested a review from a teamOctober 22, 2024 16:16

lornajane approved these changes Oct 24, 2024
View reviewed changes

miqui merged commit cc25d27 into OAI:mainOct 24, 2024

This was referenced Oct 25, 2024
Schema Publish workflow #4162
Merged
Open Community (TDC) Meeting, Thursday 31 October 2024 #4155
Closed

handrews deleted the schema-ids branch March 29, 2025 17:24

Uh oh!

Conversation

handrews commented Oct 18, 2024

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

handrews commented Oct 19, 2024

Uh oh!

ralfhandl commented Oct 21, 2024

Uh oh!

handrews commented Oct 22, 2024

Uh oh!

ralfhandl commented Oct 22, 2024

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

5 participants

Uh oh!

Conversation

handrews commented Oct 18, 2024

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

handrews commented Oct 19, 2024

Uh oh!

ralfhandl commented Oct 21, 2024

Uh oh!

handrews commented Oct 22, 2024

Uh oh!

ralfhandl commented Oct 22, 2024

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

5 participants

Uh oh!

Conversation

handrews commented Oct 18, 2024

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

handrews commented Oct 19, 2024

Uh oh!

ralfhandl commented Oct 21, 2024

Uh oh!

handrews commented Oct 22, 2024

Uh oh!

ralfhandl commented Oct 22, 2024

Uh oh!

Uh oh!

Uh oh!