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

submitted by

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

2
1

Log in to comment

Hot Top New Old

Yup do as @trwnh@mastodon.social and @silverpill@mitra.social say and implement fb2a.

It is supported by NodeBB and WordPress already.

 reply
1

@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

 reply
1
Insert image