Reading Time: 2 minutes

The announcement that MarkLogic is to add linked data storage to its native XML content repository (April 2013), which was then discussed by David Gorbet at the recent ML User Group London (shown in the photo) was perhaps not so surprising.



Certainly within publishing a very common system design is to have linked data alongside, and pointing to, the content repository. Given that many ML customers are holding linked data, it made sense to allow for that data to be stored in the same box. Obviously there are benefits in having everything in a single repository, from the point of view of administration and security (one box fewer to worry about). But the intriguing aspect is that the linked data will be stored alongside the articles to which they refer. How will this work? The nature of linked data is that it it links to more than one piece of content, so for any triple there are two locations where it might make sense to position the statement. Much remains to be seen, therefore, before seeing how much of an advantage this structure might have for performance. Nonetheless for publishers this initiative has a lot to recommend it: systems are chosen not just for performance but for reliability and for security, and while triplestores have been around for some years, there have not emerged branded enterprise systems in the way that MarkLogic has established itself in the CMS area. The new feature will be available in MarkLogic v7, for release by the end of 2013.