-
Notifications
You must be signed in to change notification settings - Fork 12
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
Indirect collections #63
Comments
Another use case is where I don’t at all have a collection / membership defined in a file, but I still want to indicate from a previous file how to set the targets of the member extraction algorithm. This could be useful to make regular files or data dumps more easily part of the TREE ecosystem by providing a bit of external context. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
User stories and problems
dcat:Catalog
withdcat:Dataset
s, I want to paginate the catalog in different ways, to find dataset objects without having to redefine adcat:Catalog
as atree:Collection
with tree:membersPossible solution
In order to cover US1, we’d need a way to merely describe the containment property. The rest can be automatically inferred.
E.g.:
:Catalog a dcat:Catalog; dcat:dataset :A, :B, :C .
If we add 1 triple or header saying:
Then we can infer that
:Catalog
is atree:Collection
, and the current@base
is adcterms:isPartOf
the:Catalog
. The<>
can then be extended with tree:Relations and the likes.In order to tackle US2 and US3 we can work with a default value: we can maintain a list of a default containment path that must be checked. This can be for example:
:Collection tree:containmentPath [sh:alternatePath (tree:member as:item hydra:member ldp:contains) ]
ISSUE: for AS2, the items are contained on a view, and not on the collection. How do we deal with that?
The text was updated successfully, but these errors were encountered: