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

Resolvers... #101

Open
2 of 11 tasks
jpstroop opened this issue Sep 29, 2016 · 1 comment
Open
2 of 11 tasks

Resolvers... #101

jpstroop opened this issue Sep 29, 2016 · 1 comment
Labels

Comments

@jpstroop
Copy link
Owner

jpstroop commented Sep 29, 2016

I want to know all of the resolvers that this server supports.

  • /resolvers should be an extension that is added to the profile
  • Maybe /resolvers should be /resolvers.json (/resolvers could redirect) 160de37
  • Each resolver instance should have a documentation string that is set in the config 160de37
  • It should be possible to make a resolver a secret, excluding it from the list at /resolvers
  • If all resolvers are a secret, /resolvers.json should 404
  • The response should be JSON-LD
    • The subject should be the server
    • The predicate should be ? (loris:hasResolver?)
    • The Range of ⬆️ should be an a loris:Resolver``@type
    • The object be the base URI + the resolver prefix, e.g. https://myserver.edu/xyz:
  • yup.
@jpstroop
Copy link
Owner Author

context stub:

{
  "@context": {
    "loris": "http://loris.io/features/3#",
    "xsd": "http://www.w3.org/2001/XMLSchema#",
    "dcterms": "http://purl.org/dc/terms/",

    "prefix": {
      "@id": "loris:resolverPrefix",
      "@type": "xsd:string"
    },
    "description": {
      "@id": "dcterms:description",
      "@type": "xsd:string"
    }
  }
}

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

1 participant