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

Create a per-provider Turtle file to describe the provider #1059

Open
kjetilk opened this issue Jan 22, 2019 · 3 comments
Open

Create a per-provider Turtle file to describe the provider #1059

kjetilk opened this issue Jan 22, 2019 · 3 comments
Labels
inrupt-planning Issues that Inrupt will consider when planning development cycles

Comments

@kjetilk
Copy link
Member

kjetilk commented Jan 22, 2019

Per the discussion in solid-contrib/information#16 , we should make a Turtle file per provider, where the provider may describe themselves and their policies. They could then submit their URL to POD provider registries and it could then be scuttered to provide such a list.

@kjetilk kjetilk added the inrupt-planning Issues that Inrupt will consider when planning development cycles label Jan 22, 2019
@megoth
Copy link
Contributor

megoth commented Jan 22, 2019

Should we expand the Solid vocabulary or are there existing vocabularies that might cover our need?

@kjetilk
Copy link
Member Author

kjetilk commented Jan 22, 2019

Not sure, but I think we can use a lot from Dublin Core and friends.

@megoth
Copy link
Contributor

megoth commented Feb 14, 2019

Perhaps the resource describing the provider should be a virtual resource, and be automatically generated? I reckon trustedOrigins could be an interesting list to expose (cf #1090)?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
inrupt-planning Issues that Inrupt will consider when planning development cycles
Projects
None yet
Development

No branches or pull requests

2 participants