search

json-ld / yaml-ld

CG specification for YAML-LD and UCR
https://json-ld.github.io/yaml-ld/spec
Other
19 stars 8 forks source link

#81 The YAML-LD Primer #82

Closed anatoly-scherbakov closed 4 weeks ago

anatoly-scherbakov commented 1 year ago

This is very much a draft.

I decided to push it however to show how we maybe could visualize RDF graphs.

image

This image is generated using Cytoscape JS library. The nodes and edges should be clickable. What do you think of the idea itself?

Perhaps there is some off-the-shelf JS visualization tool for RDF that we could use?

Preview | Diff

TallTed commented 1 year ago

I would expect this to eventually be published as a non-normative a/k/a informative NOTE, so there's probably little point to keeping this PR of a new document in draft, nor even in keeping this as a PR, once @anatoly-scherbakov feels comfortable opening it up to full review and input by/from CG and/or WG.

Active content is neither globally forbidden nor globally permitted, especially in NOTE space. It should be carefully considered, as many people prefer to print things, but when used well, I think it may fit well into a Primer or similar NOTE.

anatoly-scherbakov commented 1 year ago

@TallTed I agree that, if done, this document must be non normative.

I am not entirely clear though whether you propose to factor this out as a separate document right away? Instead of having it as part of the spec for the time being.

gkellogg commented 1 year ago

Looks like this got lost, as it targets a branch already merged. You may need a new PR to re-target it.

TallTed commented 1 year ago

@anatoly-scherbakov -- To my mind, having the Primer treated as its own doc (doesn't need to be a separate repo) from inception is best. Given that json-ld/yaml-ld#80 (which holds the branch you forked from) has been merged, requiring this to be rebased against main at minimum, I'd suggest that you break into that distinct doc now.

ioggstream commented 1 year ago

having the Primer treated as its own doc (doesn't need to be a separate repo) from inception is best

+1 to integrate in a separate repo, unless there's specific need to visually represent a graph to clarify the spec content.

Didn't know cytoscape. Looks cool.