Copyright and Licensing
Articles accepted for publication will be licensed under the Creative Commons BY-NC-SA. Authors must sign a non-exclusive distribution agreement after article acceptance.
Identifier Management and Resolution: Conforming the IEEE Standard for Learning Object Metadata
Keywords:
Learning objects, Knowledge repositories, Identifiers, Content-Negotiation, Education informaticsAbstract
Uniform Resource Identifiers are an integral part of the current Architecture of the World Wide Web. This work analyzes the implications and possibilities of using Universal Resource Names as unique and persistent identifiers in systems for management of decentralized content and federated collections. Particularly, discussion focuses on applying such identifiers on the context of a learning object repository that the authors are developing at Universidad Nacional del Litoral, according to the IEEE 1484.12.1 standard for Learning Object Metadata. It is explained why Uniform Resource Locators are inadequate, and why Universal Resource Names are preferable. A standardized resolution service over Hypertext Transfer Protocol is recommended for locating resources, and usage of Uniform Resource Characteristics for accessing Learning Object Metadata is proposed. Finally, a content-negotiation mechanism for selecting the best representation among several format or language variants is outlined. The proposed naming schema provides a doubleindirection mechanism, comparable to the Human- Friendly Names approach proposed by Ballintijn, van Steen, and Tanenbaum for improving scalability and usability in naming replicated resources.
Downloads
Download data is not yet available.
References
[1] D. Booth, “URIs and the myth of resource identity,” Identity, Reference, and the Web, WWW2006 Workshop, 2006.
[2] A. Powell, P. Johnston, L. Campbell, and P. Barker, “Guidelines for using resource identifiers in Dublin Core metadata and IEEE LOM,” Dublin Core Metadata Initiative, DCMI Recommended Resource, Apr. 2005, http://www.ukoln.ac.uk/metadata/dcmi-ieee/identifiers/ (last access 2007-05).
[3] N. H. Shadbolt and T. W. Berners-Lee, “The semantic web revisited,” Intelligent Systems, IEEE, vol. 21, no. 3, pp. 96 – 101, Feb. 2006.
[4] I. Jacobs, N. Walsh et al., “Architecture of the world wide web, volume one,” World Wide Web Consortium, W3C Recommendation REC-webarch-20041215, Dec. 2004.
[5] D. Tessman, “A uniform resource name (URN) namespace for federated content,” Internet Engineering Task Force, RFC 4198, Nov. 2005.
[6] R. J. Godoy, H. Minni, G. Zarza, and H. Loyarte, “Design criteria for the development of an institutional learning object repository,” in Proceedings of XII Argentine Congress on Computer Science, San Luis, 2006.
[7] Learning Technology Standards Committee, “IEEE standard for learning object metadata,” Institute of Electrical and Electronics Engineers, New York, IEEE Standard 1484.12.1, 2002.
[8] R. Moats, “URN syntax,” Internet Engineering Task Force, RFC 2141, May 1997.
[9] T. Berners-Lee, R. Fielding, and L. Masinter, “Uniform resource identifier (URI): generic syntax,” Internet Engineering Task Force, RFC 3986, Jan. 2005.
[10] Internet Assigned Numbers Authority, “Official IANA registry of URN namespaces,” http://www. iana.org/assignments/urn-namespaces, June 2008.
[11] “Uniform resource identifier (URI) schemes,” http://www.iana.org/assignments/uri-schemes.html, June 2008.
[12] R. Moats, “A URN namespace for IETF documents,” Internet Engineering Task Force, RFC 2648, Aug. 1999.
[13] J. Goodwin and H. Apel, “A uniform resource name (URN) namespace for the international organization for standardization (ISO),” Internet Engineering Task Force, RFC 5141, Mar. 2008.
[14] M. Mealling, “A URN namespace of object identifiers,” Internet Engineering Task Force, RFC 3061, Feb. 2001.
[15] N. Walsh, J. Cowan, and P. Grosso, “A URN namespace for public identifiers,” Internet Engineering Task Force, RFC 3151, Aug. 2001.
[16] International Organization for Standardization, “Information processing — text and office systems —standard generalized markup language (SGML),” International Organization for Standardization, Geneva, Switzerland, ISO Standard ISO 8879:1986(E), Oct. 1986.
[17] P. J. Leach, M. Mealling, and R. Salz, “A universally unique identifier (UUID) URN namespace,” Internet Engineering Task Force, RFC 4122, Jul. 2005.
[18] R. J. Godoy and H. Minni, “Asignación y resolución de identificadores para un repositorio de objetos de aprendizaje basado en LOM,” in IX Workshop de Investigadores en Ciencias de la Computación, Trelew, 2007, pp. pp658–662.
[19] K. Sollins, “Architectural principles of uniform resource name resolution,” Internet Engineering Task Force, RFC 2276, Jan. 1998.
[20] M. Mealling and R. Daniel, “URI resolution services necessary for URN resolution,” Internet Engineering Task Force, RFC 2483, Jan. 1999.
[21] R. Daniel, “A trivial convention for using HTTP in URN resolution,” Internet Engineering Task Force, RFC 2169, Jun. 1997.
[22] N. Freed and N. Borenstein, “Multipurpose internet mail extensions (MIME) part two: Media types,” Internet Engineering Task Force, RFC 2046, Nov. 1996.
[23] M. Murata, S. Laurent, and D. Kohn, “XML media types,” Internet Engineering Task Force, RFC 3023, Jan. 2001.
[24] R. Fielding, J. Gettys, J. Mogul, H. Frystyk, L. Masinter, P. Leach, and T. Berners-Lee, “Hypertext transfer protocol – HTTP/1.1,” Internet Engineering Task Force, RFC 2616, Jun. 1999.
[25] R. J. Godoy and H. Minni, “Identifier management and resolution: conforming the ieee standard for learning object metadata,” in XIII Congreso Argentino de Ciencias de la Computación, Corrientes, 2007, pp967–975.
[26] E. Duval, R. J. Godoy et al., “LOM v1.0 corrigenda,” Learning Technology Standards Committee, Draft Minutes, 2007–2008, http://ariadne.cs.kuleuven.be/mediawiki/index.php/LOM_v1.0_Corrigenda (last access: 2008-06).
[27] Learning Technology Standards Committee, “Draft standard for learning object metadata — Corrigendum 1: Corrigenda for 1484.12.1 LOM (learning object metadata),” P1484.12.1-2002/Cor 1/D2, May 2008.
[28] F. Dawson and T. Howes, “vCard MIME directory profile,” Internet Engineering Task Force, RFC 2426, Sep. 1998.
[29] T. Howes, M. Smith, and F. Dawson, “A MIME Content-Type for directory information,” Internet Engineering Task Force, RFC 2425, Sep. 1998.
[30] G. Ballintijn, M. van Steen, and A. Tanenbaum, “Scalable human-friendly resource names,” Internet Computing, IEEE, vol. 5, no. 5, pp. 20–27, Oct. 2001.
[31] C. Duncan, “Use cases for persistent identifiers,” in DCC Workshop on Persistent Identifiers, Glasgow, Jul. 2005.
[32] A. Powell, “Identifiers - requirements and issues,” in DCC Workshop on Persistent Identifiers, Glasgow, Jul. 2005.
[33] S. Bradner, “The internet standards process – revision3,” Internet Engineering Task Force, RFC 2026, Oct.1996.
[2] A. Powell, P. Johnston, L. Campbell, and P. Barker, “Guidelines for using resource identifiers in Dublin Core metadata and IEEE LOM,” Dublin Core Metadata Initiative, DCMI Recommended Resource, Apr. 2005, http://www.ukoln.ac.uk/metadata/dcmi-ieee/identifiers/ (last access 2007-05).
[3] N. H. Shadbolt and T. W. Berners-Lee, “The semantic web revisited,” Intelligent Systems, IEEE, vol. 21, no. 3, pp. 96 – 101, Feb. 2006.
[4] I. Jacobs, N. Walsh et al., “Architecture of the world wide web, volume one,” World Wide Web Consortium, W3C Recommendation REC-webarch-20041215, Dec. 2004.
[5] D. Tessman, “A uniform resource name (URN) namespace for federated content,” Internet Engineering Task Force, RFC 4198, Nov. 2005.
[6] R. J. Godoy, H. Minni, G. Zarza, and H. Loyarte, “Design criteria for the development of an institutional learning object repository,” in Proceedings of XII Argentine Congress on Computer Science, San Luis, 2006.
[7] Learning Technology Standards Committee, “IEEE standard for learning object metadata,” Institute of Electrical and Electronics Engineers, New York, IEEE Standard 1484.12.1, 2002.
[8] R. Moats, “URN syntax,” Internet Engineering Task Force, RFC 2141, May 1997.
[9] T. Berners-Lee, R. Fielding, and L. Masinter, “Uniform resource identifier (URI): generic syntax,” Internet Engineering Task Force, RFC 3986, Jan. 2005.
[10] Internet Assigned Numbers Authority, “Official IANA registry of URN namespaces,” http://www. iana.org/assignments/urn-namespaces, June 2008.
[11] “Uniform resource identifier (URI) schemes,” http://www.iana.org/assignments/uri-schemes.html, June 2008.
[12] R. Moats, “A URN namespace for IETF documents,” Internet Engineering Task Force, RFC 2648, Aug. 1999.
[13] J. Goodwin and H. Apel, “A uniform resource name (URN) namespace for the international organization for standardization (ISO),” Internet Engineering Task Force, RFC 5141, Mar. 2008.
[14] M. Mealling, “A URN namespace of object identifiers,” Internet Engineering Task Force, RFC 3061, Feb. 2001.
[15] N. Walsh, J. Cowan, and P. Grosso, “A URN namespace for public identifiers,” Internet Engineering Task Force, RFC 3151, Aug. 2001.
[16] International Organization for Standardization, “Information processing — text and office systems —standard generalized markup language (SGML),” International Organization for Standardization, Geneva, Switzerland, ISO Standard ISO 8879:1986(E), Oct. 1986.
[17] P. J. Leach, M. Mealling, and R. Salz, “A universally unique identifier (UUID) URN namespace,” Internet Engineering Task Force, RFC 4122, Jul. 2005.
[18] R. J. Godoy and H. Minni, “Asignación y resolución de identificadores para un repositorio de objetos de aprendizaje basado en LOM,” in IX Workshop de Investigadores en Ciencias de la Computación, Trelew, 2007, pp. pp658–662.
[19] K. Sollins, “Architectural principles of uniform resource name resolution,” Internet Engineering Task Force, RFC 2276, Jan. 1998.
[20] M. Mealling and R. Daniel, “URI resolution services necessary for URN resolution,” Internet Engineering Task Force, RFC 2483, Jan. 1999.
[21] R. Daniel, “A trivial convention for using HTTP in URN resolution,” Internet Engineering Task Force, RFC 2169, Jun. 1997.
[22] N. Freed and N. Borenstein, “Multipurpose internet mail extensions (MIME) part two: Media types,” Internet Engineering Task Force, RFC 2046, Nov. 1996.
[23] M. Murata, S. Laurent, and D. Kohn, “XML media types,” Internet Engineering Task Force, RFC 3023, Jan. 2001.
[24] R. Fielding, J. Gettys, J. Mogul, H. Frystyk, L. Masinter, P. Leach, and T. Berners-Lee, “Hypertext transfer protocol – HTTP/1.1,” Internet Engineering Task Force, RFC 2616, Jun. 1999.
[25] R. J. Godoy and H. Minni, “Identifier management and resolution: conforming the ieee standard for learning object metadata,” in XIII Congreso Argentino de Ciencias de la Computación, Corrientes, 2007, pp967–975.
[26] E. Duval, R. J. Godoy et al., “LOM v1.0 corrigenda,” Learning Technology Standards Committee, Draft Minutes, 2007–2008, http://ariadne.cs.kuleuven.be/mediawiki/index.php/LOM_v1.0_Corrigenda (last access: 2008-06).
[27] Learning Technology Standards Committee, “Draft standard for learning object metadata — Corrigendum 1: Corrigenda for 1484.12.1 LOM (learning object metadata),” P1484.12.1-2002/Cor 1/D2, May 2008.
[28] F. Dawson and T. Howes, “vCard MIME directory profile,” Internet Engineering Task Force, RFC 2426, Sep. 1998.
[29] T. Howes, M. Smith, and F. Dawson, “A MIME Content-Type for directory information,” Internet Engineering Task Force, RFC 2425, Sep. 1998.
[30] G. Ballintijn, M. van Steen, and A. Tanenbaum, “Scalable human-friendly resource names,” Internet Computing, IEEE, vol. 5, no. 5, pp. 20–27, Oct. 2001.
[31] C. Duncan, “Use cases for persistent identifiers,” in DCC Workshop on Persistent Identifiers, Glasgow, Jul. 2005.
[32] A. Powell, “Identifiers - requirements and issues,” in DCC Workshop on Persistent Identifiers, Glasgow, Jul. 2005.
[33] S. Bradner, “The internet standards process – revision3,” Internet Engineering Task Force, RFC 2026, Oct.1996.
Downloads
Published
2008-07-01
Issue
Section
Original Articles
License
How to Cite
[1]
“Identifier Management and Resolution: Conforming the IEEE Standard for Learning Object Metadata”, JCS&T, vol. 8, no. 02, pp. p. 85–90, Jul. 2008, Accessed: Apr. 14, 2026. [Online]. Available: https://journal.info.unlp.edu.ar/JCST/article/view/746
