You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Move over the envelopes and payloads with as much semantic fidelity as possible, but don't worry about signatures and original structure - just get the metadata across. (We would worry about identities, just not crypto stuff). The old envelopes would look like new envelopes.
We might junk many envelopes that we don't know how to transform. Basically this is best effort with a focus on meaning and quality for the end user who is consuming these new envelopes.
The text was updated successfully, but these errors were encountered:
Possibly we would include the original envelope exactly as-was in a extra envelope field like "legacy_envelope" or something - so that anyone who wants to access the exact original resource could do so..
We want to have a schema that can handle structured relationships between content and curriculum. Stuff like "Math-Grade 9/Module 1/Unit 3/Lesson 26/Resource 2"
Move over the envelopes and payloads with as much semantic fidelity as possible, but don't worry about signatures and original structure - just get the metadata across. (We would worry about identities, just not crypto stuff). The old envelopes would look like new envelopes.
We might junk many envelopes that we don't know how to transform. Basically this is best effort with a focus on meaning and quality for the end user who is consuming these new envelopes.
The text was updated successfully, but these errors were encountered: