jmd0.1 - JMA's simple schema for WIS Discovery Metadata revisions: * 2014-06-27: charset added for support of WMO Core Metadata Profile v1.3 * 2011-07-30: widely-advertised version this too liberal rule is intended for XSD schemaLocation etc. UUID computed from serialized XML representation of this record. Intended for storage management purpose. Semantic comparison of two jmd:metadata records should ignore this field. Metadata file identifier. Should be named globally unique. Declared optional for situations such as drafting process, but is [Mandatory] for published metadata. Organization name of contact for metadata. In WIS, it's name of the WIS Centre that has created the metadata. Hence this is a property of metadata, not of dataset. Full spelled name in English is preferred to acronyms or abbreviation unless the word is clearly understood in entire WIS. [Mandatory] URLs as conctact for metadata. In WIS, it should be any dereferencable URI that can be used to make contact to the WIS Centre. Schemes mailto:, http:, tel:, or fax: are supported. Thre is no limitation on number, except that http: URL cannot be given more than once for ISO 19115 compatibility. [Mandatory] Organization name of contact for data content. This is a property of dataset, not of metadata. Full spelled name in English is preferred to acronyms or abbreviation unless those words are understood in entire WIS. If the element is missing jmd:wisorg is used instead. URLs as conctact for data content Schemes mailto:, http:, tel:, or fax: are expected. Thre is no limitation on number, except that http: URL cannot be given more than once for ISO 19115 compatibility. If the element is missing jmd:wiscont is used instead. The timestamp or date when this metadata record is made. [Mandatory] Frequency at which metadata (not the data content) is expected to be updated. Subject Keywords Word or short phrase that describes the discipline or field of learning of the dataset. Use of code list "jmdTopicCategoryCode" is strongly recommended. This is optional for backward compatibility but is [Mandatory] for WCMP compliance. Title of the dataset Some DAR catalogue displays only titles of the search result, thus it should be as descriptive as possible, while it is less useful to extend it more than one line. Rule of thumb: the text that exceeds 80 characters is suggested to be written in abstract. [Mandatory] Abstract. Narrative description of the dataset. The more information is more welcomed. Even duplicated information (such as geographic domain or thematic content) is useful, since typical DAR catalogue displays titles and abstracts in the search result. [Mandatory] Thematic keywords. Word or phrase that describe the theme or content of the dataset, such as physical quantity, weather phenomenon, observation type or data processing. Multiple phrases for multiple concept should be stored in separate <jmd:themekey> elements. Metadata creator/manager is advised not to spend too much effort to make the keyword list complete. Five or ten keywords should be enough for data discovery by users in other disciplines. No specific controlled vocabulary has been assigned. It is too liberal and new restriction may apply in the future. Latitude of southern end of the geographical bounding box WGS 84 is assumed as CRS [cf: Rec 1 WMO/CBS-Ext.(06)], but DAR does not require high precision. Even ten-degree range is welcomed for mobile observation. Multiple use is currently not recommended since its portability is unclear. Units must be degree and must be shown explicitly. Acceptable range: -90 to 90, northward positive (cf. ISO 19115). deg Latitude of northern end of the geographical bounding box WGS 84 is assumed as CRS [cf: Rec 1 WMO/CBS-Ext.(06)], but DAR does not require high precision. Even ten-degree range is welcomed for mobile observation. Multiple use is currently not recommended since its portability is unclear. Units must be degree and must be shown explicitly. Acceptable range: -90 to 90, northward positive (cf. ISO 19115). deg Longitude of western end of the geographical bounding box WGS 84 is assumed as CRS [cf: Rec 1 WMO/CBS-Ext.(06)], but DAR does not require high precision. Even ten-degree range is welcomed for mobile observation. Multiple use is currently not recommended since its portability is unclear. Units must be degree and must be shown explicitly. Acceptable range: -180 to 180, eastward positive (cf. ISO 19115). deg Longitude of eastern end of the geographical bounding box WGS 84 is assumed as CRS [cf: Rec 1 WMO/CBS-Ext.(06)], but DAR does not require high precision. Even ten-degree range is welcomed for mobile observation. Multiple use is currently not recommended since its portability is unclear. Units must be degree and must be shown explicitly. Acceptable range: -180 to 180, eastward positive (cf. ISO 19115). deg Geographical keywords to describe the horizontal extent of data More computer-friendly notation of the place. Currently WMO Station Index (5 digits) and ICAO location identifier (4 uppercase letters) are recognised. Horizontal resolution of the dataset. If different grid spacings are used in meridional and zonal directions, use coarser value. Units of horizontal resolution: "deg" is assumed if missing. deg km m Vertical location keywords. Word or short phrase that describes vertical extent of the dataset. Use of code list "jmdTopicCategoryCode" is enforced for former Excel version but not here for ISO compatibility. It is too liberal and new restriction may apply in the future. The time period for which a dataset fragment is available. This element is used when old data is removed after some period of time. Hence it is nonsense to use it with <jmd:begdate>. The beginning date (and time if appropriate) to which the available data refers. This element is used when old data is not deleted. Hence it is nonsense to use it with <jmd:avail>. The ending date (and time if appropriate) to which the available data refers. This element is used (1) if no new data is coming, or (2) in case metadata is issued every time the data is updated. The actual date when the content of the dataset is updated or released. Rationale: Some academic data sources issue many versions of the same dataset including the time the data content refers to. In some cases old versions of the data are not withdrawn and many versions are kept available at the same time to compare the progress of technology. Hence there is a need to distinguish them and <jmd:begdate> does not work. Metadata may be managed independently with the dataset so <jmd:mddate> won't work too. Maximum forecast time of the dataset, relative to analysis reference time. Rationale: Some NWP centre is running many forecast models for different forecast time range. There is a need to distinguish all the same dataset except for the forecast time period. Frequency at which the data content (not metadata) is expected to be updated. This element gives temporal resolution in an approximate sense. There is no need of guarantee of regular update: for example, you can use "hourly" if hourly observation is done only in daytime or in storm watch. Similarly an observation three times a day at 00Z, 12Z, 18Z can be described as "6-hourly" (or no problem to use "8-hourly" if it is described as "three times a day"). [near-deprecated] Time of the day at which the data is updated or delivered. character set of the resource. Needed for data. File format or WMO code form in which the dataset is expressed. FM number and name for WMO Codes (ex. "FM 92 GRIB" for GRIB). Version number of format. CBS session for WMO Codes (ex. "XI Ext." for PILOT, "XI Ext." for GRIB Edition 1, and "XIV" for GRIB Edition 2). Instance Pattern. Regular expression to be matched with filename in GISC Cache, in order to search dataset fragments from dataset metadata. This element is designed for globally-distributed data for which the data originator (NC or DCPC) cannot specify actual URL. GTS bulletin is assumed to be a file with "T_" form of WMO Filename Convention. Dereferencable URI to reach data retrieval facility. It may be dataset itself, HTML page to navigate inside a dataset to list fragments, HTML form to request delivery, or some data service protocol. Brief description of restriction on data access. Value "no restriction" is recommended for dataset with open access. The reason why this restriction is imposed is usually out of scope; use other elements in this section instead. Brief description of a group of people who will be allowed to access the data. Distribution Scope Code (GlobalDistribution/RegionalDistribution/ ...) is mandatory for GTS data and recommended for other data. Brief description of the policy of redistribution. GTSPriority1/2/3/4 must be used for GTS data. Brief description of the use policy imposed on the dataset. The date when the metadata is incorporated in DAR catalogue. Internal purposes Topic category of ISO 19115. High-level geospatial data thematic classification to assist in the grouping and search of available geospatial datasets. This is optional for compatibility to versions before 2010-09-15, and "climatologyMeteorologyAtmosphere" is assumed if none is specified. s min h d mon a Possible values for subject keywrords weatherObservations weatherForecasts meteorology hydrology climatology landMeteorologyClimate synopticMeteorology marineMeteorology agriculturalMeteorology aerology marineAerology oceanography landHydrology rocketSounding pollution waterPollution landWaterPollution seaPollution landPollution airPollution glaciology actinometry satelliteObservation airplaneObservation observationPlatform atmosphericComposition spaceWeather Extended frequency code to that of ISO 19115, partly derived from obsolete version 1.0 of WMO Core Profile. [near-deprecated] 1-minute 5-minute 10-minute 15-minute 30-minute 2-hourly 8-hourly 10-daily decadally continuous continually quarterly daily 12Z irregularly irregulaly irregulaly AS AVAILABLE irregularly AS REQUIRED irregulaly AS REQUIRED Frequency code defined in ISO 19115 [near-deprecated] continual daily weekly fortnightly monthly quartely biannually annually asNeeded irregular notPlanned unknown hourly 3-hourly 6-hourly 12-hourly Possible values for vertical extent code, enforced in the former Excel version of the schema. Surface Sea surface Upper-air Surface/Upper Ocean Troposphere Stratosphere Top of Atmosphere Possible values of topicat, defined in ISO 19115. farming biota boundaries climatologyMeteorologyAtmosphere economy elevation environment geoscientificInformation health imageryBaseMapsEarthCover intelligenceMilitary inlandWaters location oceans planningCadastre society structure transportation utilitiesCommunication ucs2 ucs4 utf7 utf8 utf16 8859part1 8859part2 8859part3 8859part4 8859part5 8859part6 8859part7 8859part8 8859part9 8859part10 8859part11 8859part12 8859part13 8859part14 8859part15 8859part16 jis shiftJIS eucJP usAscii ebcdic eucKR big5 GB2312 8859part7