Post AnZnp8GmUUPxBemwc4 by laurin@mastodon.online
 (DIR) More posts by laurin@mastodon.online
 (DIR) Post #AnKn0uDRrx7LnuGDLM by silverpill@mitra.social
       2024-10-24T14:38:32.637882Z
       
       1 likes, 0 repeats
       
       @grindhold @dansup @helge @pfefferle @linos @laurin @MastodonEngineering @mkljczk Yes, unfortunately this is in the specs: https://www.w3.org/TR/activitystreams-core/#fig-an-object-that-is-both-a-place-and-a-gr-locationIn practice multi-typing is totally useless and hinders interoperability, so all ActivityPub projects assign a single type to their objects.
       
 (DIR) Post #AnNFihZ1SMHkL3wXui by linos@graz.social
       2024-10-25T18:03:37Z
       
       1 likes, 0 repeats
       
       @silverpillI think there are good examples, where it might be useful.E.g. take an Event. You have the location, but it is online. So you don't add a Place, but rather an schema.org/VirtualLocation. It also has a Name and a URL. If you also give it the type Place applications that do not know about VirtualLocation can still receive it.I am just about finishing a FEP draft. I hope I don't miss something! I'd say let's keep discussing on socialhub once it's submitted?!
       
 (DIR) Post #AnNFiiyEE82ehWkBqC by silverpill@mitra.social
       2024-10-25T19:09:43.357971Z
       
       0 likes, 0 repeats
       
       @linos Generally, applications should look for properties they understand, and ignore object types. This practice is known as duck typing. In case of location you can parse name and optionally coordinates. Now your peers can use any type they want, or skip it altogether - as long as name is present you will have something to work with.
       
 (DIR) Post #AnP5u7BQWAtKpV5Z2G by silverpill@mitra.social
       2024-10-26T16:29:04.044189Z
       
       0 likes, 0 repeats
       
       @linoshttps://codeberg.org/fediverse/fep/pulls/430/files>Or use a custom attribute https://event-federation.eu/ns/#isVirtualLocation+1I think boolean attribute is cleaner than multi-typing. You can also duck-type location as a virtual location if url attribute is present
       
 (DIR) Post #AnZnp8GmUUPxBemwc4 by laurin@mastodon.online
       2024-10-31T17:48:05Z
       
       0 likes, 0 repeats
       
       @silverpill @linos I see the point about compatibility with apps that do not follow the spec here.Why would you say, it is cleaner though, to add a property only, over adding a second type?For both cases: If I wanted to be thorough, I'd go and add this property to an RDF ontology. I'd expect the ontology to define that type and the property associated with it.So in the end, it'd be a multi-type along with a definition of the property that is linking to a video, for example.
       
 (DIR) Post #AnZnp8n2YYDonhshtY by silverpill@mitra.social
       2024-10-31T20:28:27.876622Z
       
       0 likes, 0 repeats
       
       @laurin @linosisVirtualLocation is self explanatory. [Place, VirtualLocation] is not - is it "Place and VirtualLocation", "Place or VirtualLocation", something else?More importantly, no one in Fediverse uses multi-typing, we use properties to extend standard objects. Introduction of multi-typing creates a lot of work for everyone.