complexType "AbstractMaintainableType"
Namespace: |
|
Content: |
|
Abstract: |
(cannot be assigned directly to elements used in instance XML documents) |
Defined: |
|
Includes: |
|
Used: |
|
XML Representation Summary |
<... |
|
|
|
= |
("Add" | "Update" | "Delete") |
|
|
= |
(xs:string | xs:string) |
|
|
= |
("Agency" | "Maintainable") : "Agency" |
|
|
= |
xs:boolean |
|
|
= |
(xs:dateTime | xs:date | xs:gYearMonth | xs:gYear | xs:duration) |
|
|
= |
xs:boolean : "false" |
|
|
= |
xs:anyURI |
|
|
= |
xs:language |
|
|
> |
|
Content: |
( URN | ( Agency, ID, Version))[1..2], UserID*, UserAttributePair*, ( VersionResponsibility | VersionResponsibilityReference)?, VersionRationale?, BasedOnObject?, RelatedOtherMaterialReference*, Note*, Software*, MetadataQuality* |
|
</...> |
Known Direct Subtypes (1):
-
Known Indirect Subtypes (43):
-
ArchiveType,
BaseLogicalProductType,
CategorySchemeType,
ClassificationFamilyType,
CodeListSchemeType,
CodeListType,
ComparisonType,
ConceptSchemeType,
ConceptualComponentType,
ConceptualVariableSchemeType,
ControlConstructSchemeType,
DDIInstanceType,
DDIProfileType,
DataCollectionType,
DevelopmentActivitySchemeType,
GeographicLocationSchemeType,
GeographicStructureSchemeType,
GroupType,
InstrumentSchemeType,
InterviewerInstructionSchemeType,
LocalHoldingPackageType,
LogicalProductType,
ManagedRepresentationSchemeType,
MeasurementSchemeType,
NCubeSchemeType,
OrganizationSchemeType,
OtherMaterialSchemeType,
PhysicalDataProductType,
PhysicalInstanceGroupType,
PhysicalInstanceType,
PhysicalStructureSchemeType,
ProcessingEventSchemeType,
ProcessingInstructionSchemeType,
QualitySchemeType,
QuestionSchemeType,
RecordLayoutSchemeType,
RepresentedVariableSchemeType,
ResourcePackageType,
SamplingInformationSchemeType,
StudyUnitType,
UnitTypeSchemeType,
UniverseSchemeType,
VariableSchemeType
All Direct / Indirect Based Elements (46):
-
Archive,
BaseLogicalProduct,
CategoryScheme,
ClassificationFamily,
CodeList,
CodeListScheme,
Comparison,
ConceptScheme,
ConceptualComponent,
ConceptualVariableScheme,
ControlConstructScheme,
DDIInstance,
DDIProfile,
DataCollection,
DevelopmentActivityScheme,
GeographicLocationScheme,
GeographicStructureScheme,
Group,
InstrumentScheme,
InterviewerInstructionScheme,
LocalGroupContent,
LocalHoldingPackage,
LocalResourcePackageContent,
LocalStudyUnitContent,
LogicalProduct,
ManagedRepresentationScheme,
MeasurementScheme,
NCubeScheme,
OrganizationScheme,
OtherMaterialScheme,
PhysicalDataProduct,
PhysicalInstance,
PhysicalInstanceGroup,
PhysicalStructureScheme,
ProcessingEventScheme,
ProcessingInstructionScheme,
QualityScheme,
QuestionScheme,
RecordLayoutScheme,
RepresentedVariableScheme,
ResourcePackage,
SamplingInformationScheme,
StudyUnit,
UnitTypeScheme,
UniverseScheme,
VariableScheme
Annotation
Used to identify described maintainable objects for purposes of internal and/or external referencing. Elements of this type may be maintained as independent objects (outside of a parent object). Provides containers for Uniform Resource Name (URN) as well as ID information. An entity can either be identified either by a URN and/or an identification sequence. At a minimum, one or the other is required. You must designate they type of URN supported by your agency, either "Canonical" or "Deprecated". To fully support interoperability both the DDI URN and the full identification sequence should be used. Note that to support interoperability of the canonical and deprecated URN, at minimum the MaintainableIdentifier and TypeOfMaintainableObject should be supplied if the canonical URN is being used by the agency. If both URN and the identification sequence is used, and there is any conflict, the URN takes precedence. The element can be designated as an addition, replacement, or deletion to facilitate tracking changes. In addtion to the elements and attributes inherited from AbstractIdentifiable, additional information regarding the versioning process can be provided; version date, the person and/or organization within the maintenance agency responsible for the change as either text or reference, and the reason for the change. If the object created was based on an exisiting object (other than by versioning), the object on which it is based can be identified using BasedOnReference. In addition to UserID, versionable and maintainable objects may also designate additional user specific properties expressed as a key/value pair using UserAttributePair. Maintainable objects may also contain any notes related to the objects they contain, identification of the software used to create and/or manage the metadata, a statement of the metadata quality, and a default URI value to use for external external references. The attribute xml:lang can be used to provide specification of the default language of the metadata contents. When the isPublished attribute is set to "true" it indicates to the user that they may safely reference the contents as they will continue to be accessible and any changes in the non-administrative content will be tracked by a versioning mechanism.
|
Type Derivation Tree
 AbstractMaintainableType
|
XML Source (w/o annotations (6); see within schema source)
<xs:complexContent>
<xs:extension base="AbstractVersionableType">
<xs:sequence>
<xs:element maxOccurs="unbounded" minOccurs="0" ref="Note"/>
<xs:element maxOccurs="unbounded" minOccurs="0" ref="Software"/>
</xs:sequence>
<xs:attribute ref="xml:lang" use="optional"/>
</xs:extension>
</xs:complexContent>
</xs:complexType>
|
Attribute Detail (all declarations; defined within this component only; 2/8)
externalReferenceDefaultURI-
Type: |
xs:anyURI, predefined |
Use: |
optional |
Use to provide a default value for the URI of external references. Use of a URI in a reference within this maintainable overrides the value entered here. Nested maintainables should redeclare the contents of this attribute for clarity.
XML Source (w/o annotations (1); see within schema source)
-
Type: |
xs:language, predefined
|
Use: |
optional |
This is used to designate the language of the metadata content of the maintainable. If a lower level xml:lang attribute conflicts with the content at the maintainable level, the object level value takes precedence.
XML Source (w/o annotations (1); see within schema source)
<xs:attribute ref="xml:lang" use="optional"/>
|
Content Element Detail (all declarations; defined within this component only; 3/14)
-
An assessment of the quality of the metadata within the Maintainable object, e.g. the quality of the transcription, completeness, editing status, etc.
XML Source (w/o annotations (1); see within schema source)
-
Note allows for the attachment of a piece of additional information to any object with an ID. Note facilitates capturing temporary processing notes such as "Review and approval required". A single note can be attached to multiple objects by reference to the objects. Note may also contain content for a needed object that has been reported for addition in a later version of the schema. Ideally this should be handled by a local extension, but Note can accommodate run-time extensions when required. The Note should be housed within the Maintainable object that contains the referenced objects. In this way the user is ensured of receiving all known Note attachments when the maintainable content is delivered. This means that if a Note references objects within multiple Maintainable objects, the Note should be repeated in each Maintainable and reference only those objects with that Maintainable.
XML Source (w/o annotations (1); see within schema source)
<xs:element maxOccurs="unbounded" minOccurs="0" ref="Note"/>
|
-
Indicate the software used to create and/or manage the metadata. This is repeatable to allow for multiple softwares or multiple functions. If this information is important it is advisable to provide it in each maintainable so that it does not become separated from the internal content if the metadata is re-factored.
XML Source (w/o annotations (1); see within schema source)
<xs:element maxOccurs="unbounded" minOccurs="0" ref="Software"/>
|
