Recommended general purpose schemas

[denisnazarov]

For mediachain-first data.

[denisnazarov]

If your data is mediachain-first, then presumably it wont have any WKIs at all. What's the best practice here?

EDIT: rfc answers this:

Works that are mediachain-first and require an identifier can either generate one or receive it from a ticket server. This ID will be treated the same way as any other.

[parkan]

Yeah, we haven't built this part yet. Basically we need either

• blockchain-based id generation of some kind (blockchain ticket server)
• provably unique nothing-shared ID generation scheme as juan suggested (UUID-like)

Re: schemas, we should think about the ultimate purpose of the data. A first-pass answer may be just using schema.org schemas.

[denisnazarov]

Def. some good stuff on schema.org like http://schema.org/ImageObject

Can we suggest using schema.org and generating UUIDs for now?

[parkan]

I think recommending schema.org as baseline is fine.

For IDs I am not 100% sure UUID is ideal; something like https://github.com/boundary/flake that uses peerIds instead of MACs could be a better choice (though we should think about what information we want to leak)

[denisnazarov]

ID genrator/flake #57

[parkan]

@yusefnapora this probably falls under documentation scope?

[yusefnapora]

Yup, sounds good.

[parkan]

@yusefnapora what's the status here?

[yusefnapora]

So far I've just got a few paragraphs that amount to "use JSON-LD with schema.org types". I haven't pushed that section to the docs site yet, but I'm planning to get that done today.

[parkan]

@yusefnapora let's try to get this wrapped ASAP, doesn't have to be detailed at this point.

[yusefnapora]

@parkan I just pushed an update to the docs site: https://mediachain.github.io/mediachain-docs/publishing/schema-recommendations#using-json-ld

I think it does a decent job of covering the basics, given the current state of support in the code so far.

[parkan]

Great, that's more than sufficient 😄