@kin Is there JSON Schema for apis.json somewhere?
@kin That list of required properties feels like it is saying, "oh, no, you ain't auto creating these entries from scraped data" 🙂
Thanks for putting this together, just used it to normalize our index file and fix kiota's implementation.
https://github.com/microsoftgraph/msgraph-metadata/blob/71a3a35f68c0356182a602027e4f861a8ab718d5/apis.yaml
Some feedback/questions:
- all the contact objects require a "FN" property, what's that?
- it'd be great if the URL property (for X-openapi) would also accept relative URLs for our scenario
@vincentbiret @kin FN is vCard funkiness that inherited from X509 funkiness https://www.rfc-editor.org/rfc/rfc6350#section-6.2.1
@darrel_miller @kin
So the display name in essence, from digging into this 1988 document...
https://www.itu.int/rec/dologin_pub.asp?lang=e&id=T-REC-X.520-198811-S!!PDF-E&type=items
@vincentbiret @darrel_miller Yeah, the FN is vCard -- Minimum just a name and email or I use name + twitter handle. And it doesn't have to be for the API, just whoever is building the APIs.json index and responsible for upkeep.
@vincentbiret @darrel_miller The relative URL is great addition -- adding to the list for next version. I like that.
@kin @darrel_miller Thanks! Let us know when the next version is out so we can keep in sync :)
@kin You're a mighty fine gentleman, sir.