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.
Linked data viewer / resolver LDView has improved display of blank nodes / skolems and inverse relations.
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.
Anonymous Nodes for SASSY
The anonymous nodes will be resource nodes that use a URI with a fragment that is a generated id.
The generated ids in the RDF Redland C library use time and PID as their basis, with a local sequence number for each id generated in the session. This might have collisions in a distributed system - unlikely, but not quite unlikely enough. Something based on a UUID would be better.
The UUID library generates a 128 bit random number in 16 bytes. This string is not URI friendly. A URI fragment can have alpha and numeric characters and a very small set of other characters. Only two are necessary if we use base64 encoding - underscore and hyphen would seem to be the best choices.
To avoid soaking up all the randomness only one UUID needs to be created for each session. Subsequent requests can have a sequence number added. A decimal point, separating the UUID part from the sequence number, can make the values a bit more readable.
We now have a representation for the anonymous nodes. Next is to write the generator....
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/
📢 Nächstes Treffen der TWG FuzzyWobblySW
🗓️ 22. April 2026
🕜 10:00 - 11:30 Uhr
🔗 Zoom: https://uni-frankfurt.zoom-x.de/j/91655933093?pwd=aEM4YmtFV1g1SmNDVzRaTU4yaThOZz09
🎯 Präsentation & Diskussion zu Use Cases
SASSY has hit a wall, part 3
So, how to proceed?
RDF is a foundational part of this version of SASSY. It is possible that other graph databases might get used in the final version, but for now its RDF. It needs to be used correctly or it will be an unending source of problems.
This implies that probably all the blank nodes need to be replaced by resource nodes (URIs). These I will call anonymous nodes.
The plan:
+ Decide on the representation for these anonymous nodes. Sequence numbers or UUIDs seem to be the obvious alternatives.
+ Update my RDF library to create these nodes.
+ Write a program to turn the existing blank nodes into anonymous nodes.
+ Update all the SASSY projects to use the new code.
3/3
SASSY has hit a wall, part 2.
The rule engine uses SPARQL to find the data the rules are to be applied to. Blank nodes break this design.
When I first started SASSY I avoided blank nodes. As time went on I realised that generated names for nodes was going to save a lot of time, so I used them in lists and other places where names did not add any real information to the model.
My initial design for generated names was OK for toy examples, but was not going to work well for a multi-user distributed system. Hence I moved to using blank nodes that have identifiers which are mini-UUIDs.
So the early version of the rule engine worked OK since it used generated names. It is only the more recent data that uses the blank nodes, and the world fell apart.
2/n
SASSY has hit a wall.
I was debugging the rule engine, finding easy bugs at first, and getting steadily harder to resolve as work proceeded. This is normal.
In the end the results were really strange with some odd messages from the underlying RDF library.
It seems I have misunderstood a fundamental component of RDF, the blank node.
The blank node is often described as being useful in things like linked lists or other structural uses where naming the node with a URI would seem redundant. This leads to problems.
The correct use is as a placeholder for when the identity of the node is not known. For example, the perpetrator of a crime before a suspect has been identified. There must be somebody, but they are unknown.
Mostly both uses work. The gotcha is SPARQL. You cannot give it a blank node to search on. If you do it treats it as a variable to be bound to some value.
1/n