mastodon.social is one of the many independent Mastodon servers you can use to participate in the fediverse.
The original server operated by the Mastodon gGmbH non-profit

Administered by:

Server stats:

354K
active users

1/

"orderedItems" shows up in the examples in the ActivityStreams Vocabulary spec:

w3.org/TR/activitystreams-voca

But, I don't see a definition for "orderedItems" in there (in the ActivityStreams Vocabulary spec).

www.w3.orgActivity Vocabulary
@reiver ⊼ (Charles) :batman:

3/

However, "orderedItems" is mentioned in the ActivityStreams Core spec:

w3.org/TR/activitystreams-core/

Maybe the closest thing to a definition is:

"Collection are represented using the 'items' property while ordered items are represented using the 'orderedItems' property."

So, "orderedItems" is just like "items":

w3.org/TR/activitystreams-voca

... except renamed and the interpretation is different

www.w3.orgActivity Streams 2.0

@reiver to me the distinction between items and orderedItems seemed rather flimsy. It introduces a separation that has no practical benefit in my opinion.

As the ordered collection doesn't have any way to express the logic for the ordering, it might as well not exist as a separate ActivityStreams object and it just serves to introduce friction for no benefit.

@mariusor @reiver Well, the type itself is fine by me, but having to put them on a different property is stupid. The type is named OrderedCollection, I would kinda expect the items to be ordered, no need to rename it to orderedItems.

This is all json-ld nonsense. orderedItems is an alias for items, signifying that the json array should be treated as a list and not a set, see

        "orderedItems": {
            "@container": "@list",
            "@id": "as:items",
            "@type": "@id"
        },

in the json-ld context.

@helge @mariusor @reiver Cool, but still stupid. There's no need to do both a distinct type and a property. Either one would do the job, being forced to do both at once is stupid.