Understanding activation functions better
And making neural networks look a little less magic.
And making neural networks look a little less magic.
Setting some constraints--then violating them!
Last month, in The W3C standard constraint language for RDF: SHACL, I described the history of this new standard that lets us define constraints on RDF data and an open source tool that lets us identify where such constraints were violated. The presence of the standard and tools that let us implement the standard will be a big help to the use of RDF in production environments.
A brief history of the new standard and some toys to play with it.
Lots of columns and commas, but all in the right place.
I recently decided to copy my address book, which I have in an RDF file, to Google Contacts. The basic steps are pretty straightforward:
Queries as data to help you get at more data.
Reference works to get you taking advantage of the fancy parts quickly.
Last month I promised that I would dig further into the Wikidata data model, its mapping to RDF, and how we can take advantage of this with SPARQL queries. I had been trying to understand the structure of the data based on the RDF classes and properties I saw and the documentation that I could find, and some of the vocabulary discussing these issues confused me–for example, RDF is about describing resources, but I was seeing lots of references to entities, which can mean slightly different…
Learning about the data, its structure, and more.
First (SPARQL-oriented) steps.
I’ve written so often about DBpedia here that a few times I considered writing a book about it. As I saw Wikidata get bigger and bigger, I kept postponing the day when I would dig in and learn more about this Wikipedia sibling project. I’ve finally done this, starting with a few basic steps and one extra fun one: