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

Add ability to track agent separately from instrument in assertions #23

Open
AleitaT opened this issue Jun 18, 2021 · 1 comment
Open

Comments

@AleitaT
Copy link

AleitaT commented Jun 18, 2021

Currently, assertion object information is limited and lacks complete context to tell from where and from who the assertion was generated. This has largely been due to the nature of the information being very nearby or in the same system, so we knew where it came from. As assertion processing and environments expand and grow, it makes sense to provide more information to enable other systems to use this data to tell both a) how it was created (what system, tool, etc) and b) whom (system, or person) generated this assertion.

For example:
Kristen asserted X about Y using instrument VLRC
Moodle asserted X about Y from instrument MoodleAssessment
Salesforce asserted X about Y from instrument AssertionBot

https://schema.org/instrument
schema:instrument

@Lomilar
Copy link
Member

Lomilar commented Jun 18, 2021

Instrument can be harvested from the evidence (if it came in via xAPI, the xAPI statement may somehow tell the system where it came from) but this is more explicit. I don't know how the instrument would be used downstream, but +1.

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

No branches or pull requests

2 participants