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

You know how every server uses schema:PropertyValue in actor attachment for profile metadata fields (like “Website”, “GitHub”, etc.)? Turns out, strict 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 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.

0

If you have a fediverse account, you can quote this note from your own instance. Search https://hollo.social/@hongminhee/019d0eaa-637d-70e4-b110-fb96d4f2cf24 on your instance and quote it. (Note that quoting is not supported in Mastodon.)

RDFの意味論においては`as:attachment`の値域が`as:Object`または`as:Link`であるというのは、`as:attachment`の値として`as:Object`でも`as:Linkでもないものを指定したらエラーとなるという意味*ではなく*、`as:attachment`の値として指定されたものは全て`as:Object`または`as:Link`であると見なしますという意味であるはずなので、この場合は拒否する方が間違いな気がする(自信がない)
QT: hollo.social/@hongminhee/019d0
[参照]

0