Open azure-sdk opened 1 year ago
Hi @deyaaeldeen, The usage scenarios link doesn't contain any code or pseudocode samples. Can you please add usage scenarios with code/pseudocode examples? Thank you.
Hi @deyaaeldeen, Looks like the Hero Scenarios Link points to some documentation that doesn't include any code samples. The architects will want code samples for each language being reviewed. Those can be added to the Usage Samples tab in API View.
@ronniegeraghty Thanks for the reminder, I asked the crew to address it.
@deyaaeldeen The Java APIView is hard to diff. There doesn't appear to be a 5.2.0 in there to diff against? Can you please provide details or a link to the review diff that should be reviewed? Also, unlike the .net review, there aren't any Java usage samples that I can see yet?
@mssfang Could you please address the issues that @JonathanGiles raised in https://github.com/Azure/azure-sdk/issues/5476#issuecomment-1427150028?
Thanks @mssfang for updating the link! @JonathanGiles Please let me know if you have any questions.
Hi @deyaaeldeen, I was told that in the Intro session today, your team didn't have time to get through everything. Looks like next week on the 22nd there is no Arch Board Review scheduled yet. The architects recommended you scheduled a second follow-up intro meeting on that day to continue the discussion. You can schedule the meeting exactly the same way as you scheduled this one.
@ronniegeraghty Thanks a lot Ronnie for accommodating us, we need more time to follow-up on the open items so we will pass on that spot for now. Thanks again.
New SDK Review meeting has been requested.
Service Name: Azure Cognitive service for language - Text Analysis Review Created By: Deyaaeldeen Almahallawi Review Date: 2/13/2023 2:05 PM PT
Hero Scenarios Link: here Architecture Diagram Link: Not Provided Core Concepts Doc Link: here APIView Links: Javascript, Python, .NET, Java,
Description: Review for the following features: • Abstractive summarization • Dynamic classification • Automatic language detection • Entity resolution • Script detection • FHIR document type hint
Detailed meeting information and documents provided can be accessed here