OAv3 context update schedule

[Fak3]

Hi. What is the schedule of deploying the OAv3 context file from this github repo to
https://schemata.openattestation.com/com/openattestation/1.0/OpenAttestation.v3.json ?

[jley81]

How about now? Would that work for you

…

On Wed, Jun 23, 2021, 2:18 AM Evstifeev Roman ***@***.***> wrote: Hi. What is the schedule of deploying the OAv3 context file from this github repo to https://schemata.openattestation.com/com/openattestation/1.0/OpenAttestation.v3.json ? — You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub <#186>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/APHTLUYCCCJBKZUJCFIUE43TUGDFLANCNFSM47FF3AIQ> .

[Fak3]

Sure, thanks in advance.

[Nebulis]

I'm sorry to disappoint you but jley81 does not work on open attestation

I need to check why the file is in this repo and deployed somewhere else i will check tomorrow maybe

[jley81]

What do I do? I dont know how.

[Nebulis]

Deployed :)

[Nebulis]

Ok it works for this property, now the problem moved to identityProof. I tried to add like you did for openAttestationMetadata, but it only works if I add a type property in openAttestationMetadata like this : type: ["OpenAttestationCredential"]

By doing this the problem now move to identifier property.

I'm not really familiar with json-ld, but does that mean that for every object I will need to add a type property for a definition to apply ? Or am I doing wrongly

[Fak3]

identityProof should be in the nested context under openAttestationMetadata: Open-Attestation/schemata#29

[Nebulis]

Ok I see, I get a rough idea how to fix the rest. Thanks for your help I will ping you if I face other issues 👍

[Nebulis]

@Fak3 any idea what's different with the issuer property? I can't validate the issuer.name. You can check the latest version https://schemata.openattestation.com/com/openattestation/1.0/OpenAttestation.v3.json

[Fak3]

That is a limitation of json-ld syntax: w3c/json-ld-syntax#361

It is possible to do with type-scoped context, if the issuer will have "OpenAttestationIssuer" type assigned: Open-Attestation/schemata#30

But I am unsure if it is a good idea to put this in the context. As a VC creator, I would prefer to customize the full url for issuer.name field in my own custom context so that I can give it more specific semantics, like restricting allowed characters, or omit it completely, only requiring an "id".