Recent searches

No recent searches

Search options

Not available on photog.social.
photog.social is one of the many independent Mastodon servers you can use to participate in the fediverse.
A place for your photos and banter. Photog first is our motto Please refer to the site rules before posting.

Administered by:

Server stats:

240
active users

photog.social: AboutProfiles directoryPrivacy policy

Mastodon: AboutGet the appKeyboard shortcutsView source codev4.4.2

#linkeddata

1 post1 participant1 post today
*
Frederik Elwert

Today the #SemDH2025 workshop takes place alongside #ESWC2025. I’m happy that Philipp Tögel will present our paper on Data-rich Web Annotations. We discuss how web annotations, a W3C standard, can be leveraged to include complex analysis with domain-specific data models as #LinkedData, without a need to extend the WADM core ontology. We apply this in @sfb1475 to store rich information about metaphorical expressions as annotations. semdh.github.io/accepted-paper #DigitalHumanities #SemanticWeb

semdh.github.ioAccepted Papers
W3C Developers

Last April, @fabien_gandon highlighted how @w3c #LinkedData standards (such as RDF, SHACL, and #SPARQL) enable knowledge extraction, sharing, and machine learning across domains like #robotics, culture, medicine, and chemistry. These standards support interoperability, agent collaboration, and distributed #AI. He concluded his talk with a call to address AI's impact on user attention and to encourage ethical dialogue within the W3C community.

🎬 Watch 'LLM & Linked Data': youtu.be/CVFhPYTVBlI

Replied in thread
*
leobard

@marcel @nohillside

I like the grand idea of subscribing to URL paths, for networked decentralized distribution of #linkeddata chunks. I would love to see it used for collections of #semanticweb data relevant to me, my city, my trade.

asayers.com/jetrelay

Appendix: Thoughts on ATproto and the “push-based internet”

"The fact that the model matches the OG internet means you can expose the same data over HTTP for people who’d rather pull. Giving each record an identity (in the form of a path) is also just very useful in itself.

...

The pull-based internet has HTTP. The push-based internet has made do with RSS for a long time. A new, more capable standard could be a great development."

www.asayers.comJetrelay
*
Katharina Brunner

Warum man mit verlinkten Daten arbeiten will, wirkt häufig wie eine Arbeitsbeschaffungsmaßnahme. Erst mal alles komplizierter machen, damit's später einfacher ist - das ist nicht immer das überzeugenste Argument

@stk hat hier ein gut nachvollziehbares Beispiel aufgeschrieben: zu Adressen.

Und die Pointe hier schon mal verraten: Die Schweiz macht das so, flächendeckend.

stefan.bloggt.es/2025/05/what-

stk | schlampig sortiertes Zeug, das ich schon immer mal sagen wollte. · What is in a street name – Schoener leben mit Linked Data | stk
#linkeddata#lod
Continued thread
*
Ed Summers

But in other cases a description has an existing URI already, e.g. id.loc.gov/... and we want to allow it to be POSTed. We can switch the supplied subject URI with newly minted URI, and preserve the relation with `bf:derivedFrom`. But maybe this is hocus-pocus and the API should just not allow descriptions like this to be POSTed?

Is there anything else like this going on in #linkeddata land?

*
Ed Summers

Pardon this awkwardly expressed & niche question -- it has been a minute since I've done much #linkeddata work.

If you have an API that allows an RDF description (JSON-LD) to be POSTed, which results in a new resource being created, are there practices for how the subject URI in the description should be managed?

Julien A. Raemy

My PhD thesis "Linked Open Usable Data for Cultural Heritage: Perspectives on Community Practices and Semantic Interoperability" is now (finally) available in HTML format: phd.julsraemy.ch/thesis.html (not perfect I reckon)

The PDF was published in December 2024 on the University of Basel's repository: doi.org/10.5451/unibas-ep96807.

@IIIF
#LinkedData #LOUD #CulturalHeritage #DigitalHumanities #IIIF #LinkedArt #GLAM

phd.julsraemy.chLinked Open Usable Data for Cultural Heritage: Perspectives on Community Practices and Semantic InteroperabilityDigital technologies have fundamentally transformed how Cultural Heritage (CH) collections are accessed and engaged with. Linked Open Usable Data (LOUD) specifications, including the International Image Interoperability Framework (IIIF) Presentation API 3.0, Linked Art, and the Web Annotation Data Model (WADM), have emerged as web standards to facilitate the description and dissemination of these valuable resources. Despite the widespread adoption of IIIF, implementing LOUD specifications, particularly in combination, remains challenging. This is especially evident in the development and assessment of infrastructures, or sites of assemblage, that support these standards. This research is guided by two perspectives: community practices and semantic interoperability. The first perspective assesses how organizations, individuals, and apparatuses engage with and contribute to the consensus-making processes surrounding LOUD. By examining these practices, the social fabrics of the LOUD ecosystem can be better understood. The second perspective focuses on making data meaningful to machines in a standardized, interoperable manner that promotes the exchange of well-formed information. This research is grounded in the SNSF-funded project, *Participatory Knowledge Practices in Analogue and Digital Image Archives* (PIA) (2021–2025), which aims to develop a citizen science platform for three photographic collections from the Cultural Anthropology Switzerland (CAS) archives. Actor-Network Theory (ANT) forms the theoretical foundation, aiming to describe the collaborative structures of the LOUD ecosystem and emphasize the role of non-human actors. Beyond its implementation within the PIA project, this research includes an analysis of the social dynamics within the IIIF and Linked Art communities and an investigation of Yale's Collections Discovery platform, LUX. The research identifies socio-technical requirements for developing specifications aligned with LOUD principles. It also examines how the implementation of LOUD standards in PIA highlights their potential benefits and limitations in facilitating data reuse and broader participation. Additionally, it explores Yale University's large-scale deployment of LOUD standards, emphasizing the importance of ensuring consistency between Linked Art and IIIF resources within the LUX platform for the CH domain. The core methodology of this thesis is an actor- and practice-centered inquiry, focusing on a detailed examination of specific cosmologies within LOUD-driven communities, PIA, and LUX. This micro-perspective approach provides rich empirical evidence to unravel the intricate web of cultural processes and constellations in these contexts. Key empirical findings indicate that LOUD enhances the discoverability and integration of data in CH, requiring community-driven consensus on model interoperability. However, significant challenges include engaging marginalized groups, sustaining long-term participation, and balancing technological and social factors. Strategic use of technology and the capture of digital materiality are critical, but LOUD also poses challenges related to resource investment, data consistency, and the broader implementation of complex patterns. LOUD should lead efforts to improve the accessibility and usability of CH data. The community-driven methodologies of IIIF and Linked Art inherently foster collaboration and transparency, making these standards essential tools in evolving data management practices. Even for institutions and projects that do not adopt these specifications, the socio-technical practices of LOUD offer vital insights into effective digital stewardship and strategies for community engagement.
Brian Sletten

MCP was never going to be “the answer”. It’s a half-assed non-standards-based step in the right direction. Real agentic solutions are going to need richer open world data models, workflows, processing models, etc. I don’t think LMOS is the solution either, but it is closer to what is necessary.

eclipse.dev/lmos/

eclipse.devEclipse LMOS | Eclipse LMOSOpen-source, cloud-native platform for building and running Multi-Agent systems
#ai#linkeddata#agentic
*
Nik | Klampfradler 🎸🚲

Gibt/gab es in Deutschland in letzter Zeit eine Konferenz oder Unkonferenz rund um #LinkedData #RDF #SemanticWeb?

Wenn ja: Bitte antworten und boosten.

Wenn nicht oder nicht bekannt: Bitte abstimmen und boosten.

Weder noch: Bitte boosten ;)!

Ein Barcamp rund um diese Themen…

· 0 votes · Closed
Live feeds
About