Well, now I'm confused. Many of the web sites I've seen have a homepage
and below that, a level of what might be thought of as introductory
feature pages -- is there a name for that kind of page? For example, I
work for a music museum, and our site consists of a homepage which
allows the user to click on names of sections in the site. One section
(or room or feature -- what can we call it?) is entitled "Northwest
Passages," and it's a sort of Northwest band genealogy, with
descriptions (test, discographies, photos, sound clips) of bands and
band members and how they link to one another. Then we have our "Vault"
section which features a multimedia description of a different artifact
or group of artifacts from our collections every day. There's a section
on the staff, the museum newsletter, the museum's mission and press
releases, and so forth; another section on guitars, and a section on
Jimi Hendrix. And more, but what is each of these "rooms" called? Each
contains essay-like writings, biographical writing; there's a catalog, a
schedule, but these writings contain music clips and digital images, and
one feature consists mostly of video clips and discographical
information. Most are multimedia pages. Do these qualify as DLOs?
What are the Resource Type terms we'd use to describe, say, the
introductory page for each section, and then the section itself? And
aren't a lot of sites structured similarly to ours? The URL is
http://www.experience.org
Marsha Maguire
Collections Librarian
Experience Music Project
110 - 110th Avenue, NE, Suite 550
Bellevue, WA 98004
USA
[log in to unmask]
(425) 450-1997
> -----Original Message-----
> From: Jon Knight [SMTP:[log in to unmask]]
> Sent: Thursday, July 24, 1997 5:16 AM
> To: Dan Brickley
> Cc: [log in to unmask]
> Subject: Re: Resource Types
>
> On Thu, 24 Jul 1997, Dan Brickley wrote:
> > What about CVs though? For my sins I'm involved with a project
> > that will include a database of both CVs and job adverts for Social
> > Science researchers. On the face of it these are both classic DLOs,
> but
> > the former is also straying into white-pages territory.
>
> Ah but the difference is that you're generating metadata for a CV
> object which _is_ a DLO, rather than metadata about a human object
> which
> isn't a DLO (it doesn't have an author, subject, etc, though I guess
> if
> you were being perverse you could say that parents are authors of
> children - I wouldn't recommend it though!). Similarly you can easily
> fit
> DC metadata to biographies of people, but its not a good fit for the
> people themselves.
>
> > This is a specific case of a general problem: for more or less any
> > non-DLO (people, jobs, houses, museum artifacts, databases,
> whatever...)
> > it is often useful to have a DLO describing that resource. (eg. CVs,
>
> > job description, catalogue records, photographs of artifacts). And
> once
> > we've got a class of DLOs for talking about that kind of non-DLO,
> there's
> > a need to represent them in Dublin Core. Which is maybe why people
> > sometimes seem to be using DC for everything...
>
> I agree that there's a need to represent the metadata of the DLOs in
> Dublin Core; that's what DC is all about after all. However I
> disagree
> with using DC to represent metadata for non-DLOs, even if those
> non-DLOs
> have DLOs that talk about them. A GIS or a genome database, etc
> doesn't
> sound much like a DLO to me and so shouldn't have DC for it. However
> a
> manual page describing how to use the database should be covered by DC
> and
> indeed is; it would have a resource type along the lines of
> DOCUMENT.manual (modified to suit whatever syntax we eventually end up
> with).
>
> Tatty bye,
>
> Jim'll
>
> -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
> -=-=-
> Jon "Jim'll" Knight, Researcher, Sysop and General Dogsbody, Dept.
> Computer
> Studies, Loughborough University of Technology, Leics., ENGLAND. LE11
> 3TU.
> * I've found I now dream in Perl. More worryingly, I enjoy those
> dreams. *
>
|