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

define uri standard #3

Open
ttm opened this issue Feb 12, 2016 · 0 comments
Open

define uri standard #3

ttm opened this issue Feb 12, 2016 · 0 comments

Comments

@ttm
Copy link
Owner

ttm commented Feb 12, 2016

the construction of uris in social, gmane and participation packages have many subtleties sorted out in code.

Of these, one remained until now: the uris of individuals for the most important entities should have the snapshotid in it or not?

Cons of using the snapshotid in the uris: the uri gets larger (and so the final data). Same entities are not directly related if they are present in different snapshots (they have to be related through IDs).

Pros of using the snapshotid in the uris: data from each snapshot does not get mixed. For example, a twitter user can have different screennames in different snapshots. The information about which snapshot each screenname is related to is lost in the final linked data.

This last difficulty can be overcome by the use of named graphs (alias "conjunctive graph contexts") and the RDF link between the instances and the snapshoturi.
Support for named graphs has some drawbacks in real usages,
such as the current inability in Fuseki/Jena for creating new named graphs on the fly and reasoning about them (the reasoner has to be loaded at startup for each graph).

The currently adopted "solution" is not to use the snapshotid in the uris.

@ttm ttm changed the title define uri convention define uri standard Feb 12, 2016
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant