Home

Conversation

$$15435
https://hollo.social/@hongminhee posted on Mar 21, 2026 04:32

So, an interesting issue came up in the #Fedify repo that I’ve been thinking about: #629.

You know how every #fediverse server uses schema:PropertyValue in actor attachment for profile metadata fields (like “Website”, “GitHub”, etc.)? Turns out, strict #AS2 validators like browser.pub reject it, because the AS2 spec says attachment should only contain Object or Link—and PropertyValue is a schema.org type, not an Activity Streams 2.0 type.

The thing is, we can’t just drop the type like we did with Endpoints (#576), because Mastodon and others rely on seeing "type": "PropertyValue" to render profile fields. But at the same time, it’s technically not spec-compliant.

I’m leaning towards writing a #FEP to formalize this existing practice rather than trying to invent a new type (like toot:PropertyValue extending Object), which would be a nightmare to migrate across the whole fediverse.

What do you all think? Has anyone else run into this? Would love to hear thoughts from implementers and spec folks.

#fedidev #ActivityPub #ActivityStreams #ActivityStreams2 #AS2 #PropertyValue

https://hollo.social/@hongminhee/019d0eaa-637d-70e4-b110-fb96d4f2cf24
Reply
$$15676
https://mitra.social/users/silverpill posted on Mar 21, 2026 20:04
In reply to: https://hollo.social/@hongminhee/019d0eaa-637d-70e4-b110-fb96d4f2cf24

@hongminhee +1 for formalizing the existing practice in a FEP.

PropertyValue is covered in FEP-fb2a, but it proposes an alternative representation which implementers must support:

https://codeberg.org/fediverse/fep/src/branch/main/fep/fb2a/fep-fb2a.md

https://mitra.social/objects/019d11ff-88e3-33c6-e87b-7b330d1c7cf3
Reply