⇒ A Clarification for RDFa in the Browser
On [International Talk Like a Pirate Day](http://www.talklikeapirate.com) , September 19th, I happen to post my [RDFa in the Browser](http://www.milowski.com/journal/entry/2012-09-19T15:38:11.827Z/) entry about using [Green Turtle](http://code.google.com/p/green-turtle/) . I have received some feedback about my use of “typed links” when demonstrating RDFa in action.
⇒ RDFa in the Browser
While there is a lot talk about how [RDFa](http://www.w3.org/TR/rdfa-core/) is or will be used by search engines and others for indexing, my main focus has been on how authors can use RDFa to encode “local knowledge.” Services that are local to the page, most often implemented by inclusion of some script, act upon such local knowledge that is encoded somewhere in the page. In the past, people used the `class` or `id` attributes to identify the targeted content and then some amount of scripting made the rest of the connections.
⇒ Green Turtle - Injection and Microdata Options
I've just released version 1.2 of [Green Turtle](https://code.google.com/p/green-turtle/) and its [Chrome extension](https://chrome.google.com/webstore/detail/green-turtle-rdfa/loggcajcfkpdeoaeihclldihfefijjam) . While there are minor bug fixes, there are three new features:
⇒ Problems with Microdata
Given my recent grumbling about Google Blink developers trying to [remove XSLT](https://groups.google.com/a/chromium.org/forum/#!topic/blink-dev/zIg2KC7PyH0) from Chrome, the current state of Microdata vs [RDFa](http://www.w3.org/TR/rdfa-core/) makes me think we're creating another level of incompatibilities on the Web. XSLT generally failed client-side on the Web due to the poor implementation within the various browsers. At this point, of course people aren't using it en masse because it just didn't work.
⇒ Microdata in Green Turtle
After being asked how hard it would be to add [Microdata](http://dev.w3.org/html5/md-LC/) , at least in some minimal way, to [Green Turtle](https://code.google.com/p/green-turtle/) I decided to find out. Since I already have a bunch of infrastructure, this didn't feel like a hard thing to add. If I did add support, at least experimentally, microdata and RDFa could use the same API and scripting support.
⇒ Retro: Scientific Computing in the Open Web Platform
It has been far too long since I've written about my research, past or present, and I need to correct that. I've been rather silent over the past year or more — life has kept me busy with other things. As such, I have a backlog of information.
⇒ Unified Content Descriptors
The [International Virtual Observatory Alliance (IVOA)](http://www.ivoa.net/) is an organization that helps set the technology standards used by Astronomers on the Web to exchange information. One interesting aspect of astronomical data is that how the data was collected is as important as the particular measurements or images of specific targets. As such, when information is exchanged, semantics about what particular columns of data actual mean and how they related to each other (e.g. an error estimate for another column) is very important.
⇒ Retro: Semantic Hybridization
In 2015, I presented a short paper about "Semantic Hybridization" at [XML Prague 2015](http://www.xmlprague.cz/archive/). It is a technique I've been promoting for using RDFa and JSON-LD together. Rather than make a choice of one or the other, use the strengths of each of the ways of representing semantic annotations. The result is you can often avoid awkward constructions just for the sake of annotations.
⇒ Do Elements have URIs?
I was discussing a problem with triples generated from RDFa and the in-browser applications I have developed using [Green Turtle](https://github.com/alexmilowski/green-turtle) with a learned colleague of mine whose opinions I value greatly. In short, I wanted to duplicate the kinds of processing I'm doing in the browser so I can run it through XProc and do more complicated processing of the documents. Yet, I rely on the *origin of triples* in the document for my application to work.
⇒ Thanks for all the markup + ducks
My good friend Norm Walsh [recently posted](https://norman.walsh.name/2016/05/28/non-standard) about the state of standards development around XML:
⇒ Updates and yet more updates ...
Some rather unfortunate things have been happening in my life, things that just happen because the are bound to happen sometime, like losing my father. I'm reminded of the good things and that life will just continue. In one of his more salient and conscious moments he said to me, as I was pondering my pending trip to Edinburgh, to continue my PhD research and “Go and get the damn thing done!”
⇒ Refactoring the RDFa API - Getting the Data
After numerous inquires about my opinion on making the [RDFa API](http://www.w3.org/TR/rdfa-api/) simpler, I decided to do a bit of research. I've written several fairly complex *in-situ* services that use the RDFa API to provide functionality within the browser. As such, I decided to look at which parts of the RDFa API or the extensions that [Green Turtle ](https://code.google.com/p/green-turtle/) provides are actually used.
⇒ What is the Subject Origin?
[RDFa](http://www.w3.org/TR/rdfa-core/) allow annotations of subjects (identifiers) to exist in multiple locations within a document. When a user tries to retrieve elements by this subject identifier, what element is returned? Currently, the [RDFa API](http://www.w3.org/TR/rdfa-api/) says that all the element origins in the document identified via `@about` , `@resource,` `@src` , `@href` are returned by the `document.getElementsBySubject()` API method.
⇒ Green Turtle 1.0 Released!
I've just released 1.0 of [Green Turtle](https://code.google.com/p/green-turtle/) . My implementation now passes **all** the tests in the W3C conformance test suite for both [RDFa 1.1](http://www.w3.org/TR/rdfa-core/) and [Turtle](http://www.w3.org/TR/turtle/) .