ga4gh / ga4gh/phenopacket-schema

JSON schema and entity resolution

Open
#267 6 comments 0 reactions 0 assignees View on GitHub
Dominant language
Java
Stars
101
Forks
34
PR merge metrics
No merged PRs in 30d

Description

Protobuf isn't compatible with JSON schema-based projects such as Search/Beacon so they rely on a second-hand Schemablocks representation of some elements.

Ideally pehnopackets should be directly discoverable and useable in JSON schema projects with its own namespace e.g. schema.org findability.

@jfuerth, can you expand on this?

Contributor guide

Open the contributing guide

Research direction

Start with the issue description and clarify how Phenopackets should relate to Protobuf, Schemablocks, JSON Schema, and schema.org. Define the namespace and representation needed for direct discoverability and usability in JSON schema projects; the work is done when that design is agreed and implemented.

Written by the indexing model from the issue text.

Assessment

Tech stack
json
Domain
backend-api-design
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.