ISO Service Identification

From DGIWG
Revision as of 15:23, 19 October 2017 by AUT Kautz (talk | contribs) (Created page with "<div style="color:#000000;margin-left:0cm;margin-right:0cm;">A Service Identification is an instance of srv:SV_ServiceIdentification or one of its subclasses.</div> <div styl...")
(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)
Jump to: navigation, search
A Service Identification is an instance of srv:SV_ServiceIdentification or one of its subclasses.
Its property instances are described below:


+ citation[1]:CI_Citation
  + title[1]:CharacterString RSTITLE - Default is To be determined
  + alternateTitle[0..1]:CharacterString RSALT (when set)
  + date[1..*]:CI_Date RSDATE (for each) -  See Note 1
    + date[1]:Date date - Default is 9999
    + dateType[1]:CI_DateTypeCode type - Default is publication
  + edition[0..1]:CharacterString RSED (when set)
  + editionDate[0..1]:CharacterString RSEDDAT (when set)
  + identifier[0..*]:RS_Identifier RSID (for each) -  See Identifier
+ abstract[1]:CharacterString RSABSTR - Default is To be determined
+ purpose[0..1]:CharacterString RSPURP (when set)
+ status[0..1]:MD_ProgressCode RSSTAT (when set)
+ pointOfContact[0..*]:CI_ResponsibleParty RSRPTY (for each) -  See Responsible Party
+ resourceMaintenance[0..1]:MD_MaintenanceInformation RSMTNC (when maintenanceFrequency is set)
  + maintenanceAndUpdateFrequency[1]:MD_MaintenanceFrequencyCode maintenanceFrequency - Default is unknown
  + dateOfNextUpdate[0..1]:Date maintenanceDate
  + maintenanceNote[0..1]:CharacterString maintenanceNote
+ graphicOverview[0..1]:MD_BrowseGraphic When THUMB is set
  + fileName[1]:CharacterString THUMB
  + fileDescription[0..1]:CharacterString thumbnail
+ graphicOverview[0..*]:MD_BrowseGraphic GPHICS (for each)
  + fileName[1]:CharacterString name (when linkage is not set)
  + fileName[1]:Anchor name (when linkage is set)
    + href[1]:CharacterString linkage
  + fileDescription[0..1]:CharacterString description
+ descriptiveKeywords[0..*]:MD_Keywords RSKWDS (for each) -  See Resource Keyword Set and Note 2
+ descriptiveKeywords[0..1]:MD_Keywords When RSRPTP is set -  See Resource Spatial Representation Type and Note 2
+ descriptiveKeywords[0..1]:MD_Keywords When RSTOPIC is set -  See Resource Topic Category and Note 2
+ resourceSpecificUsage[0..*]:MD_Usage RSSPUS (for each)
  + specificUsage[1]:CharacterString name
  + userDeterminedLimitations[0..1]:CharacterString limitation (when set)
  + userContactInfo[1]:CI_ResponsibleParty userContact -  See Responsible Party and Note 10
+ resourceConstraints[0..*]:MD_SecurityConstraints RSSCST (when set) -  See Security Constraints and Note 3
+ resourceConstraints[0..*]:NGMP_Constraints RSREL (for each)
  + useLimitation[0..1]:CharacterString statementExtension
  + releasability[1]:NGMP_Releasability
    + addressee[0..*]:CI_ResponsibleParty For each addressee
      + organisationName[1]:CharacterString addressee
      + role[1]:CI_RoleCode user
    + statement[1]:CharacterString statement -  See Note 12
    + statement[0..*]:CharacterString disseminationConstraints (for each)
+ resourceConstraints[0..*]:MD_Constraints For each RSUSE
  + useLimitation[0..*]:CharacterString RSUSE
+ resourceConstraints[0..*]:MD_LegalConstraints RSLCST (for each) -  See Legal Constraints
+ serviceType[1]:GenericName SRTYPE - Default is unknown
+ serviceTypeVersion[1]:CharacterString SRTVER - Default is unknown
+ extent[0..*]:EX_Extent RSEXT (for each) -  See Extent and Note 4
+ extent[0..*]:EX_Extent RSSRES (when RSSRES.distance is set)
  + description[1]:CharacterString distance -  See Note 5
+ extent[0..*]:EX_Extent RSSRES (when RSSRES.equivalentScale is set)
  + description[1]:CharacterString equivalentScale -  See Note 6
+ extent[0..*]:EX_Extent RSSRES (when RSSRES.levelOfDetail is set)
  + description[1]:CharacterString levelOfDetail -  See Note 7
+ extent[0..*]:EX_Extent RSSRES (when RSSRES.vertical is set)
  + description[1]:CharacterString vertical -  See Note 8
+ extent[0..*]:EX_Extent RSTRES (for each) (when set)
  + description[1]:CharacterString value & 10^-& factor & unit See Note 9
+ couplingType[1]:SV_CouplingType SRCPLING - Default is loose
+ coupledResource[0..*]:SV_CoupledResource SRCORS (for each)
  + operationName[1]:CharacterString operationName
  + identifier[1]:CharacterString identifier
  + ScopedName[0..1]:CodeType scope -  See Note 13
+ operatesOn[0..*]:MD_DataIdentification SROPRS (for each) -  See Note 9
+ containsOperations[1..*]:SV_OperationMetadata SROPER (for each)
  + operationName[1]:CharacterString name - Default is unknown
  + DCP[1..*]:DCPList platform (for each) - Default is WebServices
  + connectPoint[1..*]:CI_OnlineResource connectPoint (for each) -  See Online Location and Note 11
Notes:
1. There may be many instances of the date property with different date types including publication, revision or creation. The order of these instances is not fixed.
2. There may be many instances of the descriptiveKeywords property providing keywords from different thesaurus. The order of these instances is not fixed.
3. There may be many instances of the resourceConstraints property. The order of these instances is not fixed.
4. Except for non-geographic data and loose services, one of boundingBox and geogId is mandatory. Each boundingBox corresponds to a dataset subregion which implies that each boundingBox should be implemented as an instance of the extent property, possibly with the instances of geogId and boundingPolygon corresponding to the same subregion. For the same reasons, each boundingPolygon should be implemented as an instance of the extent property.
5. Preceded by "Ground sample distance: ", value and unit separated by a blank.
6. Preceded by "Equivalent scale: "
7. Preceded by "Level of detail: "
8. Preceded by "Vertical resolution: "
9. Preceded by "Temporal resolution: "
10. Default values are role=user and organisationName=undefined
11. The value may be defaulted to one instance of RSONLLC.
12. Default value for this element should be set by the implementer’s security policy.
13. gco:ScopedName is implemented as an XML global element of type gml:CodeType. The suggested Path is expressed with respect to the conceptual model, but there is no gml:CodeType element in the XML. scope.code and scope.namespace are respectively implemented in XML as the value of gco:ScopedName and the value of its codeSpace attribute