China
Africa
Explore chapters and articles related to this topic
Metadata Schemes, Structures, and Encoding
Published in Mike Cox, Linda Tadic, Ellen Mulder, Descriptive Metadata for Television An End-to-End Introduction, 2006
Mike Cox, Linda Tadic, Ellen Mulder
The Dublin Core metadata element set was developed beginning in 1995 by a group of librarians and digital information specialists in the United States, and it has been approved as a U.S. National Standard (ANSI/NISO Z39.85). It is essentially a list of simplified metadata fields that can be applied across many formats; it is not locked into a particular media type. There are no fundamental restrictions to the types of resources to which Dublin Core metadata can be assigned; they can be used to describe digital assets, images, books, films, and broadcast materials.
Survey of E-Learning Standards
Published in Ibrahiem M. M. El Emary, Anna Brzozowska, Shaping the Future of ICT, 2017
Manal Abdullah, Nashwa AbdelAziz Ali
The Dublin Core Metadata Initiative (DCMI) is adopting an interoperability metadata standard, especially a metadata vocabulary. Dublin Core defines metadata that is developed by, for example, title, creator, subject, description, and publisher. This standard represents XML and RDF languages. There are some available documents issued by Dublin Core, including Dublin Core Template, MyMetaMaker, Reggie-The Metadata Editor, and DC-dot (Blagojević et al. 2015).
The Shifting Paradigm of the Emerging Technology of Information and Communication Technology: Cheminformatics, to the Benefit of Science
Published in Alexander V. Vakhrushev, Omari V. Mukbaniani, Heru Susanto, Chemical Technology and Informatics in Chemistry with Applications, 2019
The Dublin Core specifically focuses on definitions of specifications, vocabularies, and best practice for the assertion of metadata on the web. Dublin Core is an initiative to create a digital “library card catalog” for the web and the elements that offer extended categorized information and improved document indexing.
Multi-scale hydrological system-of-systems realized through WHOS: the brokering framework
Published in International Journal of Digital Earth, 2022
Enrico Boldrini, Stefano Nativi, Silvano Pecora, Igor Chernov, Paolo Mazzetti
The implemented discovery interfaces include: OAI-PMH (The OAI Executive 2002): The Open Archives Initiative Protocol for Metadata Harvesting (OAI-PMH) interface provides metadata harvesting functionalities. WHOS OAI-PMH support metadata encoding in Dublin Core, ISO 19115, ISO 19115-2 and WIGOS metadata models.OGC CSW (OGC 2007): The Open Geospatial Consortium (OGC) Catalogue Service for the Web (CSW) interface provides metadata search functionalities. WHOS OGC CSW support metadata encoding in Dublin Core, ISO 19115, ISO 19115-2 and ISO 19115 community profiles.OpenSearch (DeWitt 2018): Amazon A9 OpenSearch interface provides custom metadata search functionality. The actual available interface is described within the search engine description document, including parameterized URL templates that indicate how the search clients should make search requests. WHOS OpenSearch supports the GeoRSS/Atom metadata model and JSON.CUAHSI HIS Central (Whitenack, Zaslavsky, and Valentine 2008): The Consortium of Universities for the Advancement of Hydrologic Science, Inc. (CUAHSI) HIS Central interface provides service and time series discovery functionalities.
Identifying organisational learning needs: an approach to the semi-automatic creation of course structures for software companies
Published in Behaviour & Information Technology, 2020
André Menolli, Huander Tirone, Sheila Reinehr, Andreia Malucelli
There are several metadata specifications for LOs in the literature. Usually, metadata are defined by standards associations like IEEE (1484.12.1 Standard for Learning Object Metadata) and ISO (SC 36 WG 2 – Information Technology for Learning, Education, and Training), which have created working groups to develop proposals for object structuring and categorisation (metadata), aiming to support the proper recovery and reuse of LO cataloging. Thus, this metadata represents a way to organise data from LOs so as to allow communication between different computing environments, as well as accessibility and usability, and ensure interoperability. Some examples of specification standards are: LOM describes important LOs features with the purpose of facilitating the search and use of LOs for instantiation by learners and instructors or automated software processes (IEEE 2002).Sharable Content Object Reference Model (SCORM) focuses on the interoperability and reusability of LOs. SCORM introduced the complex idea of sequencing, which is a set of rules that specifies the order in which a learner should follow content objects (ADL 2004).Dublin Core Metadata Initiative (DCMI) was developed by NISO (National Information Standards Organisation) and contains fifteen elements to describe learning resources (NISO 2007).
Towards knowledge-based geovisualisation using Semantic Web technologies: a knowledge representation approach coupling ontologies and rules
Published in International Journal of Digital Earth, 2020
Unlike previous studies concerning the modelling of cartographic scales (cf. Carral et al. 2013; Huang et al. 2018), we model cartographic scales at the geometry set level. Specifically, geometric representations with the same level of detail usually have the same visualisation scales. According to this principle, we develop a cartographic scale vocabulary, where we introduce the concept GeometrySet, and encapsulate geometries with the same level of detail in a named graph of the type GeometrySet. In the meantime, a class CartographicScale is created, and each instance of this class can be linked to the visualisation scale through two datatype properties, hasMaxScaleDenominator and hasMinScaleDenominator; the object property hasScale is created to associate an instance of GeometrySet (a named graph) with instance(s) of CartographicScale. The cartographic scale information may be different when this knowledge is modelled by different providers and used for different applications. Hence, the metadata, e.g. the application field, is modelled by hasApplicationField (an object property whose range is skos:Concept), as well as SKOS11 and Dublin Core12 vocabularies. Figure 1 illustrates these key concepts and their relations when employing INSPIRE draft building vocabularies for representing geospatial data.