This is a preliminary technical workflow proposal for assertions, which would be needed for badges, endorsements, and other ideas. It is based on thoughts that I had listening to the badges session at Indiewebcamp NYC 2018.
Scenario 1: Individual creates criteria and wants to assert that other individual has achieved said criteria. Example: Professor wants to certify students completed coursework.
- Professor Posts Criteria for Each Achievement as a unique page (A).
- Student completes assignment as a post (B).
- Professor Posts Badge/Assertion/Endorsement post on their website as an h-review, with a p-item property to student’s URL (B). Would need a new or existing property to represent the relationship to the original assertion (A).
Suggest u-assert and u-assert-of?j Can use u-in-reply-to possibly.
Scenario 2: Individual creates assertion post and solicits others to endorse that statement as factual.
- Individual makes a post to their site(h-resume for references on a resume, not sure what to request endorsement of a statement? p-assert with a nested h-item?) and invites other individuals(using existing invitee property used for RSVPs?) to endorse or assert it. Criteria might be included for achievement.
- Others create ‘assertion’ posts on their site(
assert-of) and send webmentions, which would cause the post to be updated to note that it had been achieved.
Existing microformats for h-resume and h-review seem to allow additional context.
- Education
- Experience
- Skill
- Rating
- Best
- Worst
Brainstorming on the Indieweb wiki under assertion.
