> I agree that the Abstract Model should be at the center of
> explanations, and I like most of the text. I also think we
> need to revisit the explanation for "simple" versus "qualified"
> Dublin Core.
>
> Two issues however:
>
> 1) To start with statements, property-value pairs, and URIs is
> to jump in at the deep end. The notion of "core metadata
> properties" has been and should continue to be a key part
> of the message. Introducing "the Dublin Core" up-front also
> helps explain the funny name.
>
> > The Dublin Core Metadata Initiative (DCMI), the body
> that facilitates
> > the community development of the DC metadata standard,
> provides a core
> > set of about 80 properties,
>
> I suspect that the notion of "core metadata properties" really
> is easier for most people to grasp than the notion of an
> abstract model. I would not want DCMI to lose that focus --
> 80 properties is no longer really a "core".
OK, could drop the specific ('80') and leave the general ('core set of
...')?
But main problem is with emphasis and order. It's difficult to say what
DCMI provides (essentially 'a core set of terms that can be used to
create descriptions of resources') without describing the nature of what
those terms are and how they fit together.
Perhaps in my suggested text,
The Dublin Core Metadata Initiative (DCMI), the body that facilitates
the community development of the DC metadata standard, provides a core
set of about 80 properties, encoding schemes and controlled vocabularies
from which descriptions can be constructed, but encourages communities
to create additional terms as necessary, within the framework provided
by the DCAM.
needs to be moved up front and changed to
The Dublin Core Metadata Initiative (DCMI), the body that facilitates
the community development of the Dublin Core metadata standard, provides
a flexible and extensible metadata framework and a core set of terms
from which descriptions can be constructed, but encourages communities
to create additional terms as necessary to meet their own descriptive
requirements.
Then go on to describe the framework (the DCAM) in more detail...
Does that help?
> 2) "DC" and "DCMI"
>
> > The features of the DC metadata standard are fully described
> > in the Dublin Core Abstract Model (DCAM).
>
> This is not quite how I understand our current use of
> "DC" and "DCMI".
Sorry. I was writing in a hurry so I didn't follow corporate
guidelines! :-)
Andy
--
Head of Development, Eduserv Foundation
http://www.eduserv.org.uk/foundation/
[log in to unmask]
+44 (0)1225 474319
|