search

1EdTech / openbadges-discussion

A no-code repository for having discussions related to the general technical issues of openbadges.
10 stars 3 forks source link

Re-introduce badge version into standard #12

Closed threeqube closed 7 years ago

threeqube commented 10 years ago

As per discussion in https://github.com/mozilla/openbadges-directory/issues/1#issuecomment-36132397 think about badge class versioning:

via @kayaelle "There's really no way to prevent changing the badge class. There's been some discussion of baking the badge class into the badges. That would atleast timestamp the badge data. If the badge class was baked into a badge as well as contain a version - that could inform the directory and save some work. Granted - issuers may not always update their versions but I think a directory would give them incentive to do so. (maybe)."

iamjessklein commented 10 years ago

Wondering if this would be particularly relevant as we now have the concept of templates and building off of a template. Seems like if we don't have versioning it could quickly escalate into confusion, particularly if a user doesn't change the badge title.

threeqube commented 10 years ago

@iamjessklein totally. @cmcavoy @brianloveswords @christensenep @andrewhayward thoughts?

ottonomy commented 10 years ago

Even with the recent discussion on #11 around extensions, badgeClass versioning doesn't seem like a good fit for an extension, although it could totally be executed that way.

Also, issuers also need education to know that if they should not overwrite previous badgeclasses that have issued badges when making new versions. Should probably make sure to teach BadgeKit to guide users through a process of duplicating and editing (with whatever standard method for connecting the classes together) as a strong suggestion over overwriting the previous badgeclass.

However, whichever method we use to add standardized versioning, it should probably be done carefully, maybe even more carefully than a lot of other extensions. It's important to maintain the ability to connect between assertions issued across different versions of the same badge.

timothyfcook commented 7 years ago

version is now a property within the badgeClass: https://github.com/openbadges/openbadges-specification/pull/99/commits/8d26bdb4263bf9f2c3155f6d1ee2adf0a3ff631a

Moving to archive.