Internationalized Resource Identifier (IRI)

An Internationalized Resource Identifier (IRI) is a standard proposed by the IETF (RFC 3987).  An IRI is a unique sequence of characters that identifies a resource.  

IRIs are a generalization of URIs (RFC3986) that permits a wider range of Unicode characters.

A Uniform Resource Identifier (URI) is a unique sequence of characters that identifies an abstract or physical resource.  The difference between an IRI and a URI is that IRIs use the more modern Universal Character Set (a.k.a. UNICODE) and URIs use the older ASCII character set. The newer IRI format is compatible with the older URI format. The most current version of RDF uses IRIs to identify resources.

Don't confuse IRIs with URLs and URNs.  A URL is a web address. A URN is a Uniform Resource Name. This Venn diagram shows the relationship between these different tools:

Why are IRIs and URIs important?  If you are thinking in terms of a single database, a silo of data, then IRIs and URIs might not make much sense.  But, if you are a systems thinker then why you need IRIs/URIs becomes very clear.
  • Standards-based approach to identifying resources: Lots of different vendors coming up with lots of different approaches to uniquely identify a resource then requires middleware to reconcile the different approaches.
  • Globally unique:  IRIs are globally unique. Database resource identifiers are local only.  Database identifiers only mean what you think they mean in the context of a specific database.  Outside that database the identifiers are meaningless and can conflict with some other identifier.  GUIDs (Guaranteed Unique Identifiers,  like this 748afe65-97a9-46ac-b218-d8fe0be2b2be) can work, but uniqueness is not really guaranteed and they can be opaque and it can be harder to figure out what the GUID actually means.
  • Resolvable: Because IRIs are based on domain names which are unique and registered with a DNS (Domain Name Server), you can know where to go to resolve them (find out what they mean).  It is up to the creator of the IRI to use best practices when they publish information; but if they do users of the information can understand what the information means.  For example, here is the IRI from DBpedia for Microsoft, Google, Apple (the fruit), SalesForce, Amazon (what do you mean?), and Cadbury.
There is tremendous value in something like the notion of the semantic web.  IRIs and URIs make things just a little bit easier.  Here is a counter example of a standard resource identifier (what NOT to do).

Additional Information:

Comments

Post a Comment

Popular posts from this blog

Relational Knowledge Graph System (RKGS)

Image
Relational Knowledge Graph System (RKGS) is an interesting idea that combines the relational paradigm and the knowledge graph paradigm.  This documentation, Why RKGS , explains the idea. This gets even more interesting with the notion of "relational AI".  RelationalAI is described as follows by the company of the same name, Relational.ai : “RelationalAI is a cloud-based relational knowledge graph management system, with state of the art probabilistic processing and declarative reasoning at scale to make developing Data Applications a superpower for your business.” This notion of knowledge graphs represented in relational databases fits into my belief that knowledge graphs have two aspects: the expression SYNTAX and the logic of what is expressed or SEMANTICS. While the LOGIC of a knowledge graph is always the same regardless of technical syntax used to express that logic; there are many, many different technical syntaxes that can be used to represent a knowledge graph. There
Read more

Getting Started with Auditchain Luca

Image
(Note that a newer, production version as opposed to only the development version , of Luca Suite is available) The Innovator's Dilemma points out that disruptive innovations often look like toys that are doing everything wrong. Auditchain Luca , which is part of the Auditchain Suite , is a unique approach to creating a knowledge graph .  To experience using Auditchain Luca, have a look at the Getting Started with Auditchain Luca instructions. Be sure to grab the Excel and JSON import files used for this getting started exercise.   This getting started exercise uses one of several different approaches to getting information into a tool for constructing and viewing professional quality knowledge graphs .  Additional getting started guides will be made available over time. Auditchain Luca might not make sense to you if you don't understand the paradigm shift that is occurring and if you have not shifted your mental map. For the next step in your journey, consider trying creat
Read more

Evaluating the Quality of XBRL-based Financial Reports

Image
From the time public companies started submitting XBRL-based financial reports to the U.S. Securities and Exchange Commission, I have been looking at those reports, trying to understand the XBRL-based reports, and trying to figure out how to get them right.  That information was used to figure out how to create software applications that help professional accountants get these reports right. Here is information that summarizes my testing and results which I stopped doing March 31, 2019: Analysis of the high level accounting relationships in the 10-Ks of about 5,716 financial reports  (5,063 public companies, about 89.1% got all these high level accounting relationships consistent with expectation, 623 were inconsistent and manual confirmation revealed the inconsistency was an error) Documentation that helps you understand 26 different types of errors in XBRL-based reports High quality documentation of hundreds of errors in XBRL-based reports submitted by public companies to the SEC Doc
Read more