jtillesFirst: is there any semantic difference between an AS2 object having a `url` attribute of "http://example.org" and an attribute of `{"type": "Link", "href": "http://example.org", "rel": "self"}`?
shevski, kevinmarks2, kevinmarks3 and Karli joined the channel
ben_thatmustbemeactually, i suppose it would depend on if thats the only object in the AS2 you fetched or not, doesn't rel only ever refer to a relation to the page as a whole?
jasnell_actually just saw the question... so semantically yes there's a difference. {"url": "http://example.org"} is a description of the object itself. It's saying, "this is an object with this url". {"type": "Link", "href": "http://example.org"} is saying, "this is a reference to something at http://example.org". The former is describing the object, the latter is describing a link to the object
ben_thatmustbeme"is there any semantic difference between an AS2 object having a `url` attribute of "http://example.org" and an attribute of `{"type": "Link", "href": "http://example.org", "rel": "self"}`?"
jasnell_it's similar in nature to the difference between <html><head><title>Foo</title></head><body></body></html> and <a href="http://link.to.foo">Foo</a>
jtillesjasnell_ first, thanks for helping out! I noticed that you didn't include `"rel": "self"` in your explanation. Was that a minor typo, or did you miss its presence in my question?
jtillesI mean, it makes sense to me that `{"url": "http://example.org"}` and `{"url": {"type": "Link", "href": "http://example.org"}}` aren't necessarily the same
jtillesbut I thought that `{"url": "http://example.org"}` and `{"url": {"type": "Link", "href": "http://example.org", "rel": "self"}}` *could* be equivalent.
kevinmarks3, kevinmarks4 and kevinmarks2 joined the channel
jtillesin case it’s helpful to know why this question of equivalence came up: at my job we'd like to store AS2 activities in Elasticsearch, but (as far as I can tell) Elasticsearch can't cope with deal with union types.