Skip to content

Add Okyline to similar technologies#2408

Open
pmbret01 wants to merge 1 commit into
json-schema-org:mainfrom
pmbret01:patch-1
Open

Add Okyline to similar technologies#2408
pmbret01 wants to merge 1 commit into
json-schema-org:mainfrom
pmbret01:patch-1

Conversation

@pmbret01

@pmbret01 pmbret01 commented Jun 3, 2026

Copy link
Copy Markdown

I'm the author and maintainer of Okyline, an open specification. This page invites suggestions of other technologies with similar goals, so I'm proposing to add it.

What kind of change does this PR introduce?
It proposed to add one entry (Okyline) to the Similar Technologies list.

Issue Number:
None. There's no related issue; this follows the page's invitation to submit relevant technologies via a pull request.

Summary
Adds Okyline to the Similar Technologies list. Okyline is an open, example-driven language for describing and validating JSON data. It expresses both the structure and the cross-field business invariants of the data in a single contract, with built-in versioning and cross-schema composition. Specification (CC BY-SA 4.0): https://github.com/Okyline/okyline-spec

Does this PR introduce a breaking change?
No.

Checklist

I'm the author/maintainer of Okyline. As this page invites suggestions of other technologies with similar goals, I'm proposing to add it. Okyline is an open, example-driven language for describing and validating JSON data, expressing structure and cross-field business invariants in a single contract.
@pmbret01 pmbret01 requested a review from a team as a code owner June 3, 2026 20:46
@github-project-automation github-project-automation Bot moved this to Ready to review in PR - Triage Group Jun 3, 2026
@github-actions

github-actions Bot commented Jun 3, 2026

Copy link
Copy Markdown

Hi @pmbret01! Thanks a lot for your contribution!

I noticed that the following required information is missing or incomplete: issue reference

Please update the PR description to include this information. You can find placeholders in the PR template for these items.

Thanks a lot!

@github-actions

github-actions Bot commented Jun 3, 2026

Copy link
Copy Markdown
built with Refined Cloudflare Pages Action

⚡ Cloudflare Pages Deployment

Name Status Preview Last Commit
website ✅ Ready (View Log) Visit Preview 722f7aa

@codecov

codecov Bot commented Jun 3, 2026

Copy link
Copy Markdown

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 100.00%. Comparing base (904bb59) to head (722f7aa).
⚠️ Report is 5 commits behind head on main.

Additional details and impacted files
@@            Coverage Diff            @@
##              main     #2408   +/-   ##
=========================================
  Coverage   100.00%   100.00%           
=========================================
  Files           31        31           
  Lines          695       695           
  Branches       215       215           
=========================================
  Hits           695       695           

☔ View full report in Codecov by Harness.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:
  • ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
  • 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

@pmbret01

pmbret01 commented Jun 3, 2026

Copy link
Copy Markdown
Author

I didn't add a related issue. I'm just following the page's own invitation to submit relevant technologies directly through a pull request. I can open a tracking issue first if you'd prefer.

@github-actions

github-actions Bot commented Jun 3, 2026

Copy link
Copy Markdown

Hi @pmbret01! Thanks a lot for your contribution!

I noticed that the following required information is missing or incomplete: issue reference

Please update the PR description to include this information. You can find placeholders in the PR template for these items.

Thanks a lot!

@vtushar06

Copy link
Copy Markdown
Collaborator

Hey @jdesrosiers, any thoughts on this?

@jdesrosiers

Copy link
Copy Markdown
Member

I guess I don't have a problem with adding it, but in general, I think this page is something we should probably remove because we don't have the capacity to maintain it properly. There are plenty of others that probably should be listed and their absence is a clear indicator how unmaintained that list is.

@vtushar06

Copy link
Copy Markdown
Collaborator

Got It then we can leave this for now.

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

Projects

Status: Ready to review

Development

Successfully merging this pull request may close these issues.

3 participants