UAI: Create Implementation Guide Version 0.1-Review and Rework

[yesrag2309]

Timelines

1. Master Class Session with NPs on November 13th 2024
2. Winroom on November 19,20 & 21
3. Go-Live December 13th

Implementation Guide MD Link

Guide link is here

For Reference Implementation Guide Confluence Link

Confluence link is here

[yesrag2309]

Current Status

1. UAI implementation guide MD files Ver0.1 are shared to Global Mission Team for Advisory, Rental & Sales use cases.
2. Internal review with @faizmagic is scheduled on 12th Nov 4-5.30pm
3. L2 config file is InProgress Advisory use case ETA by 12th Nov EOD & Rental & Sales use cases ETA 14th Nov EOD

Next Steps

1. Once @faizmagic review is completed and if there is any review comments need to incorporate and share the Ver 1.0 to Global Mission Team.
2. Once L2 files are prepared need to share it with Global Mission Team.

@rajaneeshk90

[yesrag2309]

Internal Review comments

1. Add cancellation_terms and other relevant details in the on_init payload.
2. Replace technical terms related to crop diseases with simpler, layman-friendly names (e.g., change "Stemphylium leaf blight" to "Kala Daag").
3. The current implementation assumes that the BPP collects the payment. This should be updated to reflect that the BAP is responsible for collecting the payment.
4. Change the example "bap_id": "ps-bap-network.becknprotocol.io" to something like example.becknprotocol.io and add a comment in the implementation guide to clarify that it's just an example for the NPs.
5. Add meta APIs (e.g., get_rating_categories) and other relevant details in the implementation guide.

Current Status

1. UAI implementation guide MD files Ver0.1 are shared to Global Mission Team for Advisory, Rental & Sales use cases.
2. L2 config file for Advisory is prepared and need to publish with main branch
3. L2 config file for Rental is InProgress and it will be published in main branch before 13th Nov 3pm Master Class session.
   Based on 12th Nov internal review with @faizmagic the above mentioned comment will be incorporated before 13th Nov 3pm Master Class session.

Next Steps

1. Based on 12th Nov internal review with @faizmagic the above mentioned comment will be incorporated before 13th Nov 3pm Master Class session.
2. L2 config file for Sales will be published in main branch by 14th EOD.
3. The below version 0.2 review comments need to incorporate before 19th Winroom and Version 1.0 will be ready for the Winroom.

Version 0.2

1. Need to check with @Kathirvel-ai how the paid advisory forecast data is delivered. What is the use case for the NPs?
2. Based on the paid advisory discussion the BPP flow needs to update.

@rajaneeshk90

[yesrag2309]

Internal review comments

Incorporated in V0.1

1. Add cancellation_terms and other relevant details in the on_init payload.
2. Replace technical terms related to crop diseases with simpler, layman-friendly names (e.g., change "Stemphylium leaf blight" to "Kala Daag").
3. The current implementation assumes that the BPP collects the payment. This should be updated to reflect that the BAP is responsible for collecting the payment.
4. Change the example "bap_id": "ps-bap-network.becknprotocol.io" to something like example.becknprotocol.io and add a comment in the implementation guide to clarify that it's just an example for the NPs.

Pending to Incorporate in V0.2

1. Add meta APIs (e.g., get_rating_categories) and other relevant details in the implementation guide.

Current Status

1. The above internal review comments are incorporated in the implementation guide as part of V0.1
2. L2 Config file prepared for Rental Use case
3. Tech team participated in the Master Class session today and showcased the Implementation Guide for Advisory, Rental & Sales along with Advisory, Rental L2 config file

Next Steps

1. L2 config for Sales use case will be ready by 14th Nov EOD.
2. The below version 0.2 review comments need to discuss with @Kathirvel-ai and tech team will try incorporate before 19th Winroom.

Version 0.2

1. Need to check with @Kathirvel-ai how the paid advisory forecast data is delivered. What is the use case for the NPs?
2. Based on the paid advisory discussion the BPP flow needs to update.
3. Add meta APIs (e.g., get_rating_categories) and other relevant details in the implementation guide.

@rajaneeshk90 @viraj89 @emmayank @faizmagic

[yesrag2309]

Current Status

1. Working on add meta APIs (e.g., get_rating_categories) and other relevant details in the implementation guide.

Next Steps

1. L2 config for Sales use case will be ready by 18th Nov EOD.
2. The below version 0.2 review comments need to discuss with @Kathirvel-ai and tech team will try incorporate before 19th Winroom.

Version 0.2

1. Need to check with @Kathirvel-ai how the paid advisory forecast data is delivered. What is the use case for the NPs?
2. Based on the paid advisory discussion the BPP flow needs to update.

@rajaneeshk90 @viraj89 @emmayank @faizmagic

[yesrag2309]

Current Status

Add meta APIs (e.g., get_rating_categories) and other relevant details are updated in the implementation guide.

Next Steps

The below version 0.2 review comments need to discuss with @Kathirvel-ai and tech team will try incorporate within this iteration.

Version 0.2

Need to check with @Kathirvel-ai how the paid advisory forecast data is delivered. What is the use case for the NPs?
Based on the paid advisory discussion the BPP flow needs to update.

@rajaneeshk90 @viraj89 @emmayank @faizmagic

[yesrag2309]

Current Status

UAI implementation guide is published as MD file to Global Missions Team along with L2 config files.

Next Steps

The below version 0.2 review comments need to discuss with @Kathirvel-ai and tech team will try incorporate in the next iteration. Hence closing this flow card.

Version 0.2

Need to check with @Kathirvel-ai how the paid advisory forecast data is delivered. What is the use case for the NPs?
Based on the paid advisory discussion the BPP flow needs to update.

@rajaneeshk90 @viraj89 @emmayank @faizmagic

[rajaneeshk90]

Update

• Fixed the naming convention of the 3 layer2 configuration files.
• Added additional flavours of search in all the 3 use case implementation guide.