La prochaine conférence autour du #WebSémantique, @semwebpro aura lieu à Paris le 27 novembre 2025.
L'appel à communication est lancé, c'est par ici : https://semweb.pro/
Date limite de soumission : 30 juin 2025
Préparez vos sujets 
Conférence
: 27 Novembre 2025
@FIAP
#semweb #websem #opendata #linkeddata #linkedopendata
#knowledgegraph #thesaurus #ontology #RDF #SPARQL #SHACL
#OWL #JSONLD
My stance on #ActivityPub's adoption of JSON-LD: Since we've already decided to use JSON-LD, I hope we do it properly. However, if we hadn't used JSON-LD from the beginning, things would have been much less complicated.
Appel à candidatures #SemWebPro !
Le comité de programme souhaite intégrer de nouveaux membres ! Vous souhaitez nous aider à faire connaître cet évènement ?
Alors, rejoignez-nous !
Candidature avant le 30 avril à
contact@semweb.pro 
#semweb #websem #opendata #linkeddata #linkedopendata #knowledgegraph #thesaurus #ontology #RDF #SPARQL #SHACL #OWL #JSONLD
Appel à candidatures #SemWebPro !
La conférence https://semweb.pro est LA journée annuelle de présentations et de rencontres dédiées au #webSémantique dans le monde professionnel 
Elle a lieu chaque année à Paris
Le comité de programme souhaite intégrer de nouveaux membres ! Vous nous rejoignez ?
Candidature avant le 30 avril à contact@semweb.pro
#semweb #websem #linkeddata #linkedopendata #knowledgegraph #thesaurus #ontology #RDF #SPARQL #SHACL #OWL #JSONLD
New Releases! Along with the roadmap update, I'm happy to announce:
- JSON-LD.ex v1.0 with JSON-LD 1.1 support
- RDF.ex v2.1 with rdf:JSON literal support
- Grax v0.6 with a new JSON type and support for ordered lists based on rdf:List
These updates lay groundwork for the DID implementation and future developments. Please refer to the respective CHANGELOGs for a comprehensive list of the changes.
Want to see your web page content in rich results? Read this blog to learn all you need to know about applying Schema Markup or structured data. Additionally, find out how it can affect your SEO during a migration.
https://www.specbee.com/blogs/how-schema-markup-impacts-seo-during-website-migrations
Currently, the way I am determining if content is valid ActivityPub / ActivityStreams content is —
№1:
Determining if it is valid JSON.
№2:
Checking if it has a "type" field.
And that is it.
Dealing with JSON-LD would be easier in many ways if everything was defined inline.
Rather than having to get the content from a URL in the context, parse it, etc.
Learn how to create JSON-LD Schema efficiently using JavaScript snippets! This approach simplifies the integration of structured data into your web pages, boosting your site's SEO and enhancing search engine visibility. By automating schema generation, you save time and ensure consistency across your site. Dive into the world of JSON-LD and explore the benefits of structured data today! #JSONLD #JavaScript #SEO #WebDevelopment #StructuredData https://www.screamingfrog.co.uk/generate-json-ld-schema-at-scale/
3/
ActivityPub & ActivityStreams are based on JSON-LD — a format that is not (non-programmer) human-legible & human-writable
Maybe we need an alternative way of encoding ActivityPub & ActivityStreams in situations where (non-programmer) humans might read it or write it
Maybe the INI file data format? Or something else that is friendly to (non-programmer) humans?
2/
I agree that an open protocol is better and more important than just an application.
But I also think that an open file data format is better and more important than just an open protocol.
I.e.,:
file data format ≫ protocol ≫ app
...
1/
JSON-LD is not (non-programmer) human-legible format because — JSON is not (non-programmer) human-legible format.
JSON-LD and JSON are both also not (non-programmer) human-writable.
...
This feels so wasteful —
Including the same content twice — once in "content" and again in "contentMap".
!["content": "<p><a href=\"https://mastodon.social/tags/GreatApe\" class=\"mention hashtag\" rel=\"tag\">#<span>GreatApe</span></a></p><p>.</p>",
"contentMap": {
"en": "<p><a href=\"https://mastodon.social/tags/GreatApe\" class=\"mention hashtag\" rel=\"tag\">#<span>GreatApe</span></a></p><p>.</p>"
},](https://files.mastodon.social/media_attachments/files/114/070/075/153/000/472/original/f4209c22da4a771e.png "\"content\": \"<p><a href=\\"https://mastodon.social/tags/GreatApe\\" class=\\"mention hashtag\\" rel=\\"tag\\">#<span>GreatApe</span></a></p><p>.</p>\",
\"contentMap\": {
\"en\": \"<p><a href=\\"https://mastodon.social/tags/GreatApe\\" class=\\"mention hashtag\\" rel=\\"tag\\">#<span>GreatApe</span></a></p><p>.</p>\"
},")
I couldn't find this documented anywhere other than in code so I wrote up some notes on how link previews work, and what #opengraph tags and #jsonld attributes are supported in #mastodon #webdev #mastodondev https://griff.steni.us/blog/2025/02/22/mastodon-link-previews.html
9/
And just for the record —
Just like everyone else I contacted about their 'discoverable' flag being defaulted to 'false' —
He wasn't aware of the 'discoverable' flag existing (just like everyone else I contacted).
He didn't want to be hidden (just like everyone else I contacted).
He changed it to 'true' (just like everyone else I contacted).
8/
As it is now, I think the 'discoverable' flag is broken.
And, I think the whole user-experience (UX) around the 'discoverable' flag is poor.
And, I think Fediverse software treating a 'false' value for 'discoverable' as "not discoverable" (rather than "not discoverable" or "no choice made") has hugely negative consequences for the user-experience (UX) of the Fediverse
7/
So now I have to DM Ben to tell him that his 'discoverable' flag is set to false
He (just like everyone else I contacted) will likely not even be aware that the 'discoverable' flag exists
And (just like everyone else I contacted) wished it wasn't set to false
And then (just like everyone else I contacted) struggle to find where he can set it to true
And then set it
