On Mon, 25 Oct 1999, Deb Richardson wrote:
> Hi Paul...here are my quick notes from an initial read-through:
>
> ---
> 9. Resource Type
> Label: TYPE
> Obligation: Optional
> Maximum Occurrence: Repeatable
> The category of the resource. To promote consistency, TYPE
> should be selected from the following list:
> HOWTO
> mini-HOWTO
> user's guide
> administrator's guide
> programmer's guide
> installation guide
> ---
>
> Is the list of document types extensible? I can think of a couple of
> others I would like to add for the OSWG, for example ("article",
> "research paper").
yes it is extensible and it would be simple and good to add the type you
mention
>
> I'm also a little confused about the fact that the type can be
> repeatable. Does this mean you can classify a single document in more
> than one type catagory? (I've possibly missed something :->)
yes something could conceivably be considered a research paper might
become a chapter or a mini-How-To might graduate to a How-To
> ---
> 14. Relation
> Label: RELATION
> Obligation: Optional
> Maximum Occurrence: Repeatable
> A URL that points to the IDENTIFIER element of another resource. Each
> instance of RELATION links the resource to other resources of similar
> domain or style.
> ---
>
> I'm not quite sure I understand the purpose of "relation". Could you
> expand on that a bit here?
as i understand it (kendall and miles feel free to jump in and set me
straight). relation is for say chapters and parts of collections or
say a conference paper etc.
>
> Finally, from the last section (15), I assume that the list of licenses
> allowed in the RIGHTS.type catagory is modifiable/extensible. (?) I
> doubt the list of open-source/open-content licenses is anywhere near
> static at this point :>
exactly
>
> I like the xmlifier. Once the information is xmlified, however, what's
> to be done with it? I'm not quite sure I understand what the "big
> picture" of the project is. Could you walk me though it a bit?
well, we know that a variety of XML databases will be thrashing it out
soon. we have an XML search engine that we will be trying soon, i hope,
from etymon and invisible worlds, but the collection of metadata, like the
LSMs, could and should be distributed so that others could also provide
solutions as they see fit. ours will likely look like linsearch in at
least one incarnation.
but you can't search without well-marked up, well-defined content so this
is an effort to create that content in as simple a way as possible while
still including enough information to be useful.
you may think of these entries of card catalogue records with links to the
data objects/documents that can be filed, selected and sorted by anyone.
> - deb
> (a big fan of anything that makes indexing/searching/catagorizing
> easier)
>
> --
> [EMAIL PROTECTED]
> [EMAIL PROTECTED]
> [EMAIL PROTECTED]
>
==========================================================================
Paul Jones
"We must protect our precious bodily fluids!" General Jack D Ripper
http://MetaLab.unc.edu/pjones/ at the Site Formerly Known As SunSITE.unc.edu
[EMAIL PROTECTED] voice: (919) 962-7600 fax: (919) 962-8071
===========================================================================
