agiorguk/gemini

Issues

• Page 1054-operational-guide is quite out of date

  #107 opened a year ago by PeterParslow
  1

• Services abstract references dataset encoding

  #114 opened a year ago by archaeogeek
  2

• Services reference date should not be called "dataset reference date"

  #118 opened a year ago by archaeogeek
  2

• drop services equivalent scale element

  #119 opened a year ago by archaeogeek
  2

• Discussion to clarify interpretation of Limitations on Public Access and Use Constraints

  #61 opened 4 years ago by Sgaff
  5

• Current GEMINI encoding of dataset language and metadata language is not valid in INSPIRE

  #68 opened 3 years ago by Sgaff
  9

• Services Use Constraints guidance references datasets

  #122 opened a year ago by archaeogeek
  0

• Services Vertical Extent guidance references datasets

  #123 opened a year ago by archaeogeek
  4

• Duplication across pages 1049 & 1051

  #96 opened 2 years ago by PeterParslow
  1

• How to manage & publish GEMINI pages

  #64 opened 4 months ago by PeterParslow
  23

• Use constraints: inconsistency of "Encoding Guidance" with "Guidance" and Encoding Example 3

  #104 opened 4 months ago by PeterParslow
  1

• GEMINI 2.3 accepted by Open Standards Board

  #82 opened 4 months ago by PeterParslow
  3

• Check whether what we say about DOIs in _Resource identifier_ and _Resource locator_ makes sense.

  #59 opened 4 years ago by PeterParslow
  3

• Simple UML class diagram

  #170 opened 5 months ago by PeterParslow
  0

• DateTime with fractions of a second

  #160 opened 5 months ago by PeterParslow
  8

• Broken links (from migration)

  #161 opened 5 months ago by PeterParslow
  1

• Make it more obvious that GEMINI is released under CC-BY

  #67 opened 5 months ago by PeterParslow
  8

• Incorrect use of preprocessor tags to differentiate between datasets and services

  #137 opened 5 months ago by archaeogeek
  4

• Broken links from https://agiorguk.github.io/gemini/1048-uk-gemini-encoding-guidance.html

  #153 opened 5 months ago by PeterParslow
  1

• Add Metadata standard version & name to "XML Element order" page

  #62 opened 5 months ago by PeterParslow
  2

• Open Standards Board Meeting 16 September 2021

  #70 opened 5 months ago by KoalaGeo
  5

• Services Limitations on Public Access guidance references datasets

  #121 opened a year ago by archaeogeek
  1

• Services Alternative Title references dataset in guidance

  #115 opened a year ago by archaeogeek
  1

• Services keyword references datasets

  #120 opened a year ago by archaeogeek
  2

• Services conformity references datasets

  #117 opened a year ago by archaeogeek
  1

• Services bounding box guidance references datasets

  #116 opened a year ago by archaeogeek
  0

• Files referenced by schematron have disappeared

  #159 opened 5 months ago by nmtoken
  1

• Spatial data service type and Coupled resource for near real-time data streaming services

  #146 opened 10 months ago by coalsh
  4

• GEMET HTTP URI is invalid for Geology theme

  #147 opened 6 months ago by nmtoken
  1

• Do GEMINI follow INSPIRE TG Requirement C.15 on giving 'publication' date for originating controlled vocabulary?

  #69 opened 3 years ago by Sgaff
  5

• Broken link in encoding guidelines for metadata point of contact

  #65 opened 6 months ago by archaeogeek
  1

• Spatial Data Service sub-category

  #78 opened 2 years ago by PeterParslow
  5

• Keyword, Encoding Guidelines, example 2: ISO/TC 211 code list location needs updating

  #152 opened 6 months ago by PeterParslow
  0

• Responsible organisation role: why multiple occurence?

  #144 opened 10 months ago by PeterParslow
  0

• Resource identifier #36 comment on use of MD_Identifier over RS_Identifier.

  #143 opened a year ago by coalsh
  2

• conformity report for Implementing Rule 1089/2010, where conformance is not evaluated.

  #142 opened a year ago by coalsh
  2

• Typo in element 51 Guidance

  #60 opened a year ago by archaeogeek
  3

• Coupled resource: inconsistency in Encoding Guidelines & examples

  #103 opened 2 years ago by PeterParslow
  2

• References to EPSG URL(s) are outdated in guidance

  #87 opened 2 years ago by nmtoken
  1

• "GEMET - INSPIRE themes, version 1.0" test required

  #89 opened 2 years ago by nmtoken
  0

• INSPIRE link in Element 37 Spatial data service type

  #77 opened 2 years ago by PeterParslow
  4

• Pedantic point about "Bounding Box"

  #85 opened 2 years ago by PeterParslow
  2

• Python Libary for Gemini validation & creation

  #81 opened 2 years ago by KoalaGeo
  3

• Upgrading to ISO 19115:2016?

  #71 opened 3 years ago by AlexRamageScot1
  4

• Resource Locator - proper URL form

  #80 opened 2 years ago by PeterParslow
  0

• Avoid Keywords with punctuation

  #79 opened 2 years ago by PeterParslow
  1

• Add guidance on data.gov.uk GEMINI 2.3 harvesting

  #75 opened 2 years ago by PeterParslow
  1

• Should all gmx:Anchor instances have content?

  #76 opened 2 years ago by PeterParslow
  2

• GEMINI validation depends on ISO 19139 Table A validation

  #66 opened 3 years ago by PeterParslow
  0

• align GEMINI Data quality element with the new UK Government Data Quality Framework

  #63 opened 4 years ago by playarragorn
  5