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
"registration" is intended as a data aggregation property (primarily) and we've come across use cases where it might be helpful to have a list of related registrations similar to the contextActivities. I think "registration" still stands alone as the one piece of information tying this Agent and Activity together for this instance of the experience, but also being able to relate that registration to others through a separate list would be the goal. I don't know what that property should be called, presumably it goes in context and has a matching "related_registrations" query parameter in the GET /statements request.
The text was updated successfully, but these errors were encountered:
brianjmiller
changed the title
Registrations as list in 2.0
New registrations list in 2.0
Nov 7, 2014
It seems like some of this issue could be addressed by some non-breaking changes the descriptive language around how the registration property should be used by an AP and perhaps encouraging more use of context.grouping.
In light of that, should we add an additional patch label to this issue or should I create a separate issue around updating the registration descriptive language?
"registration" is intended as a data aggregation property (primarily) and we've come across use cases where it might be helpful to have a list of related registrations similar to the contextActivities. I think "registration" still stands alone as the one piece of information tying this Agent and Activity together for this instance of the experience, but also being able to relate that registration to others through a separate list would be the goal. I don't know what that property should be called, presumably it goes in context and has a matching "related_registrations" query parameter in the GET /statements request.
The text was updated successfully, but these errors were encountered: