XML, OAC, RDF, JSON-LD and the king stood: the universe is metadata

The Open Annotation Collaboration published a data model in February that should be recognized as disruptive. JavaScript Object Notation for Linked Data whose 1.0 specifications landed November 5th (Tuesday) is another in a cluster of W3C standards that show digital objects are beginning to exist as real things that try to completely represent tangible artifacts and not simply a new whizbang-computery way to offer a limp reference to something real.

Markup, I insist, was the necessary jolt to encourage machine readable encoding. XML is a convenient vehicle to bridge relational tools and linked open data(LOD) (or any triple), but the weight limit of RDF-XML has been exceeded. The standards for annotation are necessary for interoperability and the exposure/discovery of LOD, but is also a very useful way to work with offline, local, or private/siloed data.

I am able to share experience with OAC and the manuscript-focused children of OAC, SharedCanvas and IIIF. These standards were emerging as the transcription tool T-PEN was being completed – it has allowed us to include features that were previously unplanned and filled me with healthy discontent at its completeness. Our current project, a tool for the complete creation of digital editions (focusing on manuscripts) makes heavy use of these standards and is dangerously near spawning a few of its own.

I would like to learn about other efforts in annotation, especially in fields outside of manuscripts. What already exists, what is in flux, and has this shift impacted the way you organize data?

At the very least, I would like to debate whether annotation is a fad or there is a real possibility that markup will get out of the way and we may be left with a single pristine artifact that takes the universe as its metadata.

Categories: Coding, Collaboration, Crowdsourcing, Linked Data, Session Proposals, Session: Talk, Session: Teach |
Profile photo of Patrick Cuba

About Patrick Cuba

While working in student development, surrounded by "people persons," I discovered that I am a "process person." The goal of the Center for Digital Humanities (Digital Theology, at the time) were refreshing and motivating - designing tools to accelerate the human intellect into the decisions for which technology cannot be the solution. My first project with the team was T-PEN (t-pen.org) where I was able to cut my teeth on Interface Design and become a confident "front-end guy." My academic interests have always been comfortably in the humanities, especially the ways in which language allows us to better interact with each other. This lifelong curiosity has dovetailed well with my current employment - enabling humans to interact reliably with the technology that ought to be helping make life easier.

Leave a Reply