Sachs, JoelFinin, Tim2018-11-152018-11-152010-03-22Joel Sachs and Tim Finin,What Does it Mean for a URI to Resolve? , Proceedings of the AAAI Spring Symposium on Linked Data Meets Artificial Intelligence, 2010, https://www.google.com/url?q=https://www.aaai.org/ocs/index.php/SSS/SSS10/paper/download/1178/1458&sa=U&ved=0ahUKEwjLgZDb8r_eAhXCjVkKHWQ3AlwQFggEMAA&client=internal-uds-cse&cx=016314354884912110518:gwmynp16xuu&usg=AOvVaw1sdWNqXk8dWF0AMX_NxeKJhttp://hdl.handle.net/11603/12001Proceedings of the AAAI Spring Symposium on Linked Data Meets Artificial IntelligenceAmongst the best practices that constitute Linked Data, one of the foremost is to use only HTTP-URIs as identifiers for RDF resources. This is so that the URI will resolve in a Linked Data browser to give information about the named resource. At the same time, Linked Data takes a resource-centric, as opposed to page-centric, approach to resolution. We argue that this approach can, in certain cases, obviate the need for insisting on HTTP-URIs. As a use of our “expanded” notion of Linked Data, we present as an example Life Science Identifiers.3 pagesen-USThis item is likely protected under Title 17 of the U.S. Copyright Law. Unless on a Creative Commons license, for uses protected by Copyright Law, contact the copyright holder or the author.eco-informaticslinked datasemantic webUMBC Ebiquity Research GroupText