Understanding Information Language

Web 2.0
HTTP hyper text transfer protocol--the communication standard for delivering info on the web
HTML hyper text markup language is how the information is displayed and provides the browser with information on how to display text but it does not say anything about the meaning of the text (Hastings, 2015) 
URL Uniform resource located and that's how we find a page on the web
API's application program interfaces let us pass information back and forth as we use web services like facebook

We have clicked on links since the beginning but data is locked up and we can't get access to it.

Web 3.0
URI Uniform resource identifier identifies individual "things" on the web or elsewhere (not web pages like the URL)

Four kinds of Metadata Standards (Schilling, 2012) defined by Zeng and Qin (2008)
  1. Structures like the Dublin Core Metadata element set (DCMES), established the standard for the international standard (ISO, 2009)
     
  2. Content like the Anglo American Cataloging rules (AACR2) or International Standard for Bibliographic Description (ISBD)
  3. Values like the library of Congress subject headings (LCSH)
  4. exchange like the MARC 21 format for bibliographic data (MARC 21)
     
  5. Others

  1. VRA Core
  2. Categories for the description of works of art (CDWA)
  3. Encoded archival description (EAD)
  4. Art and Architecture Thesaurus (AAT)
  5. Iconclass 
  6. Thesaurus of Graphic Materials (TGM)
  7. Thesaurus of Geographical Names (TGN)
  8. Resource Description and Access (RDA)
  9. Metadata encoding and transmission standards (METS) was created by NISO in 2004
Data Exchange Standards
  1. MARC 21--allow libraries to exchange metadata, inflexible output process
  2. Extensible Markup Language (XML) allows users to design their own markup langagues to meet their own needs, encourages across platform sharing. Can identify that two items are related but not the how

  1. RSS really simple syndication is an XML based format that allows republishing to ther sites or downloading by users
  1. Standard Generalized Markup Language (SGML), XML is a subset of this. SGML is hierarchical and flexible
Metadata has three categories
defined as structured information that describes, explains, locates or makes it easier to retrieve, use or manage information (Rubin)
  1. Descriptive- indentifies specifics, traditional library cataloging
  2. Administrative--information to help manage a resource such as when and how it was created

  1. technical (file characteristics)
  2. rights management metadata (intellectual property rights)
  3. preservation
  1. Structural--indicates how compound objects are related; indicates the relationships between physical files and pages, between pages and chapters and chapters and book
Semantic Web Standards (W3C, see https://www.w3.org/Consortium/)
  1. RDF Resource Description Framework--language for representing information about resources in the WWW. Represents Metadata about web resources (title, author, modification dates, copyright, licensing)

  1. underpins the whole semantic web
  2. includes "statements" and graphs
  3. SPARQL is the query language used across diverse data sources
  4. middleware allows other data to be viewed as RDF
  5. HTTP protocol--retrieval mechanism
  1. Vocabularies expressed in RDF

  1. RDF Schema or RDF Vocabulary definition language (RDFS) provides mechanisms for describing groups of related resources and the relationships between these resources
  2. Web Ontology Language (OWL) develops ontology evelopment and sharing via the Web with the goal of making web content more accessible to machines
  3. Other vocabularies include FOAF, SIOC, SKOS, DOAP, vCard, Dublin Core, OAI_ORE or GoodRelations
  1. Simple Knowledge Organization System (SKOS) provides a bridge between different communities of practice within the library and information sciences involved in the design and application of knowledge organization systems and between these communities and the semantic web. Helps to move systems to RDF
  2. Berners-Lee four principles of linked data (Bizer, 2010)

  1. Use URI's (Uniform Resource Identifiers) as names for things (from web pages, to objects in the real world to abstract concepts) to distinguish one thing from another (tells other computers where to look for data)

  1. URI's allow for the creation of hyperlinked based data discovery and browsing
  2. Library of Congress has started to give URI's to subject headings, names, genre terms, country codes, languages
  1. Use HTTP URIs so that people can look up those names (anyone with a domain name can create URI references)

  1. HTTP is a standardized access mechanism
  1. When someone looks up at URI, provide useful information, using the standards (RDF, SPARQL)
  2. Include links to other URI's so that they can discover more things
  1. Linked data triple (OCLC video)

  1. subject, relationship, objects
  2. example: www.bbc.co.uk/nature/; schema.org, google knowledge graph (display on right side of search page is linked data)
  3. dbpedia liked data wiki
  4. by using linked data the programs talk to each other using triples

  1. Heath and Bizer (2011) add that there are three types of links 

  1. relationship links
  2. identity links
  3. vocabulary links
  1. Currently Libraries cannot talk to the web search engines because the languages are different
  2. Search Engine Optimization (SE0) could provide a way for libraries to enhance their visibility through exposing their metadata as linked data
  3. Why important for libraries? (OCLC video)

  1. people can more easily find library resources on the web
  2. more creative applications based on library metadata
  3. opportunities for cataloging efficiency and innovation--looks at data like building blocks rather than whole building. Pieces can be removed or gathered piece by piece, they don't need to come in a full picture
  4. doesn't it also

  1. allow the computer to draw from more material
  2. provide a richer interface to show more connections
  3. allow users to contribute
  1. VIAF


(Taken from Bizer 2010) By employing HTTP URIs to identify resources, the HTTP protocol as retrieval mechanism, and the RDF data model to represent resource descriptions, Linked Data directly builds on the general architecture of the Web (Jacobs & Walsh, 2004). The Web of Data can therefore be seen as an additional layer that is tightly interwoven with the classic document Web and has many of the same properties: • The Web of Data is generic and can contain any type of data. • Anyone can publish data to the Web of Data. • Data publishers are not constrained in choice of vocabularies with which to represent data. • Entities are connected by RDF links, creating a global data graph that spans data sources and enables the discovery of new data sources. From an application development perspective the Web of Data has the following characteristics: • Data is strictly separated from formatting and presentational aspects. • Data is self-describing. If an application consuming Linked Data encounters data described with an unfamiliar vocabulary, the application can dereference the URIs that identify vocabulary terms in order to find their definition. • The use of HTTP as a standardized data access mechanism and RDF as a standardized data model simplifies data access compared to Web APIs, which rely on heterogeneous data models and access interfaces. • The Web of Data is open, meaning that applications do not have to be implemented against a fixed set of data sources, but can discover new data sources at run-time by following RDF links
  

Comments

Popular Posts