Delete renamed classes from JSON-LD context?

[marcolarosa]

I'm creating a profile in describo to drive the UI from schema.org. In that process I rename all instances of MediaObject to File so the user can't add / associate a type of MediaObject; rather, they only get the option to add / associate a File. However, the RO-crate context has an entry for File and MediaObject.

So:

• should I actually add File as an option to any location a user can use MediaObject (ie they could choose to add a File or a MediaObject)? or
• should the crate context only list File?

I guess this holds true for other examples that have been renamed but I haven't come across any myself.

[stain]

I think we only keep MediaObject because it is in the original context - it's not deleted.

https://github.com/ResearchObject/ro-crate/blob/master/docs/1.1/context.jsonld#L603

Perhaps it should be deleted? This could also help JSON-LD flattening so it does not accidentally pick the other one, and our spec do say it is renamed.

The renames from PCDM are only there in the renamed variant:

          "RepositoryCollection": "http://pcdm.org/models#Collection",
          "RepositoryObject": "http://pcdm.org/models#object",

In addition Journal is renamed from Periodical, but it is also there natively:

          "Journal": "http://schema.org/Periodical",
          "Periodical": "http://schema.org/Periodical",

[marcolarosa]

My code is renaming classes so MediaObject cannot be added via describo but File can. That said, when flattening it could come out as either as you rightly point out.

You mention Journal being renamed. I didn't know that. Is there an authoritative list of these renames in the documentation that I can consult?