Suggestion: schema-based RDF without blank nodes

Overview of the Suggestion
I would like to propose an alternative schema.org RDF file, without all the blank nodes currently in JSON-LD.

What kind of user is the suggestion intended for?
API User, Curator

What inspired this idea?

• the need to combine metadata from Dataverse with metadata from library, collections and archival systems;
• the wish to use SHACL to check for basic evaluation of data, across afore mentioned systems;

What existing behavior do you want changed?

• the current JSON-LD RDF schema creates many blank nodes (a downside of converting JSON to RDF). This conflates the number of triples and therewith hampers communication across the web. Moreover, it hinders linking of datasets to persons as for each value of a person's name, a new blank node is created and there is no way of knowing which blank node belongs to what person;

Any brand new behavior do you want to add to Dataverse?

• no, I think all the technical features are in place. Also, many of the vocabulary decisions to map Dataverse to schema.org have already been made via the current JSON-LD implementation. I do think the end result would need to be served via an additional API

Any open or closed issues related to this suggestion?

• https://github.com/IQSS/dataverse/issues/9613 (open)

Are you thinking about creating a pull request for this issue?
I could help implement it with help. I know of the Linked Data/Schema part, but would need help with the API. With some mentoring I could come a long way.

Start by reviewing Dataverse's current JSON-LD implementation and related issue #9613. Determine the API entry point for an additional schema-based RDF representation without blank nodes, then define how its output supports SHACL checks and links datasets to persons. Done means the scope, API behavior, and validation expectations are agreed.