For Discussion: We may wish to allow the case where a top level apis.json file on a given domain has
pointers to files on other servers which define APIs on the domain of the first
file. These could then be considered authoritative. This is complex but might be a real
use case.
Absolutely. The most obvious use case is that it encourages factoring out of common or standardized elements of the metadata. Another use case is that it minimizes the amount of work needed to add or revise metadata (see the admin comment above). The easiest thing would be to build a URI-based cross-reference mechanism into the format so that the metadata has to be merely referenced by the root domain or a subdomain of the API (which it looks like you’ve built in below). A robot that traverses the references from the right domain to get to any metadata residing wherever can treat it as authoritative.
For Discussion: We may wish to allow the case where a top level apis.json file on a given domain has pointers to files on other servers which define APIs on the domain of the first file. These could then be considered authoritative. This is complex but might be a real use case.
Absolutely. The most obvious use case is that it encourages factoring out of common or standardized elements of the metadata. Another use case is that it minimizes the amount of work needed to add or revise metadata (see the admin comment above). The easiest thing would be to build a URI-based cross-reference mechanism into the format so that the metadata has to be merely referenced by the root domain or a subdomain of the API (which it looks like you’ve built in below). A robot that traverses the references from the right domain to get to any metadata residing wherever can treat it as authoritative.
From Eve Maler - https://groups.google.com/forum/#!topic/apisjson/s30XLjP8Q0A