-
Notifications
You must be signed in to change notification settings - Fork 19
Issues: solid/data-interoperability-panel
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
Author
Label
Projects
Milestones
Assignee
Sort
Issues list
Add a predicate to link
AccessDescriptionSet
with AccessNeedGroupDescription
and AccessNeedDescription
#323
opened Mar 4, 2024 by
srosset81
User facing information should be rdf:langString, not xsd:string
#322
opened Dec 7, 2023 by
pchampin
Fault in example for the Solid-Interoperability Specification
#319
opened Nov 3, 2023 by
Mikkel-Boje
Do clients really need access to their Grants/Authorizations?
#315
opened Jul 28, 2023 by
woutermont
Reconsider pros and cons of advertising the Registry Set in user's WebID
#312
opened Jun 21, 2023 by
elf-pavlik
Only one Data Registration per shape tree in the Data Registry
#307
opened Apr 4, 2023 by
elf-pavlik
[UX] Presenting multiple data registries to the user (mostly label)
#294
opened Jan 16, 2023 by
elf-pavlik
Deactivating registrations
agent-registration
data-authorization
#293
opened Jan 9, 2023 by
elf-pavlik
Separate
SocialAgent
as Person
, SocialGroup
, and Organisation
#282
opened Oct 21, 2022 by
coolharsh55
Consider changing
AccessNeed
and related concepts with Purpose
#281
opened Oct 21, 2022 by
coolharsh55
Define Rejection Records
agent-registration
data-authorization
#278
opened Sep 28, 2022 by
elf-pavlik
Add semantic information to shape trees to discriminate between different resource classes
#277
opened Sep 22, 2022 by
Giacomo-Papaluca
Previous Next
ProTip!
Updated in the last three days: updated:>2024-08-20.