FRINK Linked Data Fragments server

Matches in SemOpenAlex for { <https://semopenalex.org/work/W102732630> ?p ?o ?g. }

• W102732630 startingPage "1" @default.
• W102732630 abstract "Library resources typically do not show up in standard Internet searches, where the majority of users begin their research. Library metadata has traditionally existed within in 'silos', unsearchable on the World Wide Web, so users must visit the online library catalog to search for resources available at a particular library. This has impacted the perceived value of libraries themselves, as users rely less on libraries and more on outside resources to find information.Many believe that the answer to this problem lies in the Semantic Web and Linked Data (LD) movement. Converting library metadata to LD format would make it visible and searchable on the World Wide Web. Traditionally, the web has linked documents to one another, but with the Semantic Web, data itself is linked. Library metadata has been contained within databases and documents that are not searchable outside of library interfaces.The Resource Description Framework (RDF) metadata standard is closely tied with the Semantic Web and LD movement. RDF creates meaningful statements about both the data and the links between data. The main components of an RDF statement are expressed in 'triples': subject - predicate - object. This simple example includes three RDF triples: a :Website dc:title 'rdf:about' dc:description 'A website about Resource Description Framework' (Tauberer, n.d.)This is a construct similar to a sentence, in whichthe subject (thing or resource being talked about) and the predicate (the property or relation being described) are identified by URIs. The object (the value of the predicate) may be either another resource or a literal value (a string or a typed value such as a number or date). (Reynolds et al., 2005, p. 4)A URI is a Uniform Resource Identifier, and it is an essential part of RDF. In an RDF statement, having a URI means that multiple triples may be about the same resource. This can create a complex representation of relationships between pieces of data. In RDF, these relationships are represented as 'graphs' (Reynolds et al., 2005). As more and more links are formed between data, the structure of the graph can become even more complicated. With RDF, anything can be connected to anything else, anywhere, as long as common URIs are used.The Library of Congress (LC) is one organization taking the lead in adopting LD, having converted its authority records to LD format. The original LC authority site is still active, so it is possible to view both the new LC LD records and the original LC authority records.Research ProblemOne of the problems with LD is that it requires URIs to work well. The more resources that point to a particular URI, the more interconnected pieces of data can become. The Library of Congress has begun to address this problem by converting its authority records to LD format, thereby creating millions of standardized URIs. This effort is still in the experimental stages, so it would be interesting and informative to find out what the differences are between the original LC authority records and the new LC LD authority records. By comparing the original authority records to the new linked authority records, it may be possible to better visualize both the ways in which libraries will use this data and the changes that are coming as libraries move towards LD.Research QuestionHow does data on the original Library of Congress Authorities (LCA) site (http://authorities.loc.gov/) compare to data on the Library of Congress Linked Data Service (LCLDS) authorities site (http://id.loc.gov/)?Literature reviewRDF is a very new metadata standard, and the literature about RDF and LD reflects this. Many articles give background information by describing RDF and the Semantic Web. Several authors explain why RDF and LD should be adopted by libraries, justifying the need for change, differences between MARC and RDF, and specifically addressing the affect RDF would have on the practice of crosswalking. …" @default.
• W102732630 created "2016-06-24" @default.
• W102732630 creator A5034434951 @default.
• W102732630 date "2013-12-01" @default.
• W102732630 modified "2023-09-26" @default.
• W102732630 title "Linked Data and the Library of Congress" @default.
• W102732630 cites W1771985324 @default.
• W102732630 cites W2006468167 @default.
• W102732630 cites W2033209334 @default.
• W102732630 cites W2042177478 @default.
• W102732630 cites W2063397927 @default.
• W102732630 cites W2081504460 @default.
• W102732630 cites W2112218296 @default.
• W102732630 cites W2530131213 @default.
• W102732630 cites W642189582 @default.
• W102732630 hasPublicationYear "2013" @default.
• W102732630 type Work @default.
• W102732630 sameAs 102732630 @default.
• W102732630 citedByCount "1" @default.
• W102732630 countsByYear W1027326302016 @default.
• W102732630 crossrefType "journal-article" @default.
• W102732630 hasAuthorship W102732630A5034434951 @default.
• W102732630 hasConcept C136764020 @default.
• W102732630 hasConcept C140146324 @default.
• W102732630 hasConcept C147497476 @default.
• W102732630 hasConcept C199360897 @default.
• W102732630 hasConcept C2129575 @default.
• W102732630 hasConcept C21959979 @default.
• W102732630 hasConcept C23123220 @default.
• W102732630 hasConcept C41008148 @default.
• W102732630 hasConcept C69075417 @default.
• W102732630 hasConcept C93518851 @default.
• W102732630 hasConceptScore W102732630C136764020 @default.
• W102732630 hasConceptScore W102732630C140146324 @default.
• W102732630 hasConceptScore W102732630C147497476 @default.
• W102732630 hasConceptScore W102732630C199360897 @default.
• W102732630 hasConceptScore W102732630C2129575 @default.
• W102732630 hasConceptScore W102732630C21959979 @default.
• W102732630 hasConceptScore W102732630C23123220 @default.
• W102732630 hasConceptScore W102732630C41008148 @default.
• W102732630 hasConceptScore W102732630C69075417 @default.
• W102732630 hasConceptScore W102732630C93518851 @default.
• W102732630 hasLocation W1027326301 @default.
• W102732630 hasOpenAccess W102732630 @default.
• W102732630 hasPrimaryLocation W1027326301 @default.
• W102732630 hasRelatedWork W1595922228 @default.
• W102732630 hasRelatedWork W2116715020 @default.
• W102732630 hasRelatedWork W2253295712 @default.
• W102732630 hasRelatedWork W2254639862 @default.
• W102732630 hasRelatedWork W2321285851 @default.
• W102732630 hasRelatedWork W2325085362 @default.
• W102732630 hasRelatedWork W2341503649 @default.
• W102732630 hasRelatedWork W2362290660 @default.
• W102732630 hasRelatedWork W2395052005 @default.
• W102732630 hasRelatedWork W2883990695 @default.
• W102732630 hasRelatedWork W2901511641 @default.
• W102732630 hasRelatedWork W2992170752 @default.
• W102732630 hasRelatedWork W3209479415 @default.
• W102732630 hasRelatedWork W922504128 @default.
• W102732630 hasRelatedWork W964526896 @default.
• W102732630 hasRelatedWork W216459984 @default.
• W102732630 hasRelatedWork W2182132301 @default.
• W102732630 hasRelatedWork W2185427912 @default.
• W102732630 hasRelatedWork W2749312021 @default.
• W102732630 hasRelatedWork W2904635803 @default.
• W102732630 isParatext "false" @default.
• W102732630 isRetracted "false" @default.
• W102732630 magId "102732630" @default.
• W102732630 workType "article" @default.