So, for finding the AP equivalent of an URL that I think is a Web page, I'd take these steps:
- Link header: HEAD and look for the Link: header (easy, fast) - Webfinger: Webfinger the URL (a little more complicated) - Content negotiation: GET with Accept header set to AS2 type - Parsing: GET and look for Link: header or <link> element
For finding the HTML page for an AP object:
- Link header: HEAD and look for Link: - AS2: GET and look for `url` at top level
@evan@julian@nightpool in the Postel sense, though, it's too bad that a client implementor needs to maintain (at least) four discovery pathways, and may require four separate requests to validate the information. Similarly, an ap host doesn't know which spots a client will check, so needs to implement all four. I'm well out of the standards game, but I'd very much advocate for "pick one and stick with it" 😊