SIOC Post profile for "AI3:::Adaptive Information"
type: Document
description: A SIOC profile describes the structure and contents of a weblog in a machine readable form. For more information please refer to http://sioc-project.org/.
primary topic: Erecting Road Signs on the Structured Web
generator agent: http://rdfs.org/sioc/wp-sioc.php

Erecting Road Signs on the Structured Web
type: Post
has container: weblog
has creator: Mike Bergman
maker: Mike Bergman
created: 2007-08-09T00:53:05Z
content: Structured Dataand UMBEL Will Benefit from a Standard Registration Format One implication of the structured Web is that, with the rapid proliferation of the data, how do you find what is relevant? That purpose is what stimulated the initiation of the UMBEL (Upper Mapping and Binding Exchange Layer) project. The original specification for UMBEL recognized the need for a reference set of subject "proxies" to help describe what each data set "was about" as well as the need for a variety of binding mechanisms depending on scope and data structure of the source dataset. At its most general level, the intent of UMBEL is to provide four components in its 'core' ontology [1]: A set of reference subject "proxies" and properties and relations around them A means of binding the ontologies, classes or subsets of data within each contributing dataset to the 'core' UMBEL ontology and those subject proxies Characterizing a given dataset via metadata, and Describing access methods and endpoints for getting at that data. The first component on subject proxies is largely left to another discussion. The topic of this posting is mostly related to the latter three components of dataset binding and registration mechanisms. How such road signs might work, the contributions of possible analogs, their differences in providing solutions in and of themselves, and a first-cut outline of the resulting 'core' UMBEL ontology are described below. The Why and How of These Road Signs 'Road signs' are simply a shorthand for how to find stuff. The normative case is to have sufficient characterization of datasets such that a central registry can aid their discovery, look-up and productive access and use. Yet registration can be an onerous task, and one not generally easily or willingly undertaken by publishers or providers. These challenges lead to two important design considerations. First, only minimal characterization should be required for initially registering a dataset. The remaining characterist…
encoded: Structured Dataand UMBEL Will Benefit from a Standard Registration Format One implication of the structured Web is that, with the rapid proliferation of the data, how do you find what is relevant? That purpose is what stimulated the initiation of the UMBEL (Upper Mapping and Binding Exchange Layer) project. The original specification for UMBEL recognized the need for a reference set of subject “proxies” to help describe what each data set “was about” as well as the need for a variety of binding mechanisms depending on scope and data structure of the source dataset. At its most general level, the intent of UMBEL is to provide four components in its ‘core’ ontology [1]: A set of reference subject “proxies” and properties and relations around them A means of binding the ontologies, classes or subsets of data within each contributing dataset to the ‘core’ UMBEL ontology and those subject proxies Characterizing a given dataset via metadata, and Describing access methods and endpoints for getting at that data. The first component on subject proxies is largely left to another discussion. The topic of this posting is mostly related to the latter three components of dataset binding and registration mechanisms. How such road signs might work, the contributions of possible analogs, their differences in providing solutions in and of themselves, and a first-cut outline of the resulting ‘core’ UMBEL ontology are described below. The Why and How of These Road Signs ‘Road signs’ are simply a shorthand for how to find stuff. The normative case is to have sufficient characterization of datasets such that a central registry can aid their discovery, look-up and productive access and use. Yet registration can be an onerous task, and one not generally easily or willingly undertaken by publishers or providers. These challenges lead to two important design considerations. First, only minimal characterization should be required for initially registering a dataset. The remaining characterist…
topic: Adaptive Information
topic: Semantic Web
topic: Structured Web
topic: UMBEL
links to: diam.html
links to: UMBEL
links to: original specification
links to: 1
links to: archives
links to: collections
links to: Web services
links to: WSDL
links to: Dublin Core Collection Application Profile
links to: Dublin Core
links to: DCMI Abstract Model
links to: easily read summary
links to: 2
links to: W3C
links to: OAI-PMH
links to: specifications
links to: 3
links to: NISO-MS
links to: NISO Collection Description Specification
links to: 4
links to: IESR
links to: namespaces, classes and properties
links to: controlled vocabularies
links to: DLSR
links to: NSDL
links to: 5
links to: NDIIPP
links to: Library of Congress
links to: XML
links to: Web Services Description Language (WSDL) Version 2.0: RDF Mapping
links to: 6
links to: 7
links to: OASIS
links to: 8
links to: 9
links to: 10
links to: N3
links to: discussion forum
links to: specific outline page
links to: Levels of Conceptual Interoperability Model
links to: 11
links to: Structured Web
links to: OCLC
links to: The OAI registry at University of Illinois at Urbana-Champaign
links to: The Open Archives list of registered OAI repositories
links to: The Celestial OAI registry
links to: Eprint's Institutional Archives Registry
links to: Openarchives.eu The European Guide to OAI-PMH compliant repositories in the world
links to: ScientificCommons.org A worldwide service and registry
links to: 10morgan.html
links to: MyLibrary
links to: wsdl20-rdf
links to: ms531387.aspx
links to: xml-schema-patterns.html
links to: wsn-ws topics-1.3-spec-os.htm
links to: wsn-ws base notification-1.3-spec-os.htm
links to: REWERSE-RP-2006-034.pdf
links to: i4-d9a.pdf
links to: Journal for Defense Modeling & Simulation

Mike Bergman
type: User

Mike Bergman
type: Person

NISO Collection Description Specification
label: NISO Z39.91-200x, Collection Description Specification