Use case 1: Multiple descriptions share the same schemas or other components, and users might wish to enforce which components are shared, and how, using parser/linter rules
Use case 2: The parser/linter could be expanded to account for workflows (as defined by the Workflows SIG), and therefore need to assert rules across multiple APIs connected by workflows
Use case 1: Multiple descriptions share the same schemas or other components, and users might wish to enforce which components are shared, and how, using parser/linter rules
Use case 2: The parser/linter could be expanded to account for workflows (as defined by the Workflows SIG), and therefore need to assert rules across multiple APIs connected by workflows