Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Link multiple identifiers to same object (owl:sameAs?) #48

Open
joachimvh opened this issue May 5, 2021 · 2 comments
Open

Link multiple identifiers to same object (owl:sameAs?) #48

joachimvh opened this issue May 5, 2021 · 2 comments

Comments

@joachimvh
Copy link
Member

Issue type:

  • ➕ Feature request

Description:

It could be useful to have a way to link to the same object with multiple identifiers. Example below from the community solid server:

For the CSS config I was thinking of having separate config files for every class that would be instantiated. This way you could have intermediate configs that only import the classes that are needed for a config, which would make it easy to create new combinations of classes without having to copy/paste potentially large blocks. E.g., monitoring-store.json would just contain

    {
      "@id": "urn:solid-server:default:MonitoringStore",
      "@type": "MonitoringStore",
      ...
    },

The one issue with this that some components are referenced by several other classes. One of these is the urn:solid-server:default:ResourceStore. In practice this is a MonitoringStore, so two options I see are:

  • Create a new config file monitoring-store-default.json where the identifier is set to that one instead. This would place more work on people who want to make new combinations of the configs though.
  • Change all config files that reference urn:solid-server:default:ResourceStore. Definitely would not do this since this would require a lot of changes every time.

It would be nice if I could just write urn:solid-server:default:ResourceStore owl:sameAs urn:solid-server:default:MonitoringStore since that only requires a single change there for new configs.

Note that in practice the first option would not be that horrible right now as the changes are still not that drastic, but I do think the sameAs solution might also be helpful in several other situation to streamline configurations.

@github-actions
Copy link

github-actions bot commented May 5, 2021

Thanks for the suggestion!

@rubensworks
Copy link
Member

Easiest place to add this would be in https://github.com/rubensworks/rdf-object.js
So some node squashing mechanism would be needed there.

We do have to think about how we want to handle multiple sameAs usages, and how to report errors/warnings on resources with multiple id's.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants