YAML-LD proposal

[anatoly-scherbakov]

Fixes #871

[TallTed]

Small changes

[BigBlueHat]

@anatoly-scherbakov I like where this is headed! I think we may need a conversation (here or on a call) about how to explain YAML-LD and CBOR-LD to the wider developer community. I thing "spin-offs" is a good way to start, but it does beg the question of what are these things...and what is this ecosystem?

Should developers expect JSON-LD to work like a "hub" format? or could one expect to go from CBOR-LD to YAML-LD (and vice versa)?

We don't have those answers yet. 😉 And I don't want to delay getting more content on the site, so I'm generally 👍 to what you're proposing here. Just noting we may need to rework it again soon to explain all the things as we grow in our own understanding of them. 😸

[BigBlueHat]

This is off to a great start! I think we may want to consider having top-level folders for /yaml-ld/ and /cbor-ld/ rather than putting them in the Learn section...but I'm on the fence about that.

Overall, it's great to see this content showing up, and I think this is a good way to start.

Happy to help you rework it if/as we hear from others about where best to put this content longer term.

[BigBlueHat]

Feel free to just remove stuff rather than comment it out.

[anatoly-scherbakov]

Thought maybe there are tools that I missed and we could quickly get them back :) But generally yes I agree, I'll see into doing a cleanup in one of the follow up PRs.

[anatoly-scherbakov]

how to explain YAML-LD and CBOR-LD to the wider developer community. I thing "spin-offs" is a good way to start, but it does beg the question of what are these things...and what is this ecosystem?

I thought of introducing a notion of *-LD, Asterisk-LD. Anything-LD, basically. Which means that basically any data format can be interpreted in a semantic way.

Having said that,

Should developers expect JSON-LD to work like a "hub" format? or could one expect to go from CBOR-LD to YAML-LD (and vice versa)?

…I think conversions among all the possible *-LD formats would very quickly become very astronomical in complexity if we want to add more such formats, so I suppose JSON as a middle ground among them all can be a handy thing.

Just noting we may need to rework it again soon to explain all the things as we grow in our own understanding of them.

Most definitely, the only constant is change. Incidentally that rhymes with what I've been thinking lately about what the purpose of LD is: I think it might be formulated as "accelerate change to knowledge while preserving its consistency".

I think we may want to consider having top-level folders for /yaml-ld/ and /cbor-ld/ rather than putting them in the Learn section...but I'm on the fence about that.

I suppose we can do so when we get more materials to publish maybe. Like, I am researching applications of YAML-LD for Nanopublications. We will need use cases and usage examples to lure people into using our technology so as we can be proud of ourselves that someone uses our stuff.