You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I was wondering if it makes sense to rename endpoint_url to something else. There are two reasons for that:
There isn't really an endpoint in LDF ideas, as all resources can serve equally well as a starting point. So, the URL given as parameter here has no special significance, as opposed to a SPARQL endpoint.
I'm thinking it could actually be a source of technical problems, as a model may compose many stores, and then, one might have to do conflict resolution. OTOH, it might be convenient to have the same name for practically similar things, so it is not such a weighty argument. But my gut feeling it would make things easier if it was named differently.
So, I suggest renaming the attribute start_url or something. Goes for the Attean store too.
The text was updated successfully, but these errors were encountered:
I was wondering if it makes sense to rename endpoint_url to something else. There are two reasons for that:
So, I suggest renaming the attribute start_url or something. Goes for the Attean store too.
The text was updated successfully, but these errors were encountered: