jschneider + linkeddata 460
Smart Content Re-viewed: Text Analytics and Semantic Content Enrichment
february 2012 by jschneider
"There are other solution providers in the content analytics meets semantic annotation/enrichment game. In addition to IBM and Ontotext, they include HP Autonomy, MarkLogic, OpenText, Temis, and the nascent, open-source IKS project. Other vendors offer enterprise-strength building blocks, for instance, SAS via the various SAS Text Analytics components."
text-analytics
NLP
datamining
visualization
content-analytics
content-enrichment
semantic-content-enrichment
linkeddata
ontologies
february 2012 by jschneider
Bibliographic Framework: RDF and Linked Data
january 2012 by jschneider
"There are some differences between them (e.g. RDA separates place of publication, manufacture, production while ISBD does not) but clearly they should descend from a common ancestor:
RDA: place of publication
RDA: place of distribution
RDA: place of manufacture
FRBRer: has place of publication or distribution
ISBD: has place of publication, production, distribution
This would be annoying, but not unworkable, if these different instances of "place of publication" could be treated as having some meaning in common such that one could link a FRBRer element to an ISBD element, but they cannot. The reason they cannot is that each of these constrains the elements in a particular way that defines its relationship to a single data context (what we generally think of as a "record structure"). The elements are not independent of that context, and this means that each can only be used within that particular context. This is the antithesis of the linked data concept, where data sets from diverse sources share metadata elements. It is this re-use of elements that creates the "link" in linked data. To achieve this, metadata elements need to be unconstrained by a particular context. "
RDF
lld
linkeddata
RDA: place of publication
RDA: place of distribution
RDA: place of manufacture
FRBRer: has place of publication or distribution
ISBD: has place of publication, production, distribution
This would be annoying, but not unworkable, if these different instances of "place of publication" could be treated as having some meaning in common such that one could link a FRBRer element to an ISBD element, but they cannot. The reason they cannot is that each of these constrains the elements in a particular way that defines its relationship to a single data context (what we generally think of as a "record structure"). The elements are not independent of that context, and this means that each can only be used within that particular context. This is the antithesis of the linked data concept, where data sets from diverse sources share metadata elements. It is this re-use of elements that creates the "link" in linked data. To achieve this, metadata elements need to be unconstrained by a particular context. "
january 2012 by jschneider
Local library data in the new global framework @ CommonPlace.Net
january 2012 by jschneider
"n essence only really unique data is worth publishing. You link to the rest.
Currently, library data that is really unique and interesting is administrative information about holdings and circulation. After having found metadata about a potentially relevant publication it is very useful for someone to know how and where to get access to it, if it’s not freely available online. Do you need to go to a specific library location to get the physical item, or to have access to the online article? Do you have to be affiliated to a specific institution to be entitled to borrow or access it?""No libraries in sight yet. For accessing freely available digital content on the web you actually don’t need a library, unless you need professional assistance finding the correct and relevant information. Here we have identified a possible role of librarians in this new networked information model.""Getting new software, systems and tools for both back end administrative functions and front end information finding needs. For this we need efforts from traditional library systems vendors but also from developers in libraries.
Establishing future roles for libraries, librarians and information professionals in the new framework. This may turn out to be the most important issue.
"
lld
libraries
linkeddata
opendata
Currently, library data that is really unique and interesting is administrative information about holdings and circulation. After having found metadata about a potentially relevant publication it is very useful for someone to know how and where to get access to it, if it’s not freely available online. Do you need to go to a specific library location to get the physical item, or to have access to the online article? Do you have to be affiliated to a specific institution to be entitled to borrow or access it?""No libraries in sight yet. For accessing freely available digital content on the web you actually don’t need a library, unless you need professional assistance finding the correct and relevant information. Here we have identified a possible role of librarians in this new networked information model.""Getting new software, systems and tools for both back end administrative functions and front end information finding needs. For this we need efforts from traditional library systems vendors but also from developers in libraries.
Establishing future roles for libraries, librarians and information professionals in the new framework. This may turn out to be the most important issue.
"
january 2012 by jschneider
Linked Literature, Linked TV – Everything Looks like a Graph
december 2011 by jschneider
"In NoTube, we used Mahout to compute similarity measures between each pair of items in a catalogue of BBC TV programmes for which we had privileged access to subjective viewer ratings. This was a sparse matrix of around 20,000 viewers, 12,500 broadcast items, with around 1.2 million ratings linking viewer to item. From these, after a few rather-too-casual tests using Mahout’s evaluation measure system, we picked its most promising similarity measure for our data (LogLikelihoodSimilarity or Tanimoto), and then for the most similar items, simply dumped out a huge data file that contained pairs of item numbers, plus a weight."
graphs
data
linkeddata
Dan
Brickley
NoTube
collaborative-filtering
december 2011 by jschneider
Using RDFa 1.1 Lite with Schema.org
december 2011 by jschneider
via http://twitter.com/#!/manusporny/status/135065619052756992
rdfa
linkeddata
schema.org
december 2011 by jschneider
Library of Congress Provides Details About Transition Away From MARC
october 2011 by jschneider
via http://twitter.com/#!/paulwroberts/status/131100301016039424
LC
MARC
RDF
linkeddata
lld
october 2011 by jschneider
The Real Challenge for RDF is Yet to Come | Internet Alchemy
august 2011 by jschneider
"This is a typical characteristic of technical paradigm shifts. No-one thought they had the problem of not being able to speak to anyone they liked wherever they were until the cellphone arrived and shifted expectations.
Right now, no-one realises they have the problem of not being able to merge and combine data from thousands of different primary sources. Most people aren’t thinking about it and those that do are facing an economic barrier, not a technical one. We know a general technical solution exists but the benefit/cost ratio needs to be high enough to warrant using a general solution over a custom one and today the costs of integrating data at scale are too high for most even given the massive benefits that could be possible."
RDF
linkeddata
datamodels
Right now, no-one realises they have the problem of not being able to merge and combine data from thousands of different primary sources. Most people aren’t thinking about it and those that do are facing an economic barrier, not a technical one. We know a general technical solution exists but the benefit/cost ratio needs to be high enough to warrant using a general solution over a custom one and today the costs of integrating data at scale are too high for most even given the massive benefits that could be possible."
august 2011 by jschneider
British Library Data Model: Overview | Talis Consulting
august 2011 by jschneider
"The obvious answer is ‘a book’ or ‘a serial’. The next questions follow from that initial one, and build a picture of what the cataloguer is holding.
Who wrote the book?
When was the book published?
Who published the book?
Where was the book published?
What is the book about?
What language is it written in?
My view is that none of these questions result in complex answers like “The book is a work which is a manifestation of an idea by a person who may or may not have actually written the words contained in the book, of which I hold one example of in my hands”. We simply don’t do that in our everyday understanding of what a book is. Rob Styles eloquently articulated this in his blog post Bringing FRBR down to earth.""BNB data was not originally created for machine intelligibility. The mark-up in a MARC record was originally intended to reduce printing costs and is therefore more concerned with presentation than meaning. There are myriad nuances to unpick when working out what is intended by a particular piece of information about a book. In many cases cataloguing practice has changed over time (or indeed the norms have changed), so the data may be unreliable or require further processing before it can be used. In some cases, this data unreliability has meant that the model has become simpler, in order to support the data available, rather than being as expressive as first envisaged."
datamodels
linkeddata
lld
Who wrote the book?
When was the book published?
Who published the book?
Where was the book published?
What is the book about?
What language is it written in?
My view is that none of these questions result in complex answers like “The book is a work which is a manifestation of an idea by a person who may or may not have actually written the words contained in the book, of which I hold one example of in my hands”. We simply don’t do that in our everyday understanding of what a book is. Rob Styles eloquently articulated this in his blog post Bringing FRBR down to earth.""BNB data was not originally created for machine intelligibility. The mark-up in a MARC record was originally intended to reduce printing costs and is therefore more concerned with presentation than meaning. There are myriad nuances to unpick when working out what is intended by a particular piece of information about a book. In many cases cataloguing practice has changed over time (or indeed the norms have changed), so the data may be unreliable or require further processing before it can be used. In some cases, this data unreliability has meant that the model has become simpler, in order to support the data available, rather than being as expressive as first envisaged."
august 2011 by jschneider
furialog
july 2011 by jschneider
"If you want to stage a grassroots revolution, you need to figure out four things:
- What is the big change you're going to bring about?
- What's the work that has to be done?
- Who has to do the work?
- What's in it for them? "
semanticweb
linkeddata
scalability
- What is the big change you're going to bring about?
- What's the work that has to be done?
- Who has to do the work?
- What's in it for them? "
july 2011 by jschneider
Linked Data life cycles
july 2011 by jschneider
"Based on our experience in Linked Data publishing and consumption over the past years, we have identify involved parties and fundamental phases, which provide for a multitude of so called Linked Data life cycles."
linkeddata
july 2011 by jschneider
Southampton ECS Web Team › Linked Data vs Open Data vs RDF Data
july 2011 by jschneider
" “Open Data” is a policy; “Linked Data” is an approach and “RDF” is a data structure."
opendata
linkeddata
RDF
july 2011 by jschneider
inkdroid › stanford linked data meeting notes & an incidental manifesto
july 2011 by jschneider
"One thing that has stuck with me a few weeks later, is the continued need in the cultural heritage Linked Data sector for reconciliation services, that help people connect up their resources with appropriate resources that other folks have published. If you work for a large organization, there is often even a need for reconciliation services within the enterprise. For example the British Library reported that it has some 300 distinct data systems within the organization, that sometimes need to be connected together. Linking is the essential ingredient, the sine qua non of Linked Data. Linking is what makes Linked Data and the RDF data model different. It helps you express the work you may have done in joining up your datas with other people’s data. It’s the 4th design pattern in Tim Berners-Lee’s Linked Data Design Issues:""Manifesto for Linked Libraries
We are uncovering better ways of publishing, sharing and using information by doing it and helping others do it. Through this work we have come to value:
Publishing data on the Web for discovery over preserving it in dark archives.
Continuous improvement of data over waiting to publish perfect data.
Semantically structured data over flat unstructured data.
Collaboration over working alone.
Web standards over domain-specific standards.
Use of open, commonly understood licenses over closed, local licenses.
That is, while there is value in the items on the right, we value the items on the left more."
linkeddata
lld
CLIR
reconciliation
licensing
opendata
We are uncovering better ways of publishing, sharing and using information by doing it and helping others do it. Through this work we have come to value:
Publishing data on the Web for discovery over preserving it in dark archives.
Continuous improvement of data over waiting to publish perfect data.
Semantically structured data over flat unstructured data.
Collaboration over working alone.
Web standards over domain-specific standards.
Use of open, commonly understood licenses over closed, local licenses.
That is, while there is value in the items on the right, we value the items on the left more."
july 2011 by jschneider
LODUM: Linked Open Data University of Münster - About
july 2011 by jschneider
via http://twitter.com/#!/olafhartig/status/89206569346142208
linkeddata
july 2011 by jschneider
related tags
*** ⊕ **** ⊕ ***** ⊕ aboutness ⊕ academia ⊕ acadmia ⊕ access-controls ⊕ ads ⊕ aggregation ⊕ ALA ⊕ alpha ⊕ amber ⊕ ambiguity ⊕ analogies ⊕ analysis ⊕ android ⊕ annotated-data ⊕ annotation ⊕ annotations ⊕ apache ⊕ api ⊕ application-profiles ⊕ archaeology ⊕ archives ⊕ ASIST ⊕ astronomy ⊕ astrophysics ⊕ Atom ⊕ authentication ⊕ authenticity ⊕ authorities ⊕ awesome ⊕ Ayers ⊕ BagIt ⊕ bbc ⊕ Ben ⊕ Ben-O'Steen ⊕ Berners-Lee ⊕ bestbuy ⊕ bestpractices ⊕ beyondthepdf ⊕ bibliographic-data ⊕ bibliographies ⊕ bibliography ⊕ bibo ⊕ bioinformatics ⊕ biology ⊕ biomedicine ⊕ blogging ⊕ blogs ⊕ books ⊕ bottom-up ⊕ Bradley ⊕ Brickley ⊕ browsers ⊕ builtworks ⊕ business-intelligence ⊕ business-models ⊕ businessmodels ⊕ c4l09 ⊕ Calhoun ⊕ Cambridge ⊕ cancer ⊕ cataloging ⊕ catalogs ⊕ cherryblossoms ⊕ Chronicling-America ⊕ Chudnov ⊕ CIDOC-CRM ⊕ citation ⊕ citations ⊕ citeulike ⊕ Clark ⊕ classification ⊕ Clay ⊕ clerezza ⊕ CLIR ⊕ cloud-computing ⊕ code4lib ⊕ collaboration ⊕ collaborative-filtering ⊕ collection-level-description ⊕ companies ⊕ competence ⊕ compilations ⊕ composability ⊕ concept-oriented ⊕ conferences ⊕ containers ⊕ content-analytics ⊕ content-enrichment ⊕ content-negotiation ⊕ context ⊕ contrlled-vocabularies ⊕ controlled-vocabularies ⊕ cooperative-cataloging ⊕ coordination ⊕ copying ⊕ copyright ⊕ copyright-law ⊕ coyle ⊕ creativecommons ⊕ criteria ⊕ crossref ⊕ crossrefopenurl ⊕ crowd-sourcing ⊕ csv ⊕ culturalheritage ⊕ culture ⊕ cycling ⊕ Dan ⊕ Danny ⊕ data ⊕ data-curation ⊕ data-integration ⊕ data-modelling ⊕ data-portability ⊕ data-quality ⊕ data.gov ⊕ data.gov.uk ⊕ databases ⊕ datacuration ⊕ dataincubator ⊕ datamining ⊕ datamodels ⊕ dataportability ⊕ datasets ⊕ davis ⊕ dbpedia ⊕ DC ⊕ dchud ⊕ DCMI ⊕ DDC ⊕ decentralization ⊕ deeplinks ⊕ del.icio.us ⊕ deri ⊕ derivatives ⊕ description ⊕ description-logics ⊕ design-patterns ⊕ designpatterns ⊕ Dewey ⊕ digitalhistory ⊕ digitalhumaniites ⊕ digitalhumanities ⊕ digitalpreservation ⊕ disambiguation ⊕ distributed ⊕ distributed-publishing ⊕ distributed-search ⊕ djatoka ⊕ DLF ⊕ DNB ⊕ document-centric ⊕ documentation ⊕ documents ⊕ doi ⊕ domain-modeling ⊕ drupal ⊕ DublinCore ⊕ EAD ⊕ economies-of-scale ⊕ ed ⊕ edsu ⊕ egovernment ⊕ ELAG10 ⊕ Elsevier ⊕ energy ⊕ enterprise2.0 ⊕ EPUB ⊕ eRDF ⊕ Eric ⊕ escience ⊕ Europeana ⊕ events ⊕ examples ⊕ exercises ⊕ facebook ⊕ facebook-for-dead-people ⊕ facets ⊕ Fiona ⊕ FOAF ⊕ frameworks ⊕ frbr ⊕ freebase ⊕ Fuseki ⊕ fusion-tables ⊕ geek-humor ⊕ geeks ⊕ geneology ⊕ genes ⊕ geolocation ⊕ Germany ⊕ GGG ⊕ GIS ⊕ Glen ⊕ googlebooks ⊕ gov2.0 ⊕ govdocs ⊕ government2.0 ⊕ graphs ⊕ Guardian ⊕ guidelines ⊕ Harvard ⊕ HCLS ⊕ health ⊕ Hellman ⊕ history ⊕ hospitals ⊕ html5 ⊕ http ⊕ httpRange-14 ⊕ humor ⊕ hypertext ⊕ i18n ⊕ Ian ⊕ Ian-Davis ⊕ Idehen ⊕ identi.ca ⊕ identifiers ⊕ identiifers ⊕ identities ⊕ ILS ⊕ images ⊕ IMDB ⊕ indexing ⊕ information-resources ⊕ inline ⊕ insomnia ⊕ instances ⊕ institutional-identifiers ⊕ integration ⊕ intellectual-property ⊕ interesting ⊕ interoperability ⊕ inverse-network-effect ⊕ Ireland ⊕ iswc2009 ⊕ Jakob ⊕ Japan ⊕ Jeni ⊕ JISC ⊕ John ⊕ Jon ⊕ journalism ⊕ journalist ⊕ Juan-Sequeda ⊕ karen ⊕ Kingsley ⊕ korea ⊕ l10n ⊕ LC ⊕ lcsh ⊕ lcsh.info ⊕ ldow2009 ⊕ legal ⊕ libraries ⊕ LibraryThing ⊕ LIBRIS ⊕ licensing ⊕ lifesciences ⊕ Lin ⊕ LingPipe ⊕ linked-data ⊕ linkeddata ⊖ linkedopendata ⊕ linkedscience ⊕ linking ⊕ linkrel=canonical ⊕ links ⊕ lld ⊕ LLDXG ⊕ LoC ⊕ LOCAH ⊕ local ⊕ local-government ⊕ location ⊕ lodlam ⊕ london ⊕ Lovecraft ⊕ machine-readable-data ⊕ maps ⊕ MARC ⊕ Mark ⊕ mashups ⊕ math ⊕ mediation ⊕ metadata ⊕ metamorph ⊕ Metcalfe's-Law ⊕ METS ⊕ microblogging ⊕ microformats ⊕ Miller ⊕ mime ⊕ MIT ⊕ mobile ⊕ modeling ⊕ MODS ⊕ movies ⊕ mugs ⊕ multilingual ⊕ museums ⊕ music ⊕ MusicBrainz ⊕ named-entities ⊕ named-graphs ⊕ namedgraphs ⊕ naming ⊕ NASA ⊕ Nature ⊕ navigation ⊕ NCSA ⊕ neologism ⊕ netneutrality ⊕ network-effect ⊕ newspapers ⊕ Newton ⊕ NKOS ⊕ NLP ⊕ Nodalities ⊕ normalization ⊕ nosql ⊕ notube ⊕ NUIG ⊕ numismatic ⊕ nyc ⊕ nytimes ⊕ O'Steen ⊕ OAC ⊕ OAI ⊕ OAI-ORE ⊕ OAI-PMH ⊕ obama ⊕ Ockerbloom ⊕ oclc ⊕ Oh ⊕ oncology ⊕ online-arguments ⊕ ontologies ⊕ opac ⊕ open ⊕ opencyc ⊕ opendata ⊕ openddata ⊕ opengraph ⊕ openlibrary ⊕ openness ⊕ opensource ⊕ openstreetmap ⊕ OpenURL ⊕ ordnance-survey ⊕ ORE ⊕ orphanworks ⊕ owl:sameAs ⊕ Oxford ⊕ paget ⊕ parodies ⊕ particular ⊕ patterns ⊕ people ⊕ periodicals ⊕ permalinks ⊕ pharma ⊕ phonebooks ⊕ php ⊕ picassa ⊕ platform ⊕ poeple ⊕ presentations ⊕ preservation ⊕ principles ⊕ printing ⊕ privacy ⊕ provenance ⊕ publishing ⊕ PubSubHubbub ⊕ quality ⊕ queries ⊕ questions ⊕ radio ⊕ RAMEAU ⊕ RDA ⊕ RDAa ⊕ RDB2RDF ⊕ RDBS ⊕ rdf ⊕ rdfa ⊕ RDTF ⊕ recipes ⊕ recommendations ⊕ recommended ⊕ reconciliation ⊕ Redding ⊕ redirection ⊕ Reese ⊕ relationships ⊕ Remix ⊕ repositories ⊕ reread ⊕ research ⊕ researchers ⊕ resources ⊕ rest ⊕ result-centric ⊕ reuse ⊕ road-bumps ⊕ Rob ⊕ Roy ⊕ Sam ⊕ scalability ⊕ schema.org ⊕ scholarly-communication ⊕ scholarly-publishing ⊕ science ⊕ scienetific-communication ⊕ Scientific-American ⊕ scientific-communication ⊕ scoping ⊕ SDMX-RDF ⊕ search ⊕ second-screen ⊕ self-service ⊕ semantic ⊕ semantic-content-enrichment ⊕ semantic-libraries ⊕ semantic-publishing ⊕ semantic-search ⊕ semantic-web ⊕ semanticlibraries ⊕ semanticpublishing ⊕ semanticweb ⊕ semtech ⊕ semtech2011 ⊕ semweb ⊕ seo ⊕ serendipity ⊕ shadow-economies ⊕ shaman ⊕ SIMILE ⊕ simulation-sciences ⊕ sioc ⊕ skos ⊕ slide-proceedings ⊕ slides ⊕ slideshare ⊕ smart-grid ⊕ smithsonian ⊕ SNAC ⊕ solr ⊕ sparql ⊕ spending ⊕ SQUIN ⊕ sru ⊕ standards ⊕ startups ⊕ statistics ⊕ stlr ⊕ storytelling ⊕ streams ⊕ structured ⊕ Stuart ⊕ Styles ⊕ subjectheadings ⊕ Summers ⊕ Sweden ⊕ SWIB10 ⊕ Swirrl ⊕ talis ⊕ technology ⊕ ted ⊕ TED09 ⊕ TEI ⊕ Tennant ⊕ Tennison ⊕ Terry ⊕ text-analytics ⊕ the-universal-vs.-the-particular ⊕ thesauri ⊕ Thomas-Reuters ⊕ threshhold-effect ⊕ Tim ⊕ timbl ⊕ tolook ⊕ tools ⊕ toread ⊕ toreread ⊕ tpdl ⊕ tpdl2011 ⊕ transparency ⊕ Trinity ⊕ tutorials ⊕ tv ⊕ twine ⊕ twitter ⊕ typed-links ⊕ u.s. ⊕ UDC ⊕ Udell ⊕ ui ⊕ UK ⊕ universal ⊕ URI ⊕ URI-aliases ⊕ uriburner ⊕ URIs ⊕ URL ⊕ validation ⊕ validators ⊕ version-control ⊕ via:@edsu ⊕ via:@mhausenblas ⊕ via:@pablomendes ⊕ viaf ⊕ video ⊕ videos ⊕ visualization ⊕ vocabularies ⊕ void ⊕ Voss ⊕ VU ⊕ w3c ⊕ walled-gardens ⊕ web ⊕ webdev ⊕ webscience ⊕ webservices ⊕ Weibel ⊕ wikipedia ⊕ wikis ⊕ wolfram ⊕ workshops ⊕ worldbank ⊕ Worldcat ⊕ worldcup ⊕ WWW ⊕ www08 ⊕ XML ⊕ XMPP ⊕ youtube ⊕ Zepheira ⊕ Zigtag_Imported_Bookmarks ⊕Copy this bookmark: