Skip to content

SEM-FIB-Schema: Update creationTime to use date-time format [DEMO PR]#23

Draft
GGoetzelmann wants to merge 1 commit intomainfrom
sem-fib-schema_datetime
Draft

SEM-FIB-Schema: Update creationTime to use date-time format [DEMO PR]#23
GGoetzelmann wants to merge 1 commit intomainfrom
sem-fib-schema_datetime

Conversation

@GGoetzelmann
Copy link
Copy Markdown
Contributor

No description provided.

@github-actions
Copy link
Copy Markdown

📋 Schema Check Report

Schema Path: SEM/SEM_schema.json
Tag Prefix: SEM_
Latest Tag for Comparison: SEM_v0.1.0

JSON Schema Check Results

Validate JSON Schema

✅ The schema is valid JSON.

Diff to Latest Release

No difference found to previous version.

Next Steps

  • Fix validation errors
  • Check backwards compatibility based on diff
  • React with 👍 to mark the PR as ready

@github-actions
Copy link
Copy Markdown

📋 Schema Check Report

Schema Path: SEM-FIB_Tomography/SEM_FIB_Tomography_Acquisition_Main.json
Tag Prefix: SEM-FIB_
Latest Tag for Comparison: SEM-FIB_v0.1.1

JSON Schema Check Results

Validate JSON Schema

✅ The schema is valid JSON.

Diff to Latest Release

 {
   $defs: {
     acquisition: {
       properties: {
         dataset: {
           items: {
             properties: {
               images: {
                 items: {
                   properties: {
                     creationTime: {
-                      pattern: "^(\\d{4}-\\d{2}-\\d{2}T\\d{2}:\\d{2}:\\d{2}(\\.\\d+)?Z?)$"
+                      format: "date-time"
                     }
                   }
                 }
               }
             }
           }
         }
       }
     }
   }
 }

Tip

To check schema backwards compatibility, you may use any AI chatbot with a prompt like:

Assuming I have two JSON schemas, both are different according to the following diff, are both schemas compatible?
<PASTE_DIFF_HERE>

If you like, you may add additional rendering instructions, e.g.:

Render the result as table showing the changed attributes, a columns to check backward compatibility, > and a column to provide comments on why a certain property is not backwards compatible.

Furthermore, you can also use the diff to get a hint on which schema version to use next:
Assuming I have a JSON schema in version 1.0.0 and the next version has the following changes in diff format. Which would be the next version number following semantic versioning principles?
<PASTE_DIFF_HERE>

Next Steps

  • Fix validation errors
  • Check backwards compatibility based on diff
  • React with 👍 to mark the PR as ready

@github-actions
Copy link
Copy Markdown

📋 Schema Check Report

Schema Path: APE-HE/APE_HE_Schema.json
Tag Prefix: APE-HE_
Latest Tag for Comparison: APE-HE_v0.1.0

JSON Schema Check Results

Validate JSON Schema

✅ The schema is valid JSON.

Diff to Latest Release

No difference found to previous version.

Next Steps

  • Fix validation errors
  • Check backwards compatibility based on diff
  • React with 👍 to mark the PR as ready

@github-actions
Copy link
Copy Markdown

📋 Schema Check Report

Schema Path: CT/lab_CT.json
Tag Prefix: CT_
Latest Tag for Comparison: unavailable

JSON Schema Check Results

Validate JSON Schema

✅ The schema is valid JSON.

Diff to Latest Release

No previous schema version found.

Next Steps

  • Fix validation errors
  • Check backwards compatibility based on diff
  • React with 👍 to mark the PR as ready

@github-actions
Copy link
Copy Markdown

📋 Schema Check Report

Schema Path: TEM/TEM_schema.json
Tag Prefix: TEM_
Latest Tag for Comparison: TEM_v0.1.0

JSON Schema Check Results

Validate JSON Schema

✅ The schema is valid JSON.

Diff to Latest Release

No difference found to previous version.

Next Steps

  • Fix validation errors
  • Check backwards compatibility based on diff
  • React with 👍 to mark the PR as ready

@github-actions
Copy link
Copy Markdown

📋 Schema Check Report

Schema Path: MRI/MRI_schema.json
Tag Prefix: MRI_
Latest Tag for Comparison: MRI_v0.1.0

JSON Schema Check Results

Validate JSON Schema

✅ The schema is valid JSON.

Diff to Latest Release

No difference found to previous version.

Next Steps

  • Fix validation errors
  • Check backwards compatibility based on diff
  • React with 👍 to mark the PR as ready

@GGoetzelmann GGoetzelmann changed the title SEM-FIB-Schema: Update creationTime to use date-time format SEM-FIB-Schema: Update creationTime to use date-time format [DEMO PR] Nov 21, 2025
@GGoetzelmann GGoetzelmann marked this pull request as draft November 21, 2025 11:16
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.

1 participant