"＠context": [ "https://www.w3.org/ns/activitystreams", { "Quotation": "as:Quotation", "citation": "as:citation", "quotation": "as:quotation" },],#ActivityPub #ActivityStreams #FediDev #Fediverse #JSONLD #ObjectTypeQuotation
-
"＠context": [
"https://www.w3.org/ns/activitystreams",
{
"Quotation": "as:Quotation",
"citation": "as:citation",
"quotation": "as:quotation"
},
],#ActivityPub #ActivityStreams #FediDev #Fediverse #JSONLD #ObjectTypeQuotation
-
"＠context": [
"https://www.w3.org/ns/activitystreams",
{
"Quotation": "as:Quotation",
"citation": "as:citation",
"quotation": "as:quotation"
},
],#ActivityPub #ActivityStreams #FediDev #Fediverse #JSONLD #ObjectTypeQuotation
What's this about? Quote posts per Mastodon are a FEP: https://codeberg.org/fediverse/fep/src/branch/main/fep/044f/fep-044f.md
Those terms do not exist in the ActivityStreams spec?
-
What's this about? Quote posts per Mastodon are a FEP: https://codeberg.org/fediverse/fep/src/branch/main/fep/044f/fep-044f.md
Those terms do not exist in the ActivityStreams spec?
No. Not for quote-posts.
For quoting things from the books, scholarly papers, blog posts, videos, podcasts, etc.
https://mastodon.social/@reiver/115213464131046302
.
-
No. Not for quote-posts.
For quoting things from the books, scholarly papers, blog posts, videos, podcasts, etc.
https://mastodon.social/@reiver/115213464131046302
.
@reiver @thisismissem instead of making up properties that don't exist in a namespace that you don't own, you should use something that someone else already defined properly within their own authority, or otherwise define stuff under your own authority.
for example: CITO is an ontology for citations http://purl.org/spar/cito
see also http://www.w3.org/ns/prov#Quotation or http://purl.org/spar/fabio/Quotation
-
@reiver @thisismissem instead of making up properties that don't exist in a namespace that you don't own, you should use something that someone else already defined properly within their own authority, or otherwise define stuff under your own authority.
for example: CITO is an ontology for citations http://purl.org/spar/cito
see also http://www.w3.org/ns/prov#Quotation or http://purl.org/spar/fabio/Quotation
@reiver @thisismissem but more importantly: before defining such terms, consider what you are actually trying to do with them practically. how do you intend to process them? what's the use case? which information do you need and why? ask yourself those questions first.
-
@reiver @thisismissem but more importantly: before defining such terms, consider what you are actually trying to do with them practically. how do you intend to process them? what's the use case? which information do you need and why? ask yourself those questions first.
I already posted about that.
-
I already posted about that.
@reiver @trwnh @thisismissem The Activity Streams 2.0 Extension Policy covers some best practices for making extensions:
-
@reiver @trwnh @thisismissem The Activity Streams 2.0 Extension Policy covers some best practices for making extensions:
@reiver @trwnh @thisismissem They're not long, so I'll list them here:
- A unique namespace, distinct from the Activity Streams 2.0 namespace.
- A JSON-LD context document at a permanent URL. Services like https://purl.archive.org/ and https://w3id.org/ can be used to provide permanent URLs.
- A document that describes the terms and usage of the extension.
- An intellectual property rights policy that is compatible with inclusion in a W3C specification.[cont'd]
-
@reiver @trwnh @thisismissem They're not long, so I'll list them here:
- A unique namespace, distinct from the Activity Streams 2.0 namespace.
- A JSON-LD context document at a permanent URL. Services like https://purl.archive.org/ and https://w3id.org/ can be used to provide permanent URLs.
- A document that describes the terms and usage of the extension.
- An intellectual property rights policy that is compatible with inclusion in a W3C specification.[cont'd]
...
- Demonstrated implementation by at least two (2) independent publishers.
- Demonstrated implementation by at least two (2) independent consumers.
Gli ultimi otto messaggi ricevuti dalla Federazione
-
@blaine @cwebber Anyways, I'm sorry your experience there was horrendous, especially since I had encouraged you to participate. As one of the authors of that report, I should have been more careful to make sure your suggestion was included. I apologize for not doing a better job; I'll try to learn from the experience to do better in the future.
-
-
@blaine @cwebber this is the AP Webfinger profile, right? I remember this.
I just re-read the issue comment history. It's weird that I didn't reply anywhere in here, given that I was tagged. I am sorry that your idea didn't get into the doc, even as a future enhancement. It seems like a useful feature and part of the point of Webfinger.
I opened some new issues on that repo recently. I'm going to reopen this one, if you don't mind. It seems like a really good topic for discussion.
-
@cwebber I actually do like the PDS part of bluesky, and I like the DID part except for the fact that it's fake. PDSes that can talk to each other via activitypub sounds highly desirable to me.
-
@cwebber Indeed, global like counts and trending hashtags are only useful for the advertising industry.
-
@julian fair enough, just expected you not to see it due to your profile text 😅
-
@blaine @cwebber Your take on the topology is spot on, and there's a traceable lineage from polled RSS to pushed RSS to OStatus to ActivityPub. I think AP supports innovation through different schemas, but it really requires supporting the AP API. See https://www.w3.org/wiki/Activity_Streams/Primer/Extensions for examples.
-
@evan @cwebber I feel like one day we should have a beer again. My "same picture" take has been (for many, many years) that ActivityPub is two-way RSS with usable identity (even if the standard doesn't admit it). XMPP is the same, and the main innovation from atproto is actually-malleable schemas. Private data will bring it in-line with AP, while perf. optimizations will work the other direction. All asides, though: I care about what the people want, not what the computers want. ❤️
