WIP

Microservice that

1. takes id of distribution in endpoint?id=... and lookes up access-url or download-url (assumes particular mu-cl-resources config)
2. runs shexer on result (sparql endpoint or remote file)
3. writes resulting graph under sh:shapesGraph (assumes particular mu-cl-resources config)

todo

• make independent of mu-cl-resources

• agree upon better name (as service matures)

• restrict microservice to (2) only? Logic of 1 & 3 somewhere else..?

• asynchronous?

  • immediately respond with a report id
  • with report id, you can request status of job (completed/busy (+logs so far))