<?xml version="1.0" encoding="utf-8"?>
<rss version="2.0" xml:base="https://blog.muninn-project.org"  xmlns:dc="http://purl.org/dc/elements/1.1/">
<channel>
 <title>The Muninn Project - Data</title>
 <link>https://blog.muninn-project.org/taxonomy/term/14</link>
 <description></description>
 <language>en</language>
<item>
 <title>The Business Value of Linked Open Data</title>
 <link>https://blog.muninn-project.org/node/102</link>
 <description>&lt;div class=&quot;field field-name-body field-type-text-with-summary field-label-hidden&quot;&gt;&lt;div class=&quot;field-items&quot;&gt;&lt;div class=&quot;field-item even&quot; property=&quot;content:encoded&quot;&gt;&lt;p class=&quot;rteindent2&quot;&gt;&lt;em&gt;Note: The following is a synopsis of comments I made to the &lt;a href=&quot;http://mw2015.museumsandtheweb.com/proposal/linked-open-data-panel-discussion/&quot;&gt;Publishing and Managing Linked Open Data in Cultural Heritage Institutions&lt;/a&gt; session at Museums on the Web 2015. I&#039;m posting them after a follow up conversation with &lt;a href=&quot;http://cristinapattuelli.com/&quot;&gt;Cristina Pattuelli&lt;/a&gt; of the &lt;a href=&quot;https://linkedjazz.org/&quot;&gt;Linked Jazz Project&lt;/a&gt;.&lt;/em&gt;&lt;/p&gt;
&lt;p&gt;&lt;span style=&quot;font-family: Helvetica;&quot;&gt;What is the business value of Linked Open Data? What is the business case that drives you to support / invest / develop into yet-another-platform and what will it do for your business/library/museum/archive/store-front? Anecdotal, academic and one-off examples aside, why should you care?&lt;/span&gt;&lt;/p&gt;
&lt;p&gt;A quick answer to these questions In three parts: because a) &lt;a href=&quot;#seca&quot;&gt;it promotes and facilitates citation&lt;/a&gt; (eg: Marketing), b) &lt;a href=&quot;#secb&quot;&gt;creates cost externalization opportunities&lt;/a&gt;  (eg: Get other people to do your work) and c) &lt;a href=&quot;#secc&quot;&gt;it leverages the idiosyncrasies of your business&lt;/a&gt; (eg: Your unique selling proposition).&lt;/p&gt;
&lt;!--break--&gt;&lt;h3&gt;
	&lt;a name=&quot;seca&quot; id=&quot;seca&quot;&gt;a) Citations (It&#039;s a popularity contest)&lt;/a&gt;&lt;/h3&gt;
&lt;p style=&quot;margin: 0px; font-family: Helvetica;&quot;&gt;Linked Open Data gives others an automated means to cite your data. At first that does sound like something that an academic would say, but it also means that Linked Open Data gives you a means to market your data.&lt;/p&gt;
&lt;p style=&quot;margin: 0px; font-family: Helvetica; min-height: 14px;&quot;&gt; &lt;/p&gt;
&lt;p style=&quot;margin: 0px; font-family: Helvetica;&quot;&gt;Linked Open Data publishes machine readable data with long term URLs for everything your customers care about. This gives them a reference to point to that can use to tell you what they like, what they want and what they don’t want. Linked Open Data is the primary building block of a sophisticated sales and marketing analysis system.&lt;/p&gt;
&lt;p style=&quot;margin: 0px; font-family: Helvetica;&quot;&gt; &lt;/p&gt;
&lt;p style=&quot;margin: 0px; font-family: Helvetica;&quot;&gt;It’s less trouble to point to something than to copy it: if you copy it, you have to store it and manage it. Why do you think that so many pinning/referencing applications exist? Linked Open Data also makes that data wrangling a little easier and lowers everyone&#039;s costs.&lt;/p&gt;
&lt;p style=&quot;margin: 0px; font-family: Helvetica;&quot;&gt; &lt;/p&gt;
&lt;h3&gt;
	&lt;a name=&quot;secb&quot; id=&quot;secb&quot;&gt;&lt;span style=&quot;font-family: Helvetica;&quot;&gt;b) Externalizing Costs (Let people work to get what they want)&lt;/span&gt;&lt;/a&gt;&lt;/h3&gt;
&lt;p style=&quot;margin: 0px; font-family: Helvetica;&quot;&gt;Costs are a major concern for everyone: needs are infinite, resources are limited. Your website (content management system) is something that takes up a lot of resources, why should you spend on yet another communication mechanism? &lt;/p&gt;
&lt;p style=&quot;margin: 0px; font-family: Helvetica; min-height: 14px;&quot;&gt; &lt;/p&gt;
&lt;p style=&quot;margin: 0px; font-family: Helvetica;&quot;&gt;One of the reason that you spent resources on the website is that creating a solution that can handle everyone’s wants and needs is hard and we all aim for the 80% solution. That leaves the remaining 20% out of luck and resorting to underhanded means like crawling your website, likely to answer a reasonable question that you didn’t think about in the first place.&lt;/p&gt;
&lt;p style=&quot;margin: 0px; font-family: Helvetica; min-height: 14px;&quot;&gt; &lt;/p&gt;
&lt;p style=&quot;margin: 0px; font-family: Helvetica;&quot;&gt;Linked Open Data lets you publish content without the layout and graphical design costs that go into a web site. It also lets you make your content available without having everyone fighting for that coveted front page on the web site. LOD lets other people build applications to answers questions that you haven’t thought about yet. Case in point: &lt;a href=&quot;http://schema.org/&quot;&gt;schema.org&lt;/a&gt; has been working to standardized vocabulary for boring, but useful, questions like when is your building open to visitors.&lt;/p&gt;
&lt;p style=&quot;margin: 0px; font-family: Helvetica; min-height: 14px;&quot;&gt; &lt;/p&gt;
&lt;p style=&quot;margin: 0px; font-family: Helvetica;&quot;&gt;Your website has a salad-bar of icons and links to social media tools, bookmarks and shared content. You bore the cost of finding out about those applications and integrating them with your website. Of course, the popularity of these shift over time, older ones disappear and new ones are created. Why not push that work back on the social tools developers by letting them make a search / discovery interface?&lt;/p&gt;
&lt;p style=&quot;margin: 0px; font-family: Helvetica;&quot;&gt; &lt;/p&gt;
&lt;p style=&quot;margin: 0px; font-family: Helvetica;&quot;&gt;Linked Open Data gives other people the opportunity to do work that will be of benefit to you without requiring you to bare the costs of doing so. Your current web analytics will work at whatever granularity of content that you publish and who knows, maybe that poorly accessioned print will be a masterpiece that was thought lost. Or maybe that bag of obsolete bearings hidden deep in your inventory system is desperately needed by someone else around the world.&lt;/p&gt;
&lt;p style=&quot;margin: 0px; font-family: Helvetica;&quot;&gt; &lt;/p&gt;
&lt;h3 style=&quot;margin: 0px; font-family: Helvetica;&quot;&gt;
	&lt;a name=&quot;secc&quot; id=&quot;secc&quot;&gt;&lt;span style=&quot;font-family: Arial, Verdana, sans-serif;&quot;&gt;c) Data &lt;/span&gt;idiosyncrasies&lt;span style=&quot;font-family: Arial, Verdana, sans-serif;&quot;&gt; &lt;/span&gt;&lt;span style=&quot;font-family: Arial, Verdana, sans-serif;&quot;&gt;(Your business data is a blizzard of beautiful snowflakes)&lt;/span&gt;&lt;/a&gt;&lt;/h3&gt;
&lt;p&gt; &lt;/p&gt;
&lt;p&gt;Parts of your business are unique, others aren&#039;t. There are hundreds of thousands of museums / widgets shops /  locations world wide just like you and yet you have something that makes people want to come to see you because you have what they want. Maybe it&#039;s a &lt;a href=&quot;http://en.wikipedia.org/wiki/Rembrandt&quot;&gt;Rembrandt&lt;/a&gt; (which one?), a replacement servo motor with the right mounting holes for your 3D printer or decent coffee in an otherwise bleak place. Who knows.&lt;/p&gt;
&lt;p&gt;When it comes to software, the common wisdom has been to standardize on commercially available packages unless you really need to roll your own. For many years experts would recommend that you should change the way you do business to the way the software package worked since this was cheaper. Linked Open Data allows you to do both through ontologies that support common standards while using your own definitions. And even if the standards you want to use are incompatible, you can &lt;em&gt;still&lt;/em&gt; work with them.&lt;/p&gt;
&lt;p&gt;Human beings are self-interested and both suppliers and customers will always insist that you use the appropriate data standard: &lt;em&gt;theirs&lt;/em&gt;. The ability to translate across different viewpoints, and in many cases the ability to agree-to-disagree, is a business advantage even before you retain the ability to model your business in the way that it actually happens.&lt;/p&gt;
&lt;h2&gt;
	Common LOD Objections&lt;/h2&gt;
&lt;p class=&quot;rteright&quot;&gt;&lt;em&gt;I&#039;d like to address some objections raised during a few talks at the conference, I regret that this is from memory as I neglected to write down the names of the people that brought these issues up.&lt;/em&gt;&lt;/p&gt;
&lt;h4&gt;
	1. We&#039;ve been talking about this for 10 years and it still hasn&#039;t happened.&lt;/h4&gt;
&lt;p&gt;I&#039;d rather say that we have been talking about this for about 50 years now.&lt;/p&gt;
&lt;p&gt;Many people have tried, the &lt;a href=&quot;http://en.wikipedia.org/wiki/Project_Xanadu&quot;&gt;Xanadu project&lt;/a&gt; is one of the better known projects, but it has taken this long to get the underlying nuts and bolts working. That includes the Internet, the World Wide Web, XML, basic schema&#039;s for Gregorian dates, hypertext, web ontology languages, machine readable time zones, reasoners marginally better integrated than &lt;a href=&quot;http://en.wikipedia.org/wiki/Prolog&quot;&gt;Prolog&lt;/a&gt;, and enough raw data to label everything in natural languages. Linked Open Data is built on all of this.&lt;/p&gt;
&lt;p&gt;It&#039;s been a hell of a trip if you were working on technology in the past 50 years and it&#039;s happening now.&lt;/p&gt;
&lt;h4&gt;
	2. People can find all of this out on my website, why don&#039;t they look there?&lt;/h4&gt;
&lt;p&gt;We have the hubris to think that people care about us when they really only care about our product. Sometimes, the product actually is the website, but not always. To recap an earlier example, if someone cares about Rembrandt they will want to know what works of Rembrandt you have on display, where the works are and when they can see them. The fact that it happens to be the prestigious Janvrin Island Museum of Fine Art is a nice-to-have. Does it matter if they find out through the website, someone&#039;s lovingly curated list of Rembrandt works, or a flyer by the tourism office?&lt;/p&gt;
&lt;p&gt;There are a lot of websites out there. In a world where information relevance is key, every little bit that clearly explains the &quot;unique selling proposition&quot; is an edge.&lt;/p&gt;
&lt;h4&gt;
	3. We can&#039;t give away the intellectual property that is in our data.&lt;/h4&gt;
&lt;p&gt;Information has value in a context; it seems counter-productive to hide the fact that your business has things that someone might want. Linked Open Data also implies Linked Data - perhaps you don&#039;t want to publicly release all of the information within your databases. Perhaps some of it was acquired by subscription to another catalog. If you are unable to publicly release the basic holdings / catalog of your offering (Name, ID Number, Image), you might have a larger problem to worry about than Linked Open Data.  Keep in mind &lt;a href=&quot;#seca&quot;&gt;Section a)&lt;/a&gt; above, the network effects alone increase the value of your own data. The simple act of publishing a URL and a machine readable label goes a long way in making your value obvious to the rest of the market.&lt;/p&gt;
&lt;h4&gt;
	4. There are errors in our data&lt;/h4&gt;
&lt;p&gt;Yes. There are errors in everyone&#039;s data. As the amount of data that you own grows, so does the statistical probability that something will go wrong and that&#039;s before a human being is involved in the process. You organization will likely never have the resources needed to check up on the quality of your entire dataset. As embarrassing as it may be, releasing some of your data in the open will likely result in them pointing out the mistakes in your data without them being asked to do so (&lt;a href=&quot;#secb&quot;&gt;See b&lt;/a&gt;). Their motivation will range from altruism to being vile, either way you will get the benefits of having the errors located.&lt;/p&gt;
&lt;h4&gt;
	5. People will steal my data&lt;/h4&gt;
&lt;p&gt;Yes. People will steal your data. They will crawl your web site. They will use your images as their desktop wall paper. They will cut and paste your website text into their own blog and claim it as their own. They will print your images on posters and sell them on the street corner. Linked Open Data carries the same risks of data theft as having a website but creates new opportunities for revenue, I&#039;d say that&#039;s a win. &lt;/p&gt;
&lt;p&gt; &lt;/p&gt;
&lt;p&gt; &lt;/p&gt;
&lt;/div&gt;&lt;/div&gt;&lt;/div&gt;&lt;div class=&quot;form-item form-type-item&quot;&gt;
  &lt;label&gt;Language &lt;/label&gt;
 English
&lt;/div&gt;
&lt;div class=&quot;field field-name-field-tags field-type-taxonomy-term-reference field-label-above&quot;&gt;&lt;div class=&quot;field-label&quot;&gt;Tags:&amp;nbsp;&lt;/div&gt;&lt;div class=&quot;field-items&quot;&gt;&lt;div class=&quot;field-item even&quot; rel=&quot;dc:subject&quot;&gt;&lt;a href=&quot;/taxonomy/term/49&quot; typeof=&quot;skos:Concept&quot; property=&quot;rdfs:label skos:prefLabel&quot; datatype=&quot;&quot;&gt;lod&lt;/a&gt;&lt;/div&gt;&lt;div class=&quot;field-item odd&quot; rel=&quot;dc:subject&quot;&gt;&lt;a href=&quot;/taxonomy/term/98&quot; typeof=&quot;skos:Concept&quot; property=&quot;rdfs:label skos:prefLabel&quot; datatype=&quot;&quot;&gt;Bottom Line&lt;/a&gt;&lt;/div&gt;&lt;div class=&quot;field-item even&quot; rel=&quot;dc:subject&quot;&gt;&lt;a href=&quot;/taxonomy/term/14&quot; typeof=&quot;skos:Concept&quot; property=&quot;rdfs:label skos:prefLabel&quot; datatype=&quot;&quot;&gt;Data&lt;/a&gt;&lt;/div&gt;&lt;div class=&quot;field-item odd&quot; rel=&quot;dc:subject&quot;&gt;&lt;a href=&quot;/taxonomy/term/99&quot; typeof=&quot;skos:Concept&quot; property=&quot;rdfs:label skos:prefLabel&quot; datatype=&quot;&quot;&gt;MW2015&lt;/a&gt;&lt;/div&gt;&lt;/div&gt;&lt;/div&gt;</description>
 <pubDate>Fri, 24 Apr 2015 13:55:56 +0000</pubDate>
 <dc:creator>warren</dc:creator>
 <guid isPermaLink="false">102 at https://blog.muninn-project.org</guid>
 <comments>https://blog.muninn-project.org/node/102#comments</comments>
</item>
<item>
 <title>SPARQL and Linked Open Data</title>
 <link>https://blog.muninn-project.org/2011/05/sparql-and-linked-open-data</link>
 <description>&lt;div class=&quot;field field-name-body field-type-text-with-summary field-label-hidden&quot;&gt;&lt;div class=&quot;field-items&quot;&gt;&lt;div class=&quot;field-item even&quot; property=&quot;content:encoded&quot;&gt;&lt;p&gt;&lt;img alt=&quot;&quot; src=&quot;sites/default/files/field/image/rdf_w3c_icon.gif&quot; style=&quot;width: 118px; height: 128px; float: left;&quot; /&gt;After a few hiccups with the SPARQL database and the web front end, the Muninn website will be undergoing some major re-work. I&#039;ll update this blog post as the new interface features go online. Update: Feb 23, 2012 - The SPARQL server at &lt;a href=&quot;http://rdf.muninn-project.org/sparql&quot;&gt;http://rdf.muninn-project.org/sparql&lt;/a&gt; is answering queries.&lt;/p&gt;
&lt;!--break--&gt;&lt;/div&gt;&lt;/div&gt;&lt;/div&gt;&lt;div class=&quot;form-item form-type-item&quot;&gt;
  &lt;label&gt;Language &lt;/label&gt;
 English
&lt;/div&gt;
&lt;div class=&quot;field field-name-field-tags field-type-taxonomy-term-reference field-label-above&quot;&gt;&lt;div class=&quot;field-label&quot;&gt;Tags:&amp;nbsp;&lt;/div&gt;&lt;div class=&quot;field-items&quot;&gt;&lt;div class=&quot;field-item even&quot; rel=&quot;dc:subject&quot;&gt;&lt;a href=&quot;/taxonomy/term/13&quot; typeof=&quot;skos:Concept&quot; property=&quot;rdfs:label skos:prefLabel&quot; datatype=&quot;&quot;&gt;SPARQL&lt;/a&gt;&lt;/div&gt;&lt;div class=&quot;field-item odd&quot; rel=&quot;dc:subject&quot;&gt;&lt;a href=&quot;/taxonomy/term/14&quot; typeof=&quot;skos:Concept&quot; property=&quot;rdfs:label skos:prefLabel&quot; datatype=&quot;&quot;&gt;Data&lt;/a&gt;&lt;/div&gt;&lt;div class=&quot;field-item even&quot; rel=&quot;dc:subject&quot;&gt;&lt;a href=&quot;/taxonomy/term/10&quot; typeof=&quot;skos:Concept&quot; property=&quot;rdfs:label skos:prefLabel&quot; datatype=&quot;&quot;&gt;RDF&lt;/a&gt;&lt;/div&gt;&lt;div class=&quot;field-item odd&quot; rel=&quot;dc:subject&quot;&gt;&lt;a href=&quot;/taxonomy/term/4&quot; typeof=&quot;skos:Concept&quot; property=&quot;rdfs:label skos:prefLabel&quot; datatype=&quot;&quot;&gt;OWL&lt;/a&gt;&lt;/div&gt;&lt;/div&gt;&lt;/div&gt;</description>
 <pubDate>Wed, 25 May 2011 05:23:42 +0000</pubDate>
 <dc:creator>warren</dc:creator>
 <guid isPermaLink="false">8 at https://blog.muninn-project.org</guid>
 <comments>https://blog.muninn-project.org/2011/05/sparql-and-linked-open-data#comments</comments>
</item>
<item>
 <title>First data dump from Library and Archives Canada</title>
 <link>https://blog.muninn-project.org/2010/05/first-data-dump-from-library-and-archives-canada</link>
 <description>&lt;div class=&quot;field field-name-body field-type-text-with-summary field-label-hidden&quot;&gt;&lt;div class=&quot;field-items&quot;&gt;&lt;div class=&quot;field-item even&quot; property=&quot;content:encoded&quot;&gt;&lt;p&gt;&lt;img alt=&quot;&quot; src=&quot;sites/default/files/field/image/train-to-lac-dump-150x150.png&quot; style=&quot;width: 150px; height: 150px; float: right;&quot; /&gt;The first data dump from &lt;a href=&quot;http://www.collectionscanada.gc.ca/index-e.html&quot;&gt;Library and Archives Canada&lt;/a&gt; has been shipped to the &lt;a href=&quot;https://www.sharcnet.ca/my/front/&quot;&gt;Sharcnet&lt;/a&gt; data-center and loaded onto the cluster for processing. The data contains scanned images of the enlistment papers of &lt;a href=&quot;http://en.wikipedia.org/wiki/Canadian_Expeditionary_Force&quot;&gt;Canadian Expeditionary Force&lt;/a&gt; soldiers (about a million images) and the full personnel file of about 200 soldiers (about twenty thousand images). The hard drive was first picked up in Ottawa and then traveled with a Muninn staffer to Waterloo, Ontario to one of the Sharcnet machine rooms.&lt;/p&gt;
&lt;!--break--&gt;&lt;p&gt;The contents were copied directly to the disk array of one of the computer cluster to be worked on. The first step will be to catalog every image and link it to its subject. Since the contents of the image is not always known, we have to identify the form that was scanned and the information contained in it before we are able to extract the information. It has been asked why we use hard-drives to move the data from a donor institution to Sharcnet instead of just sending it over the Internet? This has mostly to do with the practical considerations of moving and managing large amounts of data amongst different organizations and systems. Donor institutions do not always have the facilities available to transfer large amounts of data over the wire, nor may they be comfortable doing it for IT security reasons. Another has to do with backing up what is essentially primary source data in the distributed computing system that has become the Muninn back-end: a hard-drive on a shelf is an insurance policy against computing mishaps. The data is being worked on now and should be visible on the online catalog system shortly. We will announce results and extracted data-sets on the blog.&lt;/p&gt;
&lt;/div&gt;&lt;/div&gt;&lt;/div&gt;&lt;div class=&quot;form-item form-type-item&quot;&gt;
  &lt;label&gt;Language &lt;/label&gt;
 English
&lt;/div&gt;
&lt;div class=&quot;field field-name-field-tags field-type-taxonomy-term-reference field-label-above&quot;&gt;&lt;div class=&quot;field-label&quot;&gt;Tags:&amp;nbsp;&lt;/div&gt;&lt;div class=&quot;field-items&quot;&gt;&lt;div class=&quot;field-item even&quot; rel=&quot;dc:subject&quot;&gt;&lt;a href=&quot;/taxonomy/term/6&quot; typeof=&quot;skos:Concept&quot; property=&quot;rdfs:label skos:prefLabel&quot; datatype=&quot;&quot;&gt;Archives&lt;/a&gt;&lt;/div&gt;&lt;div class=&quot;field-item odd&quot; rel=&quot;dc:subject&quot;&gt;&lt;a href=&quot;/taxonomy/term/17&quot; typeof=&quot;skos:Concept&quot; property=&quot;rdfs:label skos:prefLabel&quot; datatype=&quot;&quot;&gt;BEF&lt;/a&gt;&lt;/div&gt;&lt;div class=&quot;field-item even&quot; rel=&quot;dc:subject&quot;&gt;&lt;a href=&quot;/taxonomy/term/14&quot; typeof=&quot;skos:Concept&quot; property=&quot;rdfs:label skos:prefLabel&quot; datatype=&quot;&quot;&gt;Data&lt;/a&gt;&lt;/div&gt;&lt;/div&gt;&lt;/div&gt;</description>
 <pubDate>Wed, 19 May 2010 23:32:00 +0000</pubDate>
 <dc:creator>warren</dc:creator>
 <guid isPermaLink="false">11 at https://blog.muninn-project.org</guid>
 <comments>https://blog.muninn-project.org/2010/05/first-data-dump-from-library-and-archives-canada#comments</comments>
</item>
</channel>
</rss>
