Representing images

[Sebastian]

Just want to mention too, that koehn’s example is perfect.
“Be liberal in what you accept and strict in what you send” –

So, I wonder if mastodon has ever read the specification for ActivityStreams Core where it reads
Care should be taken to not unduly overlap with or duplicate the existing Object types.

An Image is an Image is an Image …

@koehn

The url needn’t be a single object, but an array of multiple links with different width and height from which the client should select.

This is what I wrote here, in @redaktor it is a srcset

Opinions on `images`?

This would be a <picture srcset> but we do not know how widely this would be supported. See also example 51 in the Spec. { "@context": "https://www.w3.org/ns/activitystreams", "type": "Image", "name": "Cat Jumping on Wagon", "url": [ { "type": "Link", "href": "http://example.org/image.jpeg", "mediaType": "image/jpeg", "width": 400 }, { "type": "Link", "href": "http://example.org/image.png", "mediaType": "image/jpeg", "width": …

It is also a bad decision to let mediaType decide over ActivityPub type like mastodon !
In the real world one ActivityPub "type":"image" can have multiple mediaType and this is super useful if you let the browser decide in the srcset, e.g. webp for modern or jpeg for old-school …

---

@koehn please note that the posted examples from mastodon and pleroma are imho invalid –
the specification clearly says for mediaType

When used on a Link, identifies the MIME media type of the referenced resource.

When used on an Object, identifies the MIME media type of the value of the content property. If not specified, the content property is assumed to contain text/html content.

Document is an Object but the examples try to describe the mediaType of url –
so: Your posted example is “correct” …