Thanks to visit codestin.com
Credit goes to github.com

Skip to content

Standardization? #27

@scottslewis

Description

@scottslewis

Greetings.

First, my compliments on your work on jsog. It seems that these days all I see are use cases for serializing/deserializing object graphs (trees, lists of object references, etc) to/from json...ideally without binding to a particular language, impl on server or client, or ser/deser library.

Question 1

With all the work around json schema has there been any standardization effort around this approach for standardization (e.g. of the @id name and type of value)?

The reason I ask is that I'm proposing an enhancement to the model context protocol (which is based upon json/json schema for protocol specification), that uses object graphs to represent Groups of Tools, Resources, Prompts. Part of this will likely be the need for all mcp sdks to support the same approach to dealing with object graphs...at least wrt Groups (which are collections of other schema-defined objects by definition, and so therefore use object references/graphs).

Question 2

I'm an experienced open source project lead for 20+ years and have contributed to specifications (osgi) and to many framework implementations. If desired, I would be willing to contribute (e.g.) other language impls of jsog so that it could be used to support all of the mcp sdks.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions