#rdf — Public Fediverse posts

Even as #RDF has become ubiquitous in enterprises and across the web, its awkward handling of #reification — the ability to refer to other statements in a graph — has limited its wider adoption.

@ora and Adrian Gschwend lead the W3C working group that is tackling this problem. RDF 1.2 introduces the reifier, which lets you annotate individual graph relationships with provenance, confidence, and source.

https://knowledgegraphinsights.com/rdf12/

Even as #RDF has become ubiquitous in enterprises and across the web, its awkward handling of #reification — the ability to refer to other statements in a graph — has limited its wider adoption.

@ora and Adrian Gschwend lead the W3C working group that is tackling this problem. RDF 1.2 introduces the reifier, which lets you annotate individual graph relationships with provenance, confidence, and source.

https://knowledgegraphinsights.com/rdf12/

Even as #RDF has become ubiquitous in enterprises and across the web, its awkward handling of #reification — the ability to refer to other statements in a graph — has limited its wider adoption.

@ora and Adrian Gschwend lead the W3C working group that is tackling this problem. RDF 1.2 introduces the reifier, which lets you annotate individual graph relationships with provenance, confidence, and source.

https://knowledgegraphinsights.com/rdf12/

Even as #RDF has become ubiquitous in enterprises and across the web, its awkward handling of #reification — the ability to refer to other statements in a graph — has limited its wider adoption.

@ora and Adrian Gschwend lead the W3C working group that is tackling this problem. RDF 1.2 introduces the reifier, which lets you annotate individual graph relationships with provenance, confidence, and source.

https://knowledgegraphinsights.com/rdf12/

Even as #RDF has become ubiquitous in enterprises and across the web, its awkward handling of #reification — the ability to refer to other statements in a graph — has limited its wider adoption.

@ora and Adrian Gschwend lead the W3C working group that is tackling this problem. RDF 1.2 introduces the reifier, which lets you annotate individual graph relationships with provenance, confidence, and source.

https://knowledgegraphinsights.com/rdf12/

Bibliotheksdaten gibt es überraschen selten als #RDF: Ich habe bislang nur die DNB, BSB, TIB und so halb das BSZ (RDF nur in HTML eingebettet?) sowie das HBZ (JSONLD) gefunden. Richtig nutzbar ist es nur bei der DNB /und dem HBZ/. Dabei wäre es ja ganz interessant, wenn man sich mal durch die Kataloge sparqlen könnte.
#LOD

EDIT: HBZ ergänzt

Bibliotheksdaten gibt es überraschen selten als #RDF: Ich habe bislang nur die DNB, BSB, TIB und so halb das BSZ (RDF nur in HTML eingebettet?) sowie das HBZ (JSONLD) gefunden. Richtig nutzbar ist es nur bei der DNB /und dem HBZ/. Dabei wäre es ja ganz interessant, wenn man sich mal durch die Kataloge sparqlen könnte.
#LOD

EDIT: HBZ ergänzt

Bibliotheksdaten gibt es überraschen selten als #RDF: Ich habe bislang nur die DNB, BSB, TIB und so halb das BSZ (RDF nur in HTML eingebettet?) sowie das HBZ (JSONLD) gefunden. Richtig nutzbar ist es nur bei der DNB /und dem HBZ/. Dabei wäre es ja ganz interessant, wenn man sich mal durch die Kataloge sparqlen könnte.
#LOD

EDIT: HBZ ergänzt

Bibliotheksdaten gibt es überraschen selten als #RDF: Ich habe bislang nur die DNB, BSB, TIB und so halb das BSZ (RDF nur in HTML eingebettet?) sowie das HBZ (JSONLD) gefunden. Richtig nutzbar ist es nur bei der DNB /und dem HBZ/. Dabei wäre es ja ganz interessant, wenn man sich mal durch die Kataloge sparqlen könnte.
#LOD

EDIT: HBZ ergänzt

Bibliotheksdaten gibt es überraschen selten als #RDF: Ich habe bislang nur die DNB, BSB, TIB und so halb das BSZ (RDF nur in HTML eingebettet?) sowie das HBZ (JSONLD) gefunden. Richtig nutzbar ist es nur bei der DNB /und dem HBZ/. Dabei wäre es ja ganz interessant, wenn man sich mal durch die Kataloge sparqlen könnte.
#LOD

EDIT: HBZ ergänzt

Dogfooding was one of RDF’s biggest challenges prior to the arrival of LLMs as powerful general-purpose clients. Why? Because transforming and presenting RDF specifications in RDF form was difficult. Today, that problem is gone. Here’s an example of the new RDF 1.2 primer, deployed as a knowledge graph that uses Linked Data principles to manifest a Semantic Web.

#RDF #SemanticWeb #LinkedData #Explainer #KnowledgeGraphs

Dogfooding was one of RDF’s biggest challenges prior to the arrival of LLMs as powerful general-purpose clients. Why? Because transforming and presenting RDF specifications in RDF form was difficult. Today, that problem is gone. Here’s an example of the new RDF 1.2 primer, deployed as a knowledge graph that uses Linked Data principles to manifest a Semantic Web.

#RDF #SemanticWeb #LinkedData #Explainer #KnowledgeGraphs

Dogfooding was one of RDF’s biggest challenges prior to the arrival of LLMs as powerful general-purpose clients. Why? Because transforming and presenting RDF specifications in RDF form was difficult. Today, that problem is gone. Here’s an example of the new RDF 1.2 primer, deployed as a knowledge graph that uses Linked Data principles to manifest a Semantic Web.

#RDF #SemanticWeb #LinkedData #Explainer #KnowledgeGraphs

Dogfooding was one of RDF’s biggest challenges prior to the arrival of LLMs as powerful general-purpose clients. Why? Because transforming and presenting RDF specifications in RDF form was difficult. Today, that problem is gone. Here’s an example of the new RDF 1.2 primer, deployed as a knowledge graph that uses Linked Data principles to manifest a Semantic Web.

#RDF #SemanticWeb #LinkedData #Explainer #KnowledgeGraphs

Dogfooding was one of RDF’s biggest challenges prior to the arrival of LLMs as powerful general-purpose clients. Why? Because transforming and presenting RDF specifications in RDF form was difficult. Today, that problem is gone. Here’s an example of the new RDF 1.2 primer, deployed as a knowledge graph that uses Linked Data principles to manifest a Semantic Web.

#RDF #SemanticWeb #LinkedData #Explainer #KnowledgeGraphs

TIL:

JSON-LD, used heavily in #ActivityPub, is a way of representing #RDF triplets.

#JSON

TIL:

JSON-LD, used heavily in #ActivityPub, is a way of representing #RDF triplets.

#JSON

TIL:

JSON-LD, used heavily in #ActivityPub, is a way of representing #RDF triplets.

#JSON

TIL:

JSON-LD, used heavily in #ActivityPub, is a way of representing #RDF triplets.

#JSON

TIL:

JSON-LD, used heavily in #ActivityPub, is a way of representing #RDF triplets.

#JSON

The definition of insanity is attempting the same thing twice and expecting different results.

So I’m about to embark on building a #csvw and #rdf qb service for cube data. This time it’s a RESTful API with some #OGC querying patterns baked in.

For the second time. The previous attempt was csvcubed. It because we asked people to write json to have it write more json.

The definition of insanity is attempting the same thing twice and expecting different results.

So I’m about to embark on building a #csvw and #rdf qb service for cube data. This time it’s a RESTful API with some #OGC querying patterns baked in.

For the second time. The previous attempt was csvcubed. It because we asked people to write json to have it write more json.

The definition of insanity is attempting the same thing twice and expecting different results.

So I’m about to embark on building a #csvw and #rdf qb service for cube data. This time it’s a RESTful API with some #OGC querying patterns baked in.

For the second time. The previous attempt was csvcubed. It because we asked people to write json to have it write more json.

The definition of insanity is attempting the same thing twice and expecting different results.

So I’m about to embark on building a #csvw and #rdf qb service for cube data. This time it’s a RESTful API with some #OGC querying patterns baked in.

For the second time. The previous attempt was csvcubed. It because we asked people to write json to have it write more json.

LintedData is a linter for RDF and Ontologies for easy use in CI pipelines, we recently released. It checks for common violations of best practices in ontology engineering.
GitLab: https://gitlab.com/dlr-dw/linteddata/
Docker: https://hub.docker.com/r/dlrdw/linteddata/

Today I present LintedData at the Helmholtz Metadata Conference 2026 demo session.
Abstract & Poster: https://elib.dlr.de/223803/

#RDF #Ontologies #KnowledgeGraphs #DataQuality #OntologyQuality #OntologyEngineering #HMC2026 @helmholtz_hmc

LintedData is a linter for RDF and Ontologies for easy use in CI pipelines, we recently released. It checks for common violations of best practices in ontology engineering.
GitLab: https://gitlab.com/dlr-dw/linteddata/
Docker: https://hub.docker.com/r/dlrdw/linteddata/

Today I present LintedData at the Helmholtz Metadata Conference 2026 demo session.
Abstract & Poster: https://elib.dlr.de/223803/

#RDF #Ontologies #KnowledgeGraphs #DataQuality #OntologyQuality #OntologyEngineering #HMC2026 @helmholtz_hmc

LintedData is a linter for RDF and Ontologies for easy use in CI pipelines, we recently released. It checks for common violations of best practices in ontology engineering.
GitLab: https://gitlab.com/dlr-dw/linteddata/
Docker: https://hub.docker.com/r/dlrdw/linteddata/

Today I present LintedData at the Helmholtz Metadata Conference 2026 demo session.
Abstract & Poster: https://elib.dlr.de/223803/

#RDF #Ontologies #KnowledgeGraphs #DataQuality #OntologyQuality #OntologyEngineering #HMC2026 @helmholtz_hmc

LintedData is a linter for RDF and Ontologies for easy use in CI pipelines, we recently released. It checks for common violations of best practices in ontology engineering.
GitLab: https://gitlab.com/dlr-dw/linteddata/
Docker: https://hub.docker.com/r/dlrdw/linteddata/

Today I present LintedData at the Helmholtz Metadata Conference 2026 demo session.
Abstract & Poster: https://elib.dlr.de/223803/

#RDF #Ontologies #KnowledgeGraphs #DataQuality #OntologyQuality #OntologyEngineering #HMC2026 @helmholtz_hmc

LintedData is a linter for RDF and Ontologies for easy use in CI pipelines, we recently released. It checks for common violations of best practices in ontology engineering.
GitLab: https://gitlab.com/dlr-dw/linteddata/
Docker: https://hub.docker.com/r/dlrdw/linteddata/

Today I present LintedData at the Helmholtz Metadata Conference 2026 demo session.
Abstract & Poster: https://elib.dlr.de/223803/

#RDF #Ontologies #KnowledgeGraphs #DataQuality #OntologyQuality #OntologyEngineering #HMC2026 @helmholtz_hmc

[#veille] Mise en ligne de l'application web GARANCE - Référentiels et entités sémantisés des Archives nationales
https://www.archives-nationales.culture.gouv.fr/actualites-professionnelles/mise-en-ligne-de-lapplication-web-garance
#lod #archivesnationales #linkeddata #archives #rdf #sparql #ricO #skos #fairdata

[#veille] Mise en ligne de l'application web GARANCE - Référentiels et entités sémantisés des Archives nationales
https://www.archives-nationales.culture.gouv.fr/actualites-professionnelles/mise-en-ligne-de-lapplication-web-garance
#lod #archivesnationales #linkeddata #archives #rdf #sparql #ricO #skos #fairdata

[#veille] Mise en ligne de l'application web GARANCE - Référentiels et entités sémantisés des Archives nationales
https://www.archives-nationales.culture.gouv.fr/actualites-professionnelles/mise-en-ligne-de-lapplication-web-garance
#lod #archivesnationales #linkeddata #archives #rdf #sparql #ricO #skos #fairdata

[#veille] Mise en ligne de l'application web GARANCE - Référentiels et entités sémantisés des Archives nationales
https://www.archives-nationales.culture.gouv.fr/actualites-professionnelles/mise-en-ligne-de-lapplication-web-garance
#lod #archivesnationales #linkeddata #archives #rdf #sparql #ricO #skos #fairdata

[#veille] Mise en ligne de l'application web GARANCE - Référentiels et entités sémantisés des Archives nationales
https://www.archives-nationales.culture.gouv.fr/actualites-professionnelles/mise-en-ligne-de-lapplication-web-garance
#lod #archivesnationales #linkeddata #archives #rdf #sparql #ricO #skos #fairdata

The linked data viewer / dereferencer LDView can now be used without an expensive SPARQL endpoint.
Just convert your RDF data to the hdt format and use that as a datasource. You can even SPARQL them using the integrated Yasgui interface.

Above all, LDView attempts to offer a human friendly interface for providing RDF data.

https://codeberg.org/renevoorburg/ldview

#linkedata #rdf #ldview

The linked data viewer / dereferencer LDView can now be used without an expensive SPARQL endpoint.
Just convert your RDF data to the hdt format and use that as a datasource. You can even SPARQL them using the integrated Yasgui interface.

Above all, LDView attempts to offer a human friendly interface for providing RDF data.

https://codeberg.org/renevoorburg/ldview

#linkedata #rdf #ldview

The linked data viewer / dereferencer LDView can now be used without an expensive SPARQL endpoint.
Just convert your RDF data to the hdt format and use that as a datasource. You can even SPARQL them using the integrated Yasgui interface.

Above all, LDView attempts to offer a human friendly interface for providing RDF data.

https://codeberg.org/renevoorburg/ldview

#linkedata #rdf #ldview

The linked data viewer / dereferencer LDView can now be used without an expensive SPARQL endpoint.
Just convert your RDF data to the hdt format and use that as a datasource. You can even SPARQL them using the integrated Yasgui interface.

Above all, LDView attempts to offer a human friendly interface for providing RDF data.

https://codeberg.org/renevoorburg/ldview

#linkedata #rdf #ldview

The linked data viewer / dereferencer LDView can now be used without an expensive SPARQL endpoint.
Just convert your RDF data to the hdt format and use that as a datasource. You can even SPARQL them using the integrated Yasgui interface.

Above all, LDView attempts to offer a human friendly interface for providing RDF data.

https://codeberg.org/renevoorburg/ldview

#linkedata #rdf #ldview

Linked data viewer / resolver LDView has improved display of blank nodes / skolems and inverse relations.

https://codeberg.org/renevoorburg/ldview

#rdf #linkeddata

Linked data viewer / resolver LDView has improved display of blank nodes / skolems and inverse relations.

https://codeberg.org/renevoorburg/ldview

#rdf #linkeddata

Linked data viewer / resolver LDView has improved display of blank nodes / skolems and inverse relations.

https://codeberg.org/renevoorburg/ldview

#rdf #linkeddata

Linked data viewer / resolver LDView has improved display of blank nodes / skolems and inverse relations.

https://codeberg.org/renevoorburg/ldview

#rdf #linkeddata

Linked data viewer / resolver LDView has improved display of blank nodes / skolems and inverse relations.

https://codeberg.org/renevoorburg/ldview

#rdf #linkeddata

Dear @timbl,
I kindly ask you to consider talking to the people at #Mozilla to keep #xml documents with human-friendly rendering via #xslt visible in #Firefox.

Not only needs the web decentralisation, but also raw, machine-readable data in human-friendly appearance. #Feeds, #RDF, etc. Dropping #w3c standards and backwards-compatibiity in this regard makes the web an unreliable medium for long-term publishing and archiving of such documents, even more so for small entities with limited resources. Big players have no problem continuously overhauling their archives to meet the viewers' habits du-jour and adapt to fast-moving, volatile practices.

Please say no to this #enshittification.

Yours,
@mro

P.S.: I pledge a monthly Euro to such a browser.

Dear @timbl,
I kindly ask you to consider talking to the people at #Mozilla to keep #xml documents with human-friendly rendering via #xslt visible in #Firefox.

Not only needs the web decentralisation, but also raw, machine-readable data in human-friendly appearance. #Feeds, #RDF, etc. Dropping #w3c standards and backwards-compatibiity in this regard makes the web an unreliable medium for long-term publishing and archiving of such documents, even more so for small entities with limited resources. Big players have no problem continuously overhauling their archives to meet the viewers' habits du-jour and adapt to fast-moving, volatile practices.

Please say no to this #enshittification.

Yours,
@mro

P.S.: I pledge a monthly Euro to such a browser.

Dear @timbl,
I kindly ask you to consider talking to the people at #Mozilla to keep #xml documents with human-friendly rendering via #xslt visible in #Firefox.

Not only needs the web decentralisation, but also raw, machine-readable data in human-friendly appearance. #Feeds, #RDF, etc. Dropping #w3c standards and backwards-compatibiity in this regard makes the web an unreliable medium for long-term publishing and archiving of such documents, even more so for small entities with limited resources. Big players have no problem continuously overhauling their archives to meet the viewers' habits du-jour and adapt to fast-moving, volatile practices.

Please say no to this #enshittification.

Yours,
@mro

P.S.: I pledge a monthly Euro to such a browser.

Dear @timbl,
I kindly ask you to consider talking to the people at #Mozilla to keep #xml documents with human-friendly rendering via #xslt visible in #Firefox.

Not only needs the web decentralisation, but also raw, machine-readable data in human-friendly appearance. #Feeds, #RDF, etc. Dropping #w3c standards and backwards-compatibiity in this regard makes the web an unreliable medium for long-term publishing and archiving of such documents, even more so for small entities with limited resources. Big players have no problem continuously overhauling their archives to meet the viewers' habits du-jour and adapt to fast-moving, volatile practices.

Please say no to this #enshittification.

Yours,
@mro

P.S.: I pledge a monthly Euro to such a browser.

Dear @timbl,
I kindly ask you to consider talking to the people at #Mozilla to keep #xml documents with human-friendly rendering via #xslt visible in #Firefox.

Not only needs the web decentralisation, but also raw, machine-readable data in human-friendly appearance. #Feeds, #RDF, etc. Dropping #w3c standards and backwards-compatibiity in this regard makes the web an unreliable medium for long-term publishing and archiving of such documents, even more so for small entities with limited resources. Big players have no problem continuously overhauling their archives to meet the viewers' habits du-jour and adapt to fast-moving, volatile practices.

Please say no to this #enshittification.

Yours,
@mro

P.S.: I pledge a monthly Euro to such a browser.

The RDF & SPARQL Working Group invites implementations of two Candidate Recommendation Snapshots.

The Resource Description Framework (RDF) is a framework for representing information on the Web. The RDF 1.2 Concepts and Abstract Data Model defines an abstract data model which serves to link all RDF-based languages and specifications.

RDF 1.2 Semantics describes a precise semantics for RDF 1.2 Concepts and Abstract Data Model and RDF 1.2 Schema
#WebStandards #RDF
https://www.w3.org/news/2026/w3c-invites-implementations-of-rdf-1-2-concepts-and-abstract-data-model-and-rdf-1-2-semantics/