×
Well done. You've clicked the tower. This would actually achieve something if you had logged in first. Use the key for that. The name takes you home. This is where all the applicables sit. And you can't apply any changes to my site unless you are logged in.

Our policy is best summarized as "we don't care about _you_, we care about _them_", no emails, so no forgetting your password. You have no rights. It's like you don't even exist. If you publish material, I reserve the right to remove it, or use it myself.

Don't impersonate. Don't name someone involuntarily. You can lose everything if you cross the line, and no, I won't cancel your automatic payments first, so you'll have to do it the hard way. See how serious this sounds? That's how serious you're meant to take these.

×
Register


Required. 150 characters or fewer. Letters, digits and @/./+/-/_ only.
  • Your password can’t be too similar to your other personal information.
  • Your password must contain at least 8 characters.
  • Your password can’t be a commonly used password.
  • Your password can’t be entirely numeric.
Enter the same password as before, for verification.
Login

Grow A Dic
Define A Word
Make Space
Set Task
Mark Post
Apply Votestyle
Create Votes
(From: saved spaces)
Exclude Votes
Apply Dic
Exclude Dic

Improving API Documentation Comprehensibility via Continuous Optimization and Multilingual SDK. (arXiv:2303.13828v1 [cs.SE])

Click here to flash read.

Optimizing and maintaining up-to-date API documentation is a challenging
problem for evolving OpenAPIs. In this poster, we propose a data-driven
continuous optimization solution and multilingual SDK generation scheme to
improve the comprehensibility of API documentation. We compute the correlation
between API integrity and API trial success rate. Based on this, we partition
the API to ensure that each API has a correct optimization direction. Then, we
propose a fine-grained(i.e., parameter level) continuous optimization solution
to annotate problems in API documents in real-time. Based on the above
resolutions, we can provide theoretical analysis and support for the
optimization and management of API documents. Finally, we explore the crucial
challenges of OpenAPIs and introduce a tailored solution, TeaDSL, a
multi-language SDK solution for all OpenAPI gateways. TeaDSL is a
domain-specific language that expresses OpenAPI gateways, generating SDKs, code
samples, and test cases. The experiments evaluated on the online system show
that this work's approach significantly improves the user experience of
learning OpenAPIs.

Click here to read this post out
ID: 22054; Unique Viewers: 0
Unique Voters: 0
Total Votes: 0
Votes:
Latest Change: March 27, 2023, 7:33 a.m. Changes:
/u/anonymous
Dictionaries:
Words:
Spaces:
Views: 8
CC:
No creative common's license
Comments: