[Sigia-l] scheme v. schema

[Frank Shepard]

Historically speaking, "schema" has been used to refer to drafts,
hypotheses, diagrams, etc. And in philosophy, it refers to an a priori
form or rule. So it might be a stretch to use it to refer to an
end-product or deliverable. At least if you are concerned with being
consistent with its general usage. I can't speak for its deployment in
IA in particular.

Frank

On 8/8/07, Ruth Kaufman <ruth.kaufman at gmail.com> wrote:
> Greetings,
>
> I need to craft a statement that explains the difference between the
> notion of a scheme and a schema -- as in classification scheme v.
> schema (not XML schema, per se).
>
> The context: I'm preparing a workshop for content strategists about
> classification and taxonomy work and deliverables. This statement will
> be included in the training materials, and I will also do my best to
> use the nomenclature consistently in my ongoing communications.
>
> My thinking is that 'scheme' is a more general, "plain English" term
> for things and ideas that resemble an information classification
> concept, model or plan. Whereas a 'schema' is an artifact or
> deliverable -- a scheme that is documented and implementable.
>
> Does this sound right? Other considerations?
>
> Thanks in advance!
>
> Ruth
> ------------
> IA Summit 2008: "Experiencing Information"
> April 10-14, 2008, Miami, Florida
>
> -----
> When replying, please *trim your post* as much as possible.
> *Plain text, please; NO Attachments
>
> Searchable Archive at http://www.info-arch.org/lists/sigia-l/
> ________________________________________
> Sigia-l mailing list -- post to: Sigia-l at asis.org
> Changes to subscription: http://mail.asis.org/mailman/listinfo/sigia-l
>