`getThing` should support `name` as well as `url` like `createThing` does

Search terms you've used

getThing

Feature suggestion

I find myself creating named Things a lot, and relying on the client / server to set the base url to match a given resource when I save the resource. However, when I go to get those Things back out of the dataset, I can no longer solely use the name, I have to also use the base url to construct the full URL identifier for that Thing.

I often pass datasets around the code, and want to refer to Things in that dataset by name without also having to keep track of where that dataset was from. While I could do it myself using getSourceUrl, it seems like the SolidDataset should also have the information to just accept a string and do that conversion for me.

Expected functionality/enhancement

getThing can be called with either the name relative to the base IRI of the dataset, or the full url

getThing(dataset, "name")) === getThing(dataset,`${getSourceUrl(dataset)}#name`)

I would be happy to implement this if there is support for it, but it seems like it might be a controversial API choice, so wanted to open the issue to chat about it first. Personally, I think for pure feature parity, if createThing supports name, then getThing should as well.

Start by locating the getThing, createThing, and getSourceUrl entry points in the TypeScript library and compare how they handle names and full URLs. Confirm the expected behavior with the issue's equality example, then add coverage showing that a relative name resolves against the dataset base IRI while a full URL continues to work.