-- Definition -- An individual having a particular role associated with a real world object. -- Definition -- Role of the individual within the organisation. -- Definition -- The organisation that the individual belongs to. -- Definition -- A body/organization having a particular role associated with a real world object. -- Description -- EXAMPLE HECToR ( real world object) is funded by the UK Research Councils ( funder). -- Definition -- Acronym of the organisation -- Definition -- Textual description of the organisation. --Definition-- Individual or organisation related to organisation. -- Definition -- A party , individual or organisation, having a responsibility regarding a real world object. -- Definition -- External identifier of the organisation. -- Definition -- Name of the responsible party. -- Definition -- Information required enabling contact with the responsible person and/or organisation. -- Definition -- Responsibility, identification of, and means of communication with, person(s) and organisations associated with a real word object. -- Name -- ESPAS Identifier -- Definition -- The identifier of the object in the ESPAS system -- Description -- Every standalone data object in the ESPAS system must have an ESPAS_Identifier defined. Guidelines for ESPAS_Identifiers: namespace shall uniquely identify the 'owner' of the item and shall be according to an agreed convention within the ESPAS system. e.g. stfc, nkua, eiscat, dlr etc. localID assignments are at the discrection of the'owner but shall be alphanumeric strings with no spaces, [a decision needs to be take as to we encourage the use of opaque or non-opaque identifiers e.g. ABC234 versus radarX] version numbers are at the discretion of the owner but should usually follow typical conventions 1, 2, 3 or 1.0, 1.1, 2.0 Both namespaces and localIds should be suitable for inclusion in URLs i.e. must not use the following reserved characters: = | ; | / | # | ? | : | space ---------------------------------------------------------- Encoding namespaces according to the guidelines will enable the publication of information resources in a RESTful manner. e..g (exact url structure to be agreed) http://www.espas-fp7.eu/dataset/stfc/STFC24/ (latest version of stfc owned object STFC24) http://www.espas-fp7.eu/dataset/stfc/STFC24/2 (version 2) or with non-opaque identifiers http://www.espas-fp7.eu/dataset/eiscat/myionosonde (myionosonde owned by eiscat) These urls can then resolve to XML-based descriptions (or RDF-XML, or both using HTTP content negotiation) depending on the agreed system architecture. -- Name -- local ID -- Definition -- The local part of the identifier (assigned by the owner) -- Name -- namespace -- Definition -- the namespace part of the identifier, agreed within ESPAS, e.g. 'stfc'. -- Name -- version -- Definition -- The version number of the object being identified -- Name -- creation date -- Definition -- Date when the object/record was first created -- Name -- last modification date -- Definition -- Date when the object/record was last modified (the most recent modification) -- Definition -- Standardized resource reference (online/offline). -- Definition -- Reference to documentation online. Information about online sources from which the dataset, specification, or community profile name and extended metadata elements can be obtained.