Feature Request: Add/standardize blockURIs for all community blocks to simplify migration/improve machine-readability

[qqmyers]

Overview of the Feature Request As reported/documented in #11192, there are metadata blocks that don't define a blockURI (or individual URIs for all fields) which leads to Dataverse instance specific json-ld which is problematic in migrating metadata and machine-reading across instances. It would be a useful improvement to machine readability if all the community blocks had a blockURI.

There are a couple issues w.r.t. possible scope of work on this that should be decided before the issue is prioritized for development:

• Just adding https://dataverse.org/schema/{blockname} as the citation and codemeta blocks currently do would be useful and simple (size 3, 10?)
• Since the https://dataverse.org/schema/* URLs don't currently resolve, it would be nice if they did, i.e. if one could go to that URL to learn about the block and its fields.
  • We could change the base URL to, for example, https://schema.dataverse.org/ to facilitate this, which would mean updating the citation and codemetadata blocks as well (still size 10? just edits to a couple lines in the blocks and documentation of the (backward-incompatible) change).
  • We could create content to populate the URLs we define, hopefully automating creating from the block definition files (size tbd)
• We could explore whether there are better block or field URIs available, e.g. whether DDI-related URIs could/should be used for the social block (size tbd)

Are you thinking about creating a pull request for this feature?
I'd be happy to make block edits and document, but wouldn't have time in the short term for larger changes