Feels like @evan's FEP-5711: Inverse Properties for Collections should probably just be like `collectionFor` or something, rather than N different `____Of` collections?
ActivityPub Test Kategorie
7
Beiträge
3
Kommentatoren
1
Aufrufe
-
Feels like @evan's FEP-5711: Inverse Properties for Collections should probably just be like `collectionFor` or something, rather than N different `____Of` collections?
-
Feels like @evan's FEP-5711: Inverse Properties for Collections should probably just be like `collectionFor` or something, rather than N different `____Of` collections?
-
@thisismissem oh, also: definitely add an issue if you think there should be a change!
-
@evan well, you're the author, so, yeah, it's "your" FEP. Generally we don't make changes to other people's FEPs without getting them to review and be involved.
I'm just wondering if there's a need for a different property for each, when it feels like these are all just pointing back to the actor or to a collection on the actor?
-
@thisismissem oh, also: definitely add an issue if you think there should be a change!
@evan well, it's not really an "issue", just a concern that by having N different properties, we'll have to keep updating and extending the FEP in order to add in the new collections that might appear on an actor or object.
-
@evan well, it's not really an "issue", just a concern that by having N different properties, we'll have to keep updating and extending the FEP in order to add in the new collections that might appear on an actor or object.
@thisismissem we can do that as extensions are created; this FEP just covers the collections in AP proper.
-
Feels like @evan's FEP-5711: Inverse Properties for Collections should probably just be like `collectionFor` or something, rather than N different `____Of` collections?
thisismissem@hachyderm.io or maybe
context? Hahaha I will never stop promoting this property.Edit: or even
attributedTo
