In the next several months, it is very likely that the following scenario will be repeated over and over again. The company that you work for sends out email notices saying that, with the pandemic now in the rearview mirror, workers will be expected to return full time to the office, or face being fired.
Over the years, I’ve worked on a number of semantics projects. While some of them involved pulling data from relational databases, one thing that seemed to emerge was that a significant proportion of the metadata within an organization – the operational data that controls everything from movie production to publications to describing businesses – ultimately ended up residing in spreadsheets, specifically, Excel spreadsheets.
Education, especially college education, is facing an existential crisis. Partially due to demographic factors, and in part due to decisions made by policy-makers at national, local, and academic levels, colleges and universities are struggling to stay afloat. What’s more, there are signs that conditions are likely to get far worse for the academic world for at least the next couple of decades. The question this raises ultimately comes down to “what is it that we as a society want out of our education institutions, and what is likely going to need to change for them to survive moving forward?” I hope to be able to provide at least some answers to these question in this issue of The Cagle Report.
SPARQL is a powerful language for working with RDF triples. However, SPARQL can also be difficult to work with, so much so that it often is not utilized anywhere near as often for its advanced capabilities, which include aggregating content, building URIs, and similar uses. This is the second piece in my exploration of OntoText’s GraphDB database, but many of these techniques can be applied with other triple stores as well.
Markdown has become the default choice for producing Readme documentation, especially on GitHub. The new DSC Wordpress environment now supports it natively.
Several years ago, the typical company website fit into a predefined template – a home or landing page (usually talking…
Way back in 1991, Tim Berners-Lee, then a young English software developer working at CERN in Geneva, Switzerland, came up with an intriguing way of combining a communication protocol for retrieving content (HTTP) with a descriptive language for embedding such links into documents (HTML). Shortly thereafter, as more and more people began to create content on these new HTTP servers, it became necessary to be able to provide some kind of mechanism to find this content.