Conversation

Notices

1. Embed this notice
   André Menrath (linos@graz.social)'s status on Thursday, 24-Oct-2024 23:39:17 JST André Menrath

   • dansup
   • Marcin Mikołajczak
   • Matthias Pfefferle
   • Mastodon Engineering
   • Laurin

   Are there any Fediverse applications that have problems receiving objects that have arrays within the "type"? @MastodonEngineering @dansup @pfefferle @helge @mkljczk @laurin

   • Embed this notice
     silverpill (silverpill@mitra.social)'s status on Thursday, 24-Oct-2024 23:39:14 JST silverpill

     in reply to

     • dansup
     • Marcin Mikołajczak
     • Matthias Pfefferle
     • Mastodon Engineering
     • Laurin
     • grindhold

     @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-location
     In practice multi-typing is totally useless and hinders interoperability, so all ActivityPub projects assign a single type to their objects.

   • Embed this notice
     grindhold (grindhold@23.social)'s status on Thursday, 24-Oct-2024 23:39:16 JST grindhold

     in reply to

     • dansup
     • Marcin Mikołajczak
     • Matthias Pfefferle
     • Mastodon Engineering
     • Laurin

     @linos @MastodonEngineering @dansup @pfefferle @helge @mkljczk @laurin objects and their types respectively have a N:1-relation. which scenario would require it to be a N:M relation? is this a "the fields of my object fulfill the interfaces of more than one type"-thing?
     is this mentioned anywhere in the specs?

   • Embed this notice
     silverpill (silverpill@mitra.social)'s status on Saturday, 26-Oct-2024 04:10:26 JST silverpill

     in reply to

     @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.

   • Embed this notice
     André Menrath (linos@graz.social)'s status on Saturday, 26-Oct-2024 04:10:28 JST André Menrath

     in reply to

     • silverpill

     @silverpill

     I 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?!

   • Embed this notice
     silverpill (silverpill@mitra.social)'s status on Sunday, 27-Oct-2024 01:29:53 JST silverpill

     in reply to

     • silverpill

     @linos

     https://codeberg.org/fediverse/fep/pulls/430/files

     >Or use a custom attribute https://event-federation.eu/ns/#isVirtualLocation

     +1

     I think boolean attribute is cleaner than multi-typing. You can also duck-type location as a virtual location if url attribute is present

   • Embed this notice
     Laurin (laurin@mastodon.online)'s status on Friday, 01-Nov-2024 05:28:58 JST Laurin

     in reply to

     • silverpill

     @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.

   • Embed this notice
     silverpill (silverpill@mitra.social)'s status on Friday, 01-Nov-2024 05:28:58 JST silverpill

     in reply to

     • Laurin

     @laurin @linos
     isVirtualLocation 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.