What a library's role is now and in the future.
Posted on Jan 10 2010 14:48  Comments 0 / Librarians Trackbacks 0

The quote below come from a Chronicle interview with the Duke University "Director of Digital Information Strategy". There is nothing new here but it shows the the emphasis has to be on helps students and faculty use, manage and create digital resources.

I think that's a big future role for libraries. Libraries typically have been about providing access to things that have been published somewhere else. It's kind of an access point and a collection point. And I think one of the big new roles for libraries in the future is going to be helping our local communities to publish and make accessible materials that they're creating locally here in ways that can be consumed by people out there in the world."
Information Architecture, DITA, Topic Maps
Posted on Jan 13 2010 20:50  Comments 0 / Information Management Trackbacks 0

What is Information Architecture?

The science of expressing a model or concept for information. Used for activities that require expressions of complex systems

Consists of

  • Structural design of shared information environments
  • Organizing and labeling information to support usability and findability

From Wikipedia

What is DITA

Topic-based authoring is a modular content creation approach (popular in the technical publications and documentation arenas) that supports XML content reuse, content management, and makes the dynamic assembly of personalized information possible. DITA has the facility for customization within the standard using inheritance: specialization(thus Darwin)

A topic is a discrete piece of content that is about a specific subject, has an identifiable purpose, and can stand alone (does not need to be presented in context for the end-user to make sense of the content). Topics are also reusable. They can, when constructed properly (without reliance on other content for its meaning), be reused in any context anywhere needed.

DITA is about Information Typing

DITA specifies three basic topic types: Task, Concept and Reference. Each of the three basic topic types is a specialization of a generic Topic type, which contains a title element, a prolog element for metadata, and a body element. The body element contains paragraph, table, and list elements, similar to HTML.

  • A Task topic is intended for a procedure that describes how to accomplish a task. A Task topic lists a series of steps that users follow to produce an intended outcome. The steps are contained in a taskbody element, which is a specialization of the generic body element. The steps element is a specialization of an ordered list element.
  • Concept information is more objective, containing definitions, rules, and guidelines.
  • A Reference topic is for topics that describe command syntax, programming instructions, and other reference material, and usually contains detailed, factual material.

DITA and Topic Maps

DITA: * Topic-oriented * Content model * Develop and reuse content * Combine topics using Maps * Separates taxonomy and relationships from content * Robust tools for authoring and publishing

Topic Maps: * Subject-centric * Semantic model * Capture and reuse semantics * Relate subjects using Maps * Separates subject definition from the content resources * Robust tools for ontology design, search and navigation

Posted on Jan 21 2010 21:36  Comments 0 / Atom Pub Trackbacks 0

I don't know enough about these but the below came from Rob Sanderson

  • Simply send the Resource Map as the payload for SWORD in the same way that you would send anything else and let the server do what it wishes.
  • Send a Resource Map as a 'manifest' or object description in a zip with the resources.
  • Allow SW-ORE-D to manipulate the hierarchies within the repository via ORE nested aggregations. Eg, to create a new Collection you would post a resource map for it. The server would then create a new deposit target for that collection against which you could post more collections recursively.
  • Allow SW-ORE-D to manipulate the aggregations and aggregated resources themselves by depositing resources against Entries (possibly via the Proxy URI or something derivable from it).
A Simple FRBR Example
Posted on Jan 22 2010 14:01  Comments 0 / FRBR Metadata Trackbacks 0

This is good because it shows that the expression can be simple! It comes from Ronald Murray's (who's from the Library of Congress) excellent but challenging presentation.

What is means to be hierarchical
Posted on Jan 22 2010 14:59  Comments 0 / Data Modeling FRBR Trackbacks 0

This graphic came from a discussion about FRBR but I just thought it was interesting.

Repository Services from Florida
Posted on Jan 27 2010 18:25  Comments 0 / Repositories Trackbacks 0