AC: specifications are interrelated, building on one another, occupation, course, lesson plan ✪
AC: Learning opportunity specification, add individual information to create a credential ✪
AC: Credential metadata- Issuer data and credential type, Claim - Person ID (10-15 different identifiers) set of legal identifiers defined by EU for signature, and action ✪
AC: VC XML currently moving toward an RDF/JSONLD model ✪
<nate_otto> When you say a credential has 60 claims in it, area these 60 described achievements, each of which might have entitlements etc? Packaged together like a transcript? (For next pause)
AC: TWCU - no nesting relationship between badgeclass and resultdescription ✪
<dmitri_zagidulin> meaning, if you have a bunch of short credentials, that you can bind them into a single larger one. Or, if you have a large multi-claim credential, you can split out claims (using BBS+ etc)
DE: can it be simple and then referenced from the more complex? ✪
<dmitri_zagidulin> (or, if not able to use BBS+ or similar tech, it could be as simple as - ask your issuer for BOTH a large "transcript", and a specific skill credential.
DE: OBv3 and CLR will both support multiple claims? ✪
<deb_everhart> one important value of that approach is to give people their achievements sooner, along the way to the larger credential
AC: in the transcript you could do a number of small credentials, but there are many use cases that still require multiple claims in a single credential ✪
P1: OBv3 as a building block is a great value, complex credentials have a layering with relationships between those claims and sequence of those claims matter ✪
P1: metadata of the relationships is required in the more complex credentials ✪
P1: complex credentials work ahead is the metadata patterning ✪