Consider a unified interface with pySHACL

未關閉
#24 1 則留言 0 個 reaction 已指派 0 人 在 GitHub 檢視

維護者通常 1 天內回覆

還沒有人認領這個 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 摘要。