ACDD.csv

id,status,dct:description,dct:identifier,rdf:type,rdfs:label,rdfs:range,rdfs:seeAlso
Conventions,Highly Recommended,"A comma-separated list of the conventions that are followed by the dataset. For files that follow this version of ACDD, include the string 'ACDD-1.3'. (This attribute is described in the NetCDF Users Guide.)",Conventions,rdf:Property,Conventions,rdfs:Literal,<http://wiki.esipfed.org/index.php/Attribute_Convention_for_Data_Discovery_1-3#Conventions>
acknowledgement,Recommended,A place to acknowledge various types of support for the project that produced this data.,acknowledgement,rdf:Property,acknowledgement,rdfs:Literal,<http://wiki.esipfed.org/index.php/Attribute_Convention_for_Data_Discovery_1-3#acknowledgement>
cdm_data_type,Suggested,"The data type, as derived from Unidata\'s Common Data Model Scientific Data types and understood by THREDDS. (This is a THREDDS ""dataType"", and is different from the CF NetCDF attribute \'featureType\', which indicates a Discrete Sampling Geometry file in CF.)",cdm_data_type,rdf:Property,cdm_data_type,rdfs:Literal,<http://wiki.esipfed.org/index.php/Attribute_Convention_for_Data_Discovery_1-3#cdm_data_type>
comment,Recommended,"Miscellaneous information about the data, not captured elsewhere. This attribute is defined in the CF Conventions.",comment,rdf:Property,comment,rdfs:Literal,<http://wiki.esipfed.org/index.php/Attribute_Convention_for_Data_Discovery_1-3#comment>
contributor_name,Suggested,"The name of any individuals, projects, or institutions that contributed to the creation of this data. May be presented as free text, or in a structured format compatible with conversion to ncML (e.g., insensitive to changes in whitespace, including end-of-line characters).",contributor_name,rdf:Property,contributor_name,rdfs:Literal,<http://wiki.esipfed.org/index.php/Attribute_Convention_for_Data_Discovery_1-3#contributor_name>
contributor_role,Suggested,"The role of any individuals, projects, or institutions that contributed to the creation of this data. May be presented as free text, or in a structured format compatible with conversion to ncML (e.g., insensitive to changes in whitespace, including end-of-line characters). Multiple roles should be presented in the same order and number as the names in contributor_names.",contributor_role,rdf:Property,contributor_role,rdfs:Literal,<http://wiki.esipfed.org/index.php/Attribute_Convention_for_Data_Discovery_1-3#contributor_role>
coverage_content_type,Highly Recommended Variable Attributes,"An ISO 19115-1 code to indicate the source of the data (image, thematicClassification, physicalMeasurement, auxiliaryInformation, qualityInformation, referenceInformation, modelResult, or coordinate).",coverage_content_type,rdf:Property,coverage_content_type,rdfs:Literal,<http://wiki.esipfed.org/index.php/Attribute_Convention_for_Data_Discovery_1-3#coverage_content_type>
creator_email,Recommended,The email address of the person (or other creator type specified by the creator_type attribute) principally responsible for creating this data.,creator_email,rdf:Property,creator_email,rdfs:Literal,<http://wiki.esipfed.org/index.php/Attribute_Convention_for_Data_Discovery_1-3#creator_email>
creator_institution,Suggested,"The institution of the creator; should uniquely identify the creator's institution. This attribute's value should be specified even if it matches the value of publisher_institution, or if creator_type is institution.",creator_institution,rdf:Property,creator_institution,rdfs:Literal,<http://wiki.esipfed.org/index.php/Attribute_Convention_for_Data_Discovery_1-3#creator_institution>
creator_name,Recommended,The name of the person (or other creator type specified by the creator_type attribute) principally responsible for creating this data.,creator_name,rdf:Property,creator_name,rdfs:Literal,<http://wiki.esipfed.org/index.php/Attribute_Convention_for_Data_Discovery_1-3#creator_name>
creator_type,Suggested,"Specifies type of creator with one of the following: 'person', 'group', 'institution', or 'position'. If this attribute is not specified, the creator is assumed to be a person.",creator_type,rdf:Property,creator_type,rdfs:Literal,<http://wiki.esipfed.org/index.php/Attribute_Convention_for_Data_Discovery_1-3#creator_type>
creator_url,Recommended,The URL of the person (or other creator type specified by the creator_type attribute) principally responsible for creating this data.,creator_url,rdf:Property,creator_url,rdfs:Literal,<http://wiki.esipfed.org/index.php/Attribute_Convention_for_Data_Discovery_1-3#creator_url>
date_created,Recommended,"The date on which this version of the data was created. (Modification of values implies a new version, hence this would be assigned the date of the most recent values modification.) Metadata changes are not considered when assigning the date_created. The ISO 8601:2004 extended date format is recommended, as described in the Attribute Content Guidance section.",date_created,rdf:Property,date_created,rdfs:Literal,<http://wiki.esipfed.org/index.php/Attribute_Convention_for_Data_Discovery_1-3#date_created>
date_issued,Suggested,"The date on which this data (including all modifications) was formally issued (i.e., made available to a wider audience). Note that these apply just to the data, not the metadata. The ISO 8601:2004 extended date format is recommended, as described in the Attributes Content Guidance section.",date_issued,rdf:Property,date_issued,rdfs:Literal,<http://wiki.esipfed.org/index.php/Attribute_Convention_for_Data_Discovery_1-3#date_issued>
date_metadata_modified,Suggested,"The date on which the metadata was last modified. The ISO 8601:2004 extended date format is recommended, as described in the Attributes Content Guidance section.",date_metadata_modified,rdf:Property,date_metadata_modified,rdfs:Literal,<http://wiki.esipfed.org/index.php/Attribute_Convention_for_Data_Discovery_1-3#date_metadata_modified>
date_modified,Suggested,"The date on which the data was last modified. Note that this applies just to the data, not the metadata. The ISO 8601:2004 extended date format is recommended, as described in the Attributes Content Guidance section.",date_modified,rdf:Property,date_modified,rdfs:Literal,<http://wiki.esipfed.org/index.php/Attribute_Convention_for_Data_Discovery_1-3#date_modified>
geospatial_bounds,Recommended,"Describes the data's 2D or 3D geospatial extent in OGC's Well-Known Text (WKT) Geometry format (reference the OGC Simple Feature Access (SFA) specification). The meaning and order of values for each point's coordinates depends on the coordinate reference system (CRS). The ACDD default is 2D geometry in the EPSG:4326 coordinate reference system. The default may be overridden with geospatial_bounds_crs and geospatial_bounds_vertical_crs (see those attributes). EPSG:4326 coordinate values are latitude (decimal degrees_north) and longitude (decimal degrees_east), in that order. Longitude values in the default case are limited to the [-180, 180) range. Example: 'POLYGON ((-111.29 40.26, -111.29 41.26, -110.29 41.26, -110.29 40.26, -111.29 40.26))'.",geospatial_bounds,rdf:Property,geospatial_bounds,rdfs:Literal,<http://wiki.esipfed.org/index.php/Attribute_Convention_for_Data_Discovery_1-3#geospatial_bounds>
geospatial_bounds_crs,Recommended,"The coordinate reference system (CRS) of the point coordinates in the geospatial_bounds attribute. This CRS may be 2-dimensional or 3-dimensional, but together with geospatial_bounds_vertical_crs, if that attribute is supplied, must match the dimensionality, order, and meaning of point coordinate values in the geospatial_bounds attribute. If geospatial_bounds_vertical_crs is also present then this attribute must only specify a 2D CRS. EPSG CRSs are strongly recommended. If this attribute is not specified, the CRS is assumed to be EPSG:4326. Examples: 'EPSG:4979' (the 3D WGS84 CRS), 'EPSG:4047'.",geospatial_bounds_crs,rdf:Property,geospatial_bounds_crs,rdfs:Literal,<http://wiki.esipfed.org/index.php/Attribute_Convention_for_Data_Discovery_1-3#geospatial_bounds_crs>
geospatial_bounds_vertical_crs,Recommended,"The vertical coordinate reference system (CRS) for the Z axis of the point coordinates in the geospatial_bounds attribute. This attribute cannot be used if the CRS in geospatial_bounds_crs is 3-dimensional; to use this attribute, geospatial_bounds_crs must exist and specify a 2D CRS. EPSG CRSs are strongly recommended. There is no default for this attribute when not specified. Examples: 'EPSG:5829' (instantaneous height above sea level), ""EPSG:5831"" (instantaneous depth below sea level), or 'EPSG:5703' (NAVD88 height).",geospatial_bounds_vertical_crs,rdf:Property,geospatial_bounds_vertical_crs,rdfs:Literal,<http://wiki.esipfed.org/index.php/Attribute_Convention_for_Data_Discovery_1-3#geospatial_bounds_vertical_crs>
geospatial_lat_max,Recommended,Describes a simple upper latitude limit; may be part of a 2- or 3-dimensional bounding region. Geospatial_lat_max specifies the northernmost latitude covered by the dataset.,geospatial_lat_max,rdf:Property,geospatial_lat_max,rdfs:Literal,<http://wiki.esipfed.org/index.php/Attribute_Convention_for_Data_Discovery_1-3#geospatial_lat_max>
geospatial_lat_min,Recommended,Describes a simple lower latitude limit; may be part of a 2- or 3-dimensional bounding region. Geospatial_lat_min specifies the southernmost latitude covered by the dataset.,geospatial_lat_min,rdf:Property,geospatial_lat_min,rdfs:Literal,<http://wiki.esipfed.org/index.php/Attribute_Convention_for_Data_Discovery_1-3#geospatial_lat_min>
geospatial_lat_resolution,Suggested,"Information about the targeted spacing of points in latitude. Recommend describing resolution as a number value followed by the units. Examples: '100 meters', '0.1 degree'",geospatial_lat_resolution,rdf:Property,geospatial_lat_resolution,rdfs:Literal,<http://wiki.esipfed.org/index.php/Attribute_Convention_for_Data_Discovery_1-3#geospatial_lat_resolution>
geospatial_lat_units,Suggested,"Units for the latitude axis described in ""geospatial_lat_min"" and ""geospatial_lat_max"" attributes. These are presumed to be ""degree_north""; other options from udunits may be specified instead.",geospatial_lat_units,rdf:Property,geospatial_lat_units,rdfs:Literal,<http://wiki.esipfed.org/index.php/Attribute_Convention_for_Data_Discovery_1-3#geospatial_lat_units>
geospatial_lon_max,Recommended,"Describes a simple longitude limit; may be part of a 2- or 3-dimensional bounding region. geospatial_lon_max specifies the easternmost longitude covered by the dataset. Cases where geospatial_lon_min is greater than geospatial_lon_max indicate the bounding box extends from geospatial_lon_max, through the longitude range discontinuity meridian (either the antimeridian for -180:180 values, or Prime Meridian for 0:360 values), to geospatial_lon_min; for example, geospatial_lon_min=170 and geospatial_lon_max=-175 incorporates 15 degrees of longitude (ranges 170 to 180 and -180 to -175).",geospatial_lon_max,rdf:Property,geospatial_lon_max,rdfs:Literal,<http://wiki.esipfed.org/index.php/Attribute_Convention_for_Data_Discovery_1-3#geospatial_lon_max>
geospatial_lon_min,Recommended,Describes a simple longitude limit; may be part of a 2- or 3-dimensional bounding region. geospatial_lon_min specifies the westernmost longitude covered by the dataset. See also geospatial_lon_max.,geospatial_lon_min,rdf:Property,geospatial_lon_min,rdfs:Literal,<http://wiki.esipfed.org/index.php/Attribute_Convention_for_Data_Discovery_1-3#geospatial_lon_min>
geospatial_lon_resolution,Suggested,"Information about the targeted spacing of points in longitude. Recommend describing resolution as a number value followed by units. Examples: '100 meters', '0.1 degree'",geospatial_lon_resolution,rdf:Property,geospatial_lon_resolution,rdfs:Literal,<http://wiki.esipfed.org/index.php/Attribute_Convention_for_Data_Discovery_1-3#geospatial_lon_resolution>
geospatial_lon_units,Suggested,"Units for the longitude axis described in ""geospatial_lon_min"" and ""geospatial_lon_max"" attributes. These are presumed to be ""degree_east""; other options from udunits may be specified instead.",geospatial_lon_units,rdf:Property,geospatial_lon_units,rdfs:Literal,<http://wiki.esipfed.org/index.php/Attribute_Convention_for_Data_Discovery_1-3#geospatial_lon_units>
geospatial_vertical_max,Recommended,Describes the numerically larger vertical limit; may be part of a 2- or 3-dimensional bounding region. See geospatial_vertical_positive and geospatial_vertical_units.,geospatial_vertical_max,rdf:Property,geospatial_vertical_max,rdfs:Literal,<http://wiki.esipfed.org/index.php/Attribute_Convention_for_Data_Discovery_1-3#geospatial_vertical_max>
geospatial_vertical_min,Recommended,Describes the numerically smaller vertical limit; may be part of a 2- or 3-dimensional bounding region. See geospatial_vertical_positive and geospatial_vertical_units.,geospatial_vertical_min,rdf:Property,geospatial_vertical_min,rdfs:Literal,<http://wiki.esipfed.org/index.php/Attribute_Convention_for_Data_Discovery_1-3#geospatial_vertical_min>
geospatial_vertical_positive,Recommended,"One of 'up' or 'down'. If up, vertical values are interpreted as 'altitude', with negative values corresponding to below the reference datum (e.g., under water). If down, vertical values are interpreted as 'depth', positive values correspond to below the reference datum. Note that if geospatial_vertical_positive is down ('depth' orientation), the geospatial_vertical_min attribute specifies the data's vertical location furthest from the earth's center, and the geospatial_vertical_max attribute specifies the location closest to the earth's center.",geospatial_vertical_positive,rdf:Property,geospatial_vertical_positive,rdfs:Literal,<http://wiki.esipfed.org/index.php/Attribute_Convention_for_Data_Discovery_1-3#geospatial_vertical_positive>
geospatial_vertical_resolution,Suggested,Information about the targeted vertical spacing of points. Example: '25 meters',geospatial_vertical_resolution,rdf:Property,geospatial_vertical_resolution,rdfs:Literal,<http://wiki.esipfed.org/index.php/Attribute_Convention_for_Data_Discovery_1-3#geospatial_vertical_resolution>
geospatial_vertical_units,Suggested,"Units for the vertical axis described in ""geospatial_vertical_min"" and ""geospatial_vertical_max"" attributes. The default is EPSG:4979 (height above the ellipsoid, in meters); other vertical coordinate reference systems may be specified. Note that the common oceanographic practice of using pressure for a vertical coordinate, while not strictly a depth, can be specified using the unit bar. Examples: 'EPSG:5829' (instantaneous height above sea level), 'EPSG:5831' (instantaneous depth below sea level).",geospatial_vertical_units,rdf:Property,geospatial_vertical_units,rdfs:Literal,<http://wiki.esipfed.org/index.php/Attribute_Convention_for_Data_Discovery_1-3#geospatial_vertical_units>
history,Recommended,"Provides an audit trail for modifications to the original data. This attribute is also in the NetCDF Users Guide: 'This is a character array with a line for each invocation of a program that has modified the dataset. Well-behaved generic netCDF applications should append a line containing: date, time of day, user name, program name and command arguments.' To include a more complete description you can append a reference to an ISO Lineage entity; see NOAA EDM ISO Lineage guidance.",history,rdf:Property,history,rdfs:Literal,<http://wiki.esipfed.org/index.php/Attribute_Convention_for_Data_Discovery_1-3#history>
id,Recommended,"An identifier for the data set, provided by and unique within its naming authority. The combination of the ""naming authority"" and the ""id"" should be globally unique, but the id can be globally unique by itself also. IDs can be URLs, URNs, DOIs, meaningful text strings, a local key, or any other unique string of characters. The id should not include white space characters.",id,rdf:Property,id,rdfs:Literal,<http://wiki.esipfed.org/index.php/Attribute_Convention_for_Data_Discovery_1-3#id>
institution,Recommended,The name of the institution principally responsible for originating this data. This attribute is recommended by the CF convention.,institution,rdf:Property,institution,rdfs:Literal,<http://wiki.esipfed.org/index.php/Attribute_Convention_for_Data_Discovery_1-3#institution>
instrument,Suggested,Name of the contributing instrument(s) or sensor(s) used to create this data set or product. Indicate controlled vocabulary used in instrument_vocabulary.,instrument,rdf:Property,instrument,rdfs:Literal,<http://wiki.esipfed.org/index.php/Attribute_Convention_for_Data_Discovery_1-3#instrument>
instrument_vocabulary,Suggested,"Controlled vocabulary for the names used in the ""instrument"" attribute.",instrument_vocabulary,rdf:Property,instrument_vocabulary,rdfs:Literal,<http://wiki.esipfed.org/index.php/Attribute_Convention_for_Data_Discovery_1-3#instrument_vocabulary>
keywords,Highly Recommended,"A comma-separated list of key words and/or phrases. Keywords may be common words or phrases, terms from a controlled vocabulary (GCMD is often used), or URIs for terms from a controlled vocabulary (see also ""keywords_vocabulary"" attribute).",keywords,rdf:Property,keywords,rdfs:Literal,<http://wiki.esipfed.org/index.php/Attribute_Convention_for_Data_Discovery_1-3#keywords>
keywords_vocabulary,Suggested,"If you are using a controlled vocabulary for the words/phrases in your ""keywords"" attribute, this is the unique name or identifier of the vocabulary from which keywords are taken. If more than one keyword vocabulary is used, each may be presented with a prefix and a following comma, so that keywords may optionally be prefixed with the controlled vocabulary key. Example: 'GCMD:GCMD Keywords, CF:NetCDF COARDS Climate and Forecast Standard Names'.",keywords_vocabulary,rdf:Property,keywords_vocabulary,rdfs:Literal,<http://wiki.esipfed.org/index.php/Attribute_Convention_for_Data_Discovery_1-3#keywords_vocabulary>
license,Recommended,"Provide the URL to a standard or specific license, enter ""Freely Distributed"" or ""None"", or describe any restrictions to data access and distribution in free text.",license,rdf:Property,license,rdfs:Literal,<http://wiki.esipfed.org/index.php/Attribute_Convention_for_Data_Discovery_1-3#license>
metadata_link,Suggested,A URL that gives the location of more complete metadata. A persistent URL is recommended for this attribute.,metadata_link,rdf:Property,metadata_link,rdfs:Literal,<http://wiki.esipfed.org/index.php/Attribute_Convention_for_Data_Discovery_1-3#metadata_link>
naming_authority,Recommended,The organization that provides the initial id (see above) for the dataset. The naming authority should be uniquely specified by this attribute. We recommend using reverse-DNS naming for the naming authority; URIs are also acceptable. Example: 'edu.ucar.unidata'.,naming_authority,rdf:Property,naming_authority,rdfs:Literal,<http://wiki.esipfed.org/index.php/Attribute_Convention_for_Data_Discovery_1-3#naming_authority>
platform,Suggested,"Name of the platform(s) that supported the sensor data used to create this data set or product. Platforms can be of any type, including satellite, ship, station, aircraft or other. Indicate controlled vocabulary used in platform_vocabulary.",platform,rdf:Property,platform,rdfs:Literal,<http://wiki.esipfed.org/index.php/Attribute_Convention_for_Data_Discovery_1-3#platform>
platform_vocabulary,Suggested,"Controlled vocabulary for the names used in the ""platform"" attribute.",platform_vocabulary,rdf:Property,platform_vocabulary,rdfs:Literal,<http://wiki.esipfed.org/index.php/Attribute_Convention_for_Data_Discovery_1-3#platform_vocabulary>
processing_level,Recommended,A textual description of the processing (or quality control) level of the data.,processing_level,rdf:Property,processing_level,rdfs:Literal,<http://wiki.esipfed.org/index.php/Attribute_Convention_for_Data_Discovery_1-3#processing_level>
product_version,Suggested,"Version identifier of the data file or product as assigned by the data creator. For example, a new algorithm or methodology could result in a new product_version.",product_version,rdf:Property,product_version,rdfs:Literal,<http://wiki.esipfed.org/index.php/Attribute_Convention_for_Data_Discovery_1-3#product_version>
program,Suggested,"The overarching program(s) of which the dataset is a part. A program consists of a set (or portfolio) of related and possibly interdependent projects that meet an overarching objective. Examples: 'GHRSST', 'NOAA CDR', 'NASA EOS', 'JPSS', 'GOES-R'.",program,rdf:Property,program,rdfs:Literal,<http://wiki.esipfed.org/index.php/Attribute_Convention_for_Data_Discovery_1-3#program>
project,Recommended,"The name of the project(s) principally responsible for originating this data. Multiple projects can be separated by commas, as described under Attribute Content Guidelines. Examples: 'PATMOS-X', 'Extended Continental Shelf Project'.",project,rdf:Property,project,rdfs:Literal,<http://wiki.esipfed.org/index.php/Attribute_Convention_for_Data_Discovery_1-3#project>
publisher_email,Recommended,"The email address of the person (or other entity specified by the publisher_type attribute) responsible for publishing the data file or product to users, with its current metadata and format.",publisher_email,rdf:Property,publisher_email,rdfs:Literal,<http://wiki.esipfed.org/index.php/Attribute_Convention_for_Data_Discovery_1-3#publisher_email>
publisher_institution,Suggested,"The institution that presented the data file or equivalent product to users; should uniquely identify the institution. If publisher_type is institution, this should have the same value as publisher_name.",publisher_institution,rdf:Property,publisher_institution,rdfs:Literal,<http://wiki.esipfed.org/index.php/Attribute_Convention_for_Data_Discovery_1-3#publisher_institution>
publisher_name,Recommended,"The name of the person (or other entity specified by the publisher_type attribute) responsible for publishing the data file or product to users, with its current metadata and format.",publisher_name,rdf:Property,publisher_name,rdfs:Literal,<http://wiki.esipfed.org/index.php/Attribute_Convention_for_Data_Discovery_1-3#publisher_name>
publisher_type,Suggested,"Specifies type of publisher with one of the following: 'person', 'group', 'institution', or 'position'. If this attribute is not specified, the publisher is assumed to be a person.",publisher_type,rdf:Property,publisher_type,rdfs:Literal,<http://wiki.esipfed.org/index.php/Attribute_Convention_for_Data_Discovery_1-3#publisher_type>
publisher_url,Recommended,"The URL of the person (or other entity specified by the publisher_type attribute) responsible for publishing the data file or product to users, with its current metadata and format.",publisher_url,rdf:Property,publisher_url,rdfs:Literal,<http://wiki.esipfed.org/index.php/Attribute_Convention_for_Data_Discovery_1-3#publisher_url>
references,Suggested,Published or web-based references that describe the data or methods used to produce it. Recommend URIs (such as a URL or DOI) for papers or other references. This attribute is defined in the CF conventions.,references,rdf:Property,references,rdfs:Literal,<http://wiki.esipfed.org/index.php/Attribute_Convention_for_Data_Discovery_1-3#references>
source,Recommended,"The method of production of the original data. If it was model-generated, source should name the model and its version. If it is observational, source should characterize it. This attribute is defined in the CF Conventions. Examples: 'temperature from CTD #1234'; 'world model v.0.1'.",source,rdf:Property,source,rdfs:Literal,<http://wiki.esipfed.org/index.php/Attribute_Convention_for_Data_Discovery_1-3#source>
standard_name_vocabulary,Recommended,The name and version of the controlled vocabulary from which variable standard names are taken. (Values for any standard_name attribute must come from the CF Standard Names vocabulary for the data file or product to comply with CF.) Example: 'CF Standard Name Table v27'.,standard_name_vocabulary,rdf:Property,standard_name_vocabulary,rdfs:Literal,<http://wiki.esipfed.org/index.php/Attribute_Convention_for_Data_Discovery_1-3#standard_name_vocabulary>
summary,Highly Recommended,"A paragraph describing the dataset, analogous to an abstract for a paper.",summary,rdf:Property,summary,rdfs:Literal,<http://wiki.esipfed.org/index.php/Attribute_Convention_for_Data_Discovery_1-3#summary>
time_coverage_duration,Recommended,"Describes the duration of the data set. Use ISO 8601:2004 duration format, preferably the extended format as recommended in the Attribute Content Guidance section.",time_coverage_duration,rdf:Property,time_coverage_duration,rdfs:Literal,<http://wiki.esipfed.org/index.php/Attribute_Convention_for_Data_Discovery_1-3#time_coverage_duration>
time_coverage_end,Recommended,"Describes the time of the last data point in the data set. Use ISO 8601:2004 date format, preferably the extended format as recommended in the Attribute Content Guidance section.",time_coverage_end,rdf:Property,time_coverage_end,rdfs:Literal,<http://wiki.esipfed.org/index.php/Attribute_Convention_for_Data_Discovery_1-3#time_coverage_end>
time_coverage_resolution,Recommended,"Describes the targeted time period between each value in the data set. Use ISO 8601:2004 duration format, preferably the extended format as recommended in the Attribute Content Guidance section.",time_coverage_resolution,rdf:Property,time_coverage_resolution,rdfs:Literal,<http://wiki.esipfed.org/index.php/Attribute_Convention_for_Data_Discovery_1-3#time_coverage_resolution>
time_coverage_start,Recommended,"Describes the time of the first data point in the data set. Use the ISO 8601:2004 date format, preferably the extended format as recommended in the Attribute Content Guidance section.",time_coverage_start,rdf:Property,time_coverage_start,rdfs:Literal,<http://wiki.esipfed.org/index.php/Attribute_Convention_for_Data_Discovery_1-3#time_coverage_start>
title,Highly Recommended,"A short phrase or sentence describing the dataset. In many discovery systems, the title will be displayed in the results list from a search, and therefore should be human readable and reasonable to display in a list of such names. This attribute is also recommended by the NetCDF Users Guide and the CF conventions.",title,rdf:Property,title,rdfs:Literal,<http://wiki.esipfed.org/index.php/Attribute_Convention_for_Data_Discovery_1-3#title>
Metadata_Convention,Deprecated,Metadata_Convention: removed in favor of 'Conventions',,,,,