*** SCHEMA EXPLANATION **** This is the MAIN schema for the Objects metadata framework. This MAIN schema calls other VOCABULARY schemas to create the metadata framework structure. *** NAMESPACES ******** The chameleon approach to namespace conventions is used in the VOCABULARY schemas. Only this MAIN schema has a target namespace. The VOCABULARY schemas do not have target namespaces (allows for plug-n-play components and vocabularies). *** ROOT ELEMENT ***** The root element of this schema is news-oppsRecord. *** SCHEMA DEVELOPMENT ***** The Venetian Blind approach is used for this MAIN schema and all VOCABULARY schemas. Elements within all schemas are used for fields (quantities) of the metadata framework. When elements have controlled vocabularies that are hierarchal, the vocabularies appear in the element as a colon separated text string. Attributes are used when additional information is required for the content of an element or if two pieces of information are required. *** DEFINING COMPLEX and SIMPLE TYPES ******* Since the metadata framework uses Venetian Blind schema development, most metadata fields are defined as complex or simple types. This improves re-use for other frameworks developed at the DLESE Program Center (DPC) or within the DLESE community. As such, each schema has a complex and simple type section. Built-in simple types are defined when an elment is defined. Derived simple types are used when a metadata field appears more than once or if restrictions are needed on element content. *** LICENSE INFORMATION ***** Copyright 2002, 2003 DLESE Program Center University Corporation for Atmospheric Research (UCAR) P.O. Box 3000, Boulder, CO 80307, United States of America email: support@dlese.org. These schemas are free software; you can redistribute them and/or modify them under the terms of the GNU General Public License as published by the Free Software Foundation; either version 2 of the License, or (at your option) any later version. These schemas are distributed in the hope that they will be useful, but WITHOUT ANY WARRANTY; without even the implied warranty of MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU General Public License for more details. You should have received a copy of the GNU General Public License along with this project; if not, write to the Free Software Foundation, Inc., 59 Temple Place, Suite 330, Boston, MA 02111-1307 USA ***** CATEGORY schemas to include ************************* ***** VOCABULARY schemas to include ************************* ***** ROOT element ************************* faq-glossaryType is complex ***** Other Elements ************************* ***** Complex Types (alpha order) ************************* ***** contributorType ************************* organization is complex - the information about an institution person is complex - the information about a person role is simple; see role.xsd; the function performed by the contributor display is boolean - indication if contributor information can be displayed date is simple - the date of the contributor's contribution ***** contributorsType ************************* contributor is complex - either an organization or person who has provided information about or cataloged the object ***** dateType ************************* type is simple; see typeOfDate.xsd - a description for the kind of date ***** datesType ************************* date is complex - a date associated with some aspect of the object or metadata record ***** objectsType ************************* recordID is complex - the catalog record number libraryAreas is complex - the broad area of DLESE to which the cataloged object belongs topics is complex - the more specific area of DLESE to which the cataloged object belongs description is complex - a narrative using HTML that is about the cataloged object moreInfoEmail is simple - the email address to contact for more information about the cataloged object relations is complex - the associations to another object through a catalog record number ONLY dates is complex - a date associated with some aspect of the object or metadata record contributors is complex - either organizations or persons who provide information about or catalog the object ***** libraryAreasType ************************* libraryArea is simple; see libraryArea.xsd - the broad area of DLESE to which the cataloged object belongs ***** organizationType ************************* instName is built-in - an organization's name instDept is simple - an organization's department name instPosition is simple - an aribitrary job positions in the organization (e.g. librarian) instUrl is simple - the organization web address instEmail is simple - the organization's email address contactID is simple - not used - an internal DPC tracking number to the contributor ***** personType ************************* nameTitle is simple; see nameTitle.xsd; the salutation of a person contributor nameFirst is built-in - the first name of a person contributor nameMiddle is built-in - the middle name of a person contributor nameLast is built-in - the last name of a person contributor instName is built-in - an organization's name instDept is simple - an organization's department name emailPrimary is simple - the main email address for a person contributor emailAlt is simple - the alternate email address for a person contributor contactID is simple - not used - an internal DPC tracking number to the contributor ***** recordIDType ************************* type is simple; see typeOfRecord.xsd; the kind of metadata record (object) to be cataloged ***** relationsType ************************* relation is simple - the association to another object through a catalog record number ONLY ***** topicsType ************************* topics is simple; see topic.xsd - the more specific area of DLESE to which the cataloged object belongs ***** XHTMLType ************************* uses the W3C namespace in order to allow HTML tags to be child elments on the objects and description elements ***** Simple Types (alpha order) ************************* ***** stringTextType ************************* Use this patterned string to ensure that a null tag is not valid string content. Note: that xsd:string allows content to be null even if the element is required. ***** union.dateType ************************* Allows for a multitude of date formats to use for the date element. Uses all built-in types. ***** union.topicType ************************* Allows for the element topic to be free text but also has a vocabulary to help generat content For topicType see topic.xsd