Consider a unified interface with pySHACL

未关闭
#24 1 条评论 0 个 reaction 已指派 0 人 在 GitHub 查看

还没有人认领这个 Issue。

评估

难度
5/5
预计耗时
一周以上
新手友好度
15/100
Issue 类型
功能
描述清晰度
需要澄清
活跃度
停滞
技术栈
jupyter-notebook, python
领域
backend

调研方向

Start by reading the PyShEx project entry points and the linked pySHACL and pyshacl-webservice projects to understand the proposed interface and deployment options. The issue does not specify what to change or define an acceptance criterion; a concrete interop plan and a decision about hosting a PyShEx instance would be needed before implementation can be considered done.

由索引模型根据 Issue 内容生成。

描述

Hi PyShEx team,

We've just released an almost completely fully-functioning Python SHACL validator, pySHACL and its been suggested that we work with you to consider a unified interface or some sort of interop.

We are about to set up a web service public instance of pySHACL for people to use much like the SHACL playground. Would you be keen for us to set up an instance of PyShEx alongside it? To to this we might create a basic web UI for PyShEx, as we've done for pySHACL unless you already have one we could use?

Once we have side-by-side public instnaces up, unless there's a reason not to do this, we could work out a timeline for interop if people are interested.

Cheers,

Nick
Nicholas Car
CSIRO, Australia

主要语言
Jupyter Notebook
星标
29
派生
16
平均合并
20 小时 57 分钟
30 天内合并 PR
9

环境准备

这个项目没有提供开发容器、Dockerfile 或贡献指南,环境需要你自己搭建:先看它的 README,通用步骤见我们的新手贡献指南。

从这里开始

  1. 先读完整个 Issue,再读项目的贡献指南。
  2. 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
  3. Fork 仓库,在一个分支上完成修改。
  4. 提交 Pull Request,并在描述里引用这个 Issue 编号。

linkml/PyShEx 的其他 Issue

查看 linkml/PyShEx 的全部 Issue

相似的 Issue

更多 Backend & API Design Issue

把新 issue 发到你的邮箱

精选适合新手参与的 GitHub issue 摘要。