ASTM E2468-2005(2012) Standard Practice for Metadata to Support Archived Data Management Systems《支持存档数据管理系统的元数据标准实施规程》.pdf

《ASTM E2468-2005(2012) Standard Practice for Metadata to Support Archived Data Management Systems《支持存档数据管理系统的元数据标准实施规程》.pdf》由会员分享，可在线阅读，更多相关《ASTM E2468-2005(2012) Standard Practice for Metadata to Support Archived Data Management Systems《支持存档数据管理系统的元数据标准实施规程》.pdf（64页珍藏版）》请在麦多课文档分享上搜索。

1、Designation: E2468 05 (Reapproved 2012)Standard Practice forMetadata to Support Archived Data Management Systems1This standard is issued under the fixed designation E2468; the number immediately following the designation indicates the year oforiginal adoption or, in the case of revision, the year of

2、 last revision. A number in parentheses indicates the year of last reapproval. Asuperscript epsilon () indicates an editorial change since the last revision or reapproval.1. Scope1.1 This standard practice describes a hierarchical outline ofsections and elements to be used in developing metadata tos

3、upport archived data management systems. Specifically, thestandard establishes the names of metadata elements andcompound elements to be used in the metadata, the definitionsof these metadata elements and compound elements, andsuggested information about and examples of the values thatare to be prov

4、ided for the metadata elements.1.2 The metadata to be developed using this standardincludes qualitative and quantitative data that is associated withan information system or information object for the purposes ofdescription, administration, legal requirements, technicalfunctionality, use and usage,

5、and preservation. As such, it canbe differentiated from other metadata in that it describes andprovides an interpretation of an organized collection of data,not a single data element.1.3 This standard is intended for use by those developing,managing, or maintaining an archived data management sys-te

6、m. For example, public agencies can specify that thisstandard be used in the development of a metadata frameworkfor data archives. Data collectors and data processing interme-diaries may also use this standard to create metadata describingthe original collection conditions and intermediate processin

7、gsteps. The development of metadata by data collectors and dataprocessing intermediaries can greatly assist in the developmentof comprehensive metadata by the data archive manager. Thestandard is intended for use by all levels of government and theprivate sector.1.4 This standard is applicable to va

8、rious types of opera-tional data collected by intelligent transportation systems (ITS)and stored in an archived data management system. Similarly,the standard can also be used with other types of historicaltraffic and transportation data collected and stored in anarchived data management system.1.5

9、This standard does not specify the means by whichmetadata is to be organized in a computer system or in a datatransfer, nor the means by which metadata is to be transmitted,communicated, or presented to the user. Additionally, thestandard is not intended to reflect or imply a specific imple-mentatio

10、n design. An implementation design requires adaptingthe structure and form of the standard to meet specificapplication and environment requirements.1.6 This standard adopts with minimal changes the FederalGeographic Data Committees (FGDCs) existing ContentStandard for Digital Geospatial Metadata (FG

11、DC-STD-001-1998) as the recommended metadata framework for archiveddata management systems. The FGDC metadata standard waschosen as the framework because of its relevance and estab-lished reputation among the spatial data community. A benefitof using the FGDC standard is the widespread availability

12、ofinformational resources and software tools to create, validate,and manage metadata (see http:/www.fgdc.gov/metadata/links/metalinks.html). Commentary and several examples areprovided in this standard to illustrate the use of the FGDCstandard in the ITS domain. The detail of the standard mayappear

13、intimidating, but the examples in the Appendix illus-trate the relative simplicity of the standard when implemented.1.7 Users of this standard should note that several sectionsof the metadata standard (that is, Annex A3 and Annex A4)address spatial referencing documentation, which may not beapplicab

14、le to all data archives. These spatial referencingsections are designated as mandatory-if-applicable, whichmeans that metadata is not required for these sections if spatialreferencing is not used. Annex A6, Distribution Information, isalso designated as mandatory-if-applicable and thus may not bereq

15、uired.2. Referenced Documents2.1 ASTM Standards:2E867 Terminology Relating to Vehicle-Pavement SystemsE2259 Guide forArchiving and Retrieving Intelligent Trans-portation Systems-Generated Data1This practice is under the jurisdiction of ASTM Committee E17 on Vehicle -Pavement Systems and is the direc

16、t responsibility of Subcommittee E17.52 onTraffic Monitoring.Current edition approved July 1, 2012. Published July 2012Last previous versionapproved 2005 as D246805. DOI: 10.1520/E2468-05R12.2For referenced ASTM standards, visit the ASTM website, www.astm.org, orcontact ASTM Customer Service at serv

17、iceastm.org. For Annual Book of ASTMStandards volume information, refer to the standards Document Summary page onthe ASTM website.Copyright ASTM International, 100 Barr Harbor Drive, PO Box C700, West Conshohocken, PA 19428-2959. United States12.2 American National Standards Institute (ANSI) Stan-da

18、rds:ANSI INCITS 30-1997 (R2003) Representation of CalendarDate and Ordinal Date for Information Interchange (for-merly ANSI X3.30-1985, also formerly FIPS 4-1)3ANSI X3.43-1986 Representations of Local Time of Day forInformation Interchange3ANSI X3.51-1975 Representations of Universal Time, LocalTime

19、 Differentials, and United States Time Zone Refer-ences for Information Interchange3ANSI INCITS 61-1986 (R2002) Representation of Geo-graphic Point Locations for Information Interchange (for-merly ANSI X3.61-1986 (R1997), also formerly FIPS70-1)32.3 Federal Geographic Data Committee (FGDC) Stan-dard

20、:FGDC-STD-001-1998 Content Standard for Digital Geospa-tial Metadata, Version 2.02.4 Federal Information Processing Standards (FIPS):FIPS PUB 4-1 (1988) Representation for Calendar Date andOrdinal Date for Information InterchangeFIPS PUB 55-3 (1994) Codes for Named Populated Places,Primary County Di

21、visions, and Other Locational Entitiesof the United States, Puerto Rico, and the Outlying AreasFIPS PUB 70-1 (1986) Representation of Geographic PointLocations for Information InterchangeFIPS PUB 173-1 (1994) Spatial Data Transfer Standard(STDS)2.5 Department of Defense:MIL-STD-600006 (1992) Vector

22、Product Format (VPF)MIL-A-89007 (1989) ARC Digitized Raster Graphics(ADRG)2.6 International Organization for Standardization (ISO):ISO 19115 (2003) Geographic InformationMetadata3. Terminology3.1 Definitions:3.1.1 archived data management subsystem, na subsystemof the National ITS Architecture that

23、provides a means forseveral organizations to collect, store, and subsequently, ana-lyze and retrieve data from ITS data sources, usually by way ofone or more ITS centers.3.1.2 archived data management system, nthis is a spe-cific implementation of an archived data management subsys-tem within the co

24、ntext of a local, regional, or statewide ITSarchitecture.3.1.3 attribute, na defined property or characteristic; sub-set of an entity. In common terms, an attribute is typically acolumn in a relational database or a property in an object-oriented environment.3.1.4 before the common era, nsometimes a

25、bbreviatedBCE, the period preceding a year near the birth of Jesus,coinciding with the period from 1 BC and earlier. It issynonymous with the period called before the Christian era andis sometimes used as a religiously neutral alternative to it.3.1.5 catalog, na structured description of data beings

26、tored or transferred in data flows as described in the NationalITS Architecture.3.1.6 common era, nsometimes abbreviated CE, the pe-riod beginning with a year near the birth of Jesus, coincidingwith the period from AD 1 onwards. It is synonymous with theperiod called the Christian era and is sometim

27、es used as areligiously neutral alternative to it.3.1.7 compound element, na group or combination ofgroups of metadata elements. All compound elements aredescribed by metadata elements, either directly or throughintermediate compound elements. Compound elements repre-sent higher-level concepts that

28、cannot be represented byindividual metadata elements.3.1.8 data processing intermediary, na person or entitywho transforms and supplies data that they did not directlycollect themselves.3.1.9 data set, na logical collection of data that supports auser function; could include one or more data tables,

29、 files, orsources.3.1.10 entity, nan existing or real thing. In relation to adatabase, an entity is a single person, place, or thing aboutwhich data can be stored. In common terms, an entity can berepresented by one or more tables in a relational database or anobject in an object-oriented environmen

30、t.3.1.11 metadata, ndata about data, or more precisely,definitional and descriptive data that provides informationabout or documentation of other data managed within anapplication or environment.3.1.12 metadata element, na logically primitive item ofmetadata that forms the basic building block for t

31、his metadatastandard.3.1.13 National ITS Architecture, na document preparedthrough the sponsorship of the U.S. DOT that provides acommon structure for the design of intelligent transportationsystems giving a framework around which multiple designapproaches can be developed by defining: (a) the funct

32、ions thatmust be performed to implement a given user service; (b) thephysical entities or subsystems where these functions reside;(c) the interfaces/information flows between the physicalsubsystems; and (d) the communication requirements for theinformation flows.3.1.14 production rules, na standardi

33、zed method of illus-trating how metadata elements and compound elements arecombined into a defined hierarchical metadata structure. Pro-duction rules also illustrate the optionality and repeating natureof metadata elements and compound elements.3.2 Additional terms included in this standard but notd

34、efined here may be found in the glossary for the existingFGDC metadata standard at the following address: http:/geology.usgs.gov/tools/metadata/standard/glossary.html. Manyof the terms in the FGDC glossary are from FIPS 173 (SpatialData Transfer Standard, or SDTS).3Available from American National S

35、tandards Institute (ANSI), 25 W. 43rd St.,4th Floor, New York, NY 10036.E2468 05 (2012)24. Summary of Practice4.1 The seven basic sections included in this metadatacontent standard are shown in Fig. 1 and summarized asfollows:4.1.1 Identification Information, or basic information aboutthe data set.

36、For example, what is the name of the data set?Who developed the data set? What geographic area does itcover? What themes of information does it cover? How currentare the data? Are there restrictions on accessing or using thedata?4.1.2 Data Quality Information, or a general assessment ofthe quality o

37、f the data set. For example, how good are the data?Is information available that allows a user to decide if the dataare suitable for his or her purpose? What is the positional andattribute accuracy? Are the data complete? Were the consis-tency of the data verified? What data were used to create thed

38、ata set, and what processes were applied to these sources?4.1.3 Spatial Data Organization Information, or the mecha-nism used to represent spatial information in the data set. Forexample, what spatial data model was used to encode thespatial data? How many spatial objects are there? Are methodsother

39、 than coordinates, such as street addresses, used to encodelocations?4.1.4 Spatial Reference Information, or the description ofthe reference frame for, and the means to encode, coordinatesin the data set. For example, are coordinate locations encodedusing longitude and latitude? Is a map projection

40、or gridsystem, such as the State Plane Coordinate System, used? Whathorizontal and vertical datums are used? What parametersshould be used to convert the data to another coordinatesystem?4.1.5 Entity and Attribute Information, or details about theinformation content of the data set, including the en

41、tity types,their attributes, and the domains from which attribute valuesmay be assigned. For example, what geographic information(roads, houses, elevation, temperature, etc.) is included? Howis this information encoded? Were codes used? What do thecodes mean?4.1.6 Distribution Information, or inform

42、ation about thedistributor of and options for obtaining the data set. Forexample, from whom can I obtain the data? What formats areavailable? What media are available? Are the data availableonline? What is the price of the data (if any)?4.1.7 Metadata Reference Information, or information onthe curr

43、entness of the metadata information and the responsibleparty. For example, when were the metadata compiled? Bywhom?4.2 This standard practice adopts with minimal change anexisting FGDC metadata standard to document data stored inarchived data management systems. This standard addressesthe three type

44、s of metadata as defined in Guide E2259 andoutlined here:4.2.1 Archive Structure Metadata, or descriptive data aboutthe structure of the data archive itself and of the data andinformation in the archive that facilitate use of the archive(Source: Adapted from FGDC Metadata Workbook Version 2.0)FIG. 1

45、 FGDC Content Standard for Digital Geospatial MetadataE2468 05 (2012)3(Identification Information, Spatial Reference Information, En-tity and Attribute Information, and Distribution Information inthis standard).4.2.2 Processing Documentation Metadata, or informationthat describes the processes appli

46、ed to the data from originalsource data through to storage in an archived data managementsystem (Data Quality Information and Spatial Data Organiza-tion Information in this standard).4.2.3 Data Collection System Metadata, or data about theconditions and procedures under which original source datawer

47、e observed, surveyed, measured, gathered, collected, aswell as about the equipment that was used (Data QualityInformation, Entity and Attribute Information, and MetadataReference Information in this standard).4.3 This standard includes three additional sections that arereferenced by the other sectio

48、ns of the metadata standard.These last three sections are always used within other sectionsand are never used alone. The three sections are as follows:4.3.1 Citation Information, or the recommended referenceto be used for the data set.4.3.2 Time Period Information, or information about thedate and t

49、ime of an event.4.3.3 Contact Information, or the identity of, and means tocommunicate with, person(s) and organization(s) associatedwith the data set.4.4 Each of the seven basic sections of the metadata contentstandard has an optionality associated with it: mandatory,mandatory-if-applicable, and optional. Four of the seven sec-tions are mandatoryIdentification Information, Data QualityInformation, Entity and Attribute Information, and MetadataReference Informationand these four sections form what isconsidered the “core” for metadata that conform to thisstand