1. 2018 API 3b & 3c Proposal
05/22/2018

2. API 3b
Evaluate the ability to define specific lists to be submitted for the Query/Response in the OASIS Template format and develop new standards/modifications as needed

3. Option 1 – The Winner Create a list query variable Pros: Cons:
Example: AREF_LIST=123,456,789,...
Pros:
Low impact to existing framework
Minimal template changes required. Limited to addition of a new field.
Cons:
Hard limit for number of records supported based on max character limit

4. Option 2 Use existing structure for repeating query variables Cons:
Multiple Instances
Example: AREF1=123&AREF2=456&AREF3=789
Pros:
Utilizes an existing mechanism
No hard limit to the number of records.
Cons:
The existing framework would need to be updated. This is a much larger development task than adding a new field.

5. Option 3 Allow csv format for query response templates
This was ruled out due to the scope and complexity of changes required.

6. Changes Define the following list query variables
ASSIGNMENT_REF_LIST
REASSIGNED_REF_LIST
RELATED_REF_LIST
Remove * indicating multiple instances allowed
Update the following templates
Transstatus
Reduction
CCO
Rollover to be addressed with NITS template changes

7. API 3c
Evaluate adding dynamic notification for the rollover rights renewal deadline and develop new standards/modifications as needed (PTP only)

8. Option 1 – The winner Expand use of STATUS_NOTIFICATION
Dynamic notification will be delivered when system time is equal to ROLLOVER_NOTIFICATION _TIME
Pros
Allows customers more control over their notifications
Allows the TP to arrange for dynamic notification on the customer’s behalf
Cons
Requires creation of rolloverpost template

9. Option 2 “mailto:” URL registered on the OASIS Node
Similar to Preemption & ROFR
Pros
Allows for a simple opt-in for dynamic notification
No new templates required
Cons
TP cannot arrange for dynamic notification on the customer’s behalf
Bundled with other notifications
Option 2 - “mailto:” URL registered on the OASIS Node

10. Who is responsible?
A concern had been raised over who is responsible for delivery of dynamic notification.
Dynamic Notification
“...OASIS Nodes shall not be obligated or liable to guarantee delivery/receipt of messages via the STATUS_NOTIFICATION mechanism other than on a "best effort" basis...”

11. Changes Expand the definition of STATUS_NOTIFICATION
Add the following data elements to the rollover template:
ROLLOVER_NOTIFICATION_TIME
STATUS_NOTIFICATION
Creation of the rolloverpost template
Required to allow TC entry of dynamic notification