Skip to content
This repository has been archived by the owner on Aug 2, 2024. It is now read-only.

Feature Request: Collaborative Evaluation #340

Open
AutoSponge opened this issue Mar 23, 2020 · 4 comments
Open

Feature Request: Collaborative Evaluation #340

AutoSponge opened this issue Mar 23, 2020 · 4 comments
Labels
documentation feature: Audit Step 4: audit feature: Import priority 3 Low priority issue

Comments

@AutoSponge
Copy link

As a member of an evaluation team or as a member of a community crowd-sourcing an evaluation, I would like the ability to work on the same, persisted document as other reviewers.

I'm eager to see if there's support for this feature request as well as the ideas that come out of a discussion.
@AutoSponge
Copy link
Author

Idea 1:

Scope

  • Report Tool will accept a semantic "REST" endpoint as the "storage" option for a report.
  • Report Tool will assume OAuth2 workflow for protected endpoints.
  • Report Tool will communicate with the endpoint on "load" and "save" actions.
  • Report Tool creates pre-conditions based on Etags (conflict resolution on write).

Requirements

  • Definition of the appropriate mime type(s): application/earl+json or application/ld+json etc.
  • A spec (mostly referencing HTTP behaviors) for the server.
  • Coding OAuth2 behavior into Report Tool client.
  • Coding endpoint communication into Report Tool client.
  • Coding sample spec-compliant server or appropriate mock for testing.

@juleskuehn
Copy link

I assume this wouldn't be part of the hosted functionality on w3.org but yes, our testing team is very interested in this as well.

@AutoSponge
Copy link
Author

@juleskuehn Right. I assume the reference server or spec would provide a framework to build your own implementation from. As long as the server is compliant, any authorized user could theoretically use any client to add a report (or, more likely use the default client served by the server).

@rvantonisse
Copy link
Collaborator

rvantonisse commented Mar 27, 2020 •
edited
Loading

Report Tool will accept a semantic "REST" endpoint as the "storage" option for a report.

There is already something similar in place. It is handled by the reportStorage service.

Essentially you need to add autosave="true" with an url url="withyour.reporting-tool.com/api" to the approot in the index.html to send and get data from the backend like this:

<body ng-app="wcagReporter" autosave url="myReporter.com/report/1">

Where report would be the API and /1 the report ID.

But the backend API to store the reportdata is something you would have to build by yourself.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees
No one assigned
Labels
documentation feature: Audit Step 4: audit feature: Import priority 3 Low priority issue
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@AutoSponge @juleskuehn @rvantonisse