ISSUE-10: Best phrasing for CRS requirements

CRS requirements

Best phrasing for CRS requirements

State:
CLOSED
Product:
Use Cases and Requirements
Raised by:
Frans Knibbe
Opened on:
2015-05-11
Description:
This issue was previously raised on the e-mail list: https://lists.w3.org/Archives/Public/public-sdw-wg/2015Apr/0096.html

Currently, there is the CRS Definition requirement (http://w3c.github.io/sdw/UseCases/SDWUseCasesAndRequirements.html#CRSDefinition): "The URI of the Coordinate Reference System (CRS) shall be specified when geographic coordinates are present in the data. To be considered as sub-requirement of 5.30 Spatial metadata" (let's call it req. A)

A Best Practices requirement in the spreadsheet that has not been copied to the UCR document is: "There should be a standard for publishing data about coordinate reference systems (CRS) - Not only geographical reference systems." (let's call this req. B)

Is it OK to regard req A as fully covered by the Spatial metadata requirement?

Can we change the text of the CRS definition requirement (req. A) to the text of req. B?





Related Actions Items:
No related actions
Related emails:
  1. Fw: Australia plans new co-ordinates to fix sat-nav gap [SEC=UNCLASSIFIED] (from B.Bannerman@bom.gov.au on 2016-08-03)
  2. Re: Use of the word 'standard' in the UCR document. (from allaves@fi.upm.es on 2015-08-05)
  3. Re: Use of the word 'standard' in the UCR document. (from frans.knibbe@geodan.nl on 2015-08-05)
  4. Re: Use of the word 'standard' in the UCR document. (from allaves@fi.upm.es on 2015-08-05)
  5. Re: Use of the word 'standard' in the UCR document. (from frans.knibbe@geodan.nl on 2015-08-04)
  6. Re: [SDWWG] CRS Issues, Issue-28 (from frans.knibbe@geodan.nl on 2015-07-22)
  7. Re: [SDWWG] CRS Issues, Issue-28 (from frans.knibbe@geodan.nl on 2015-07-22)
  8. Re: [SDWWG] CRS Issues, Issue-28 [SEC=UNCLASSIFIED] (from B.Bannerman@bom.gov.au on 2015-07-22)
  9. RE: [SDWWG] CRS Issues, Issue-28 (from Simon.Cox@csiro.au on 2015-07-21)
  10. Re: [SDWWG] CRS Issues, Issue-28 (from jlieberman@tumblingwalls.com on 2015-07-21)
  11. RE: [SDWWG] CRS Issues, Issue-28 (from reh@bgs.ac.uk on 2015-07-21)
  12. Re: [SDWWG] CRS Issues, Issue-28 (from jlieberman@tumblingwalls.com on 2015-07-21)
  13. Re: [SDWWG] CRS Issues, Issue-28 (from jlieberman@tumblingwalls.com on 2015-07-21)
  14. Re: [SDWWG] CRS Issues, Issue-28 (from frans.knibbe@geodan.nl on 2015-07-21)
  15. Re: [SDWWG] CRS Issues, Issue-28 (from Kerry.Taylor@acm.org on 2015-07-21)
  16. Re: [SDWWG] CRS Issues, Issue-28 (from eparsons@google.com on 2015-07-21)
  17. Re: [Minutes] 2017-07-01 (from eparsons@google.com on 2015-07-21)
  18. Re: [Minutes] 2017-07-01 (from frans.knibbe@geodan.nl on 2015-07-21)
  19. Re: [Minutes] 2017-07-01 (from allaves@fi.upm.es on 2015-07-21)
  20. RE: [Minutes] 2017-07-01 (from Simon.Cox@csiro.au on 2015-07-21)
  21. RE: [SDWWG] CRS Issues, Issue-28 (from Simon.Cox@csiro.au on 2015-07-21)
  22. Re: [Minutes] 2017-07-01 (from frans.knibbe@geodan.nl on 2015-07-20)
  23. Re: [SDWWG] CRS Issues, Issue-28 (from frans.knibbe@geodan.nl on 2015-07-20)
  24. Re: [Minutes] 2017-07-01 (from allaves@fi.upm.es on 2015-07-20)
  25. Re: [Minutes] 2017-07-01 (from frans.knibbe@geodan.nl on 2015-07-20)
  26. Re: Use of the word 'standard' in the UCR document. (from jeremy.tandy@gmail.com on 2015-07-10)
  27. Re: [Minutes] 2017-07-01 (from allaves@fi.upm.es on 2015-07-10)
  28. Re: [Minutes] 2017-07-01 (from eparsons@google.com on 2015-07-10)
  29. Re: [Minutes] 2017-07-01 (from frans.knibbe@geodan.nl on 2015-07-09)
  30. Re: Use of the word 'standard' in the UCR document. (from frans.knibbe@geodan.nl on 2015-07-09)
  31. RE: [SDWWG] CRS Issues, Issue-28 (from reh@bgs.ac.uk on 2015-07-08)
  32. Re: [SDWWG] CRS Issues, Issue-28 (from eparsons@google.com on 2015-07-06)
  33. Re: [SDWWG] CRS Issues, Issue-28 (from Kerry.Taylor@acm.org on 2015-07-03)
  34. Re: [SDWWG] CRS Issues (from chaals@yandex-team.ru on 2015-07-02)
  35. RE: [SDWWG] CRS Issues (from L.Svensson@dnb.de on 2015-07-02)
  36. RE: [SDWWG] CRS Issues [SEC=UNCLASSIFIED] (from l.vandenbrink@geonovum.nl on 2015-07-02)
  37. Re: CRS Issues [SEC=UNCLASSIFIED] (from p.baumann@jacobs-university.de on 2015-07-02)
  38. Re: CRS Issues [SEC=UNCLASSIFIED] (from eparsons@google.com on 2015-07-02)
  39. Re: CRS Issues [SEC=UNCLASSIFIED] (from p.baumann@jacobs-university.de on 2015-07-02)
  40. Re: CRS Issues [SEC=UNCLASSIFIED] (from Kerry.Taylor@acm.org on 2015-07-02)
  41. Re: CRS Issues [SEC=UNCLASSIFIED] (from B.Bannerman@bom.gov.au on 2015-07-01)
  42. CRS Issues (from eparsons@google.com on 2015-07-01)
  43. [Minutes] 2017-07-01 (from phila@w3.org on 2015-07-01)
  44. Late regrets (was: Re: [SDWWG] SDWWG Next Meeting) (from andrea.perego@jrc.ec.europa.eu on 2015-07-01)
  45. Re: Dynamic CRS Datums. Was: UCR issue: phrasing of CRS requirement(s) (from p.baumann@jacobs-university.de on 2015-06-30)
  46. Dynamic CRS Datums. Was: UCR issue: phrasing of CRS requirement(s) (from chris.little@metoffice.gov.uk on 2015-06-30)
  47. SDWWG Next Meeting (from eparsons@google.com on 2015-06-30)
  48. Re: Issue-10 unresolved in meeting today (from eparsons@google.com on 2015-06-29)
  49. Re: Issue-10 unresolved in meeting today (from frans.knibbe@geodan.nl on 2015-06-29)
  50. Re: Issue-10 unresolved in meeting today (from eparsons@google.com on 2015-06-29)
  51. Re: Issue-10 unresolved in meeting today (from eparsons@google.com on 2015-06-29)
  52. Re: Issue-10 unresolved in meeting today (from frans.knibbe@geodan.nl on 2015-06-29)
  53. RE: Issue-10 unresolved in meeting today (from Simon.Cox@csiro.au on 2015-06-28)
  54. Fwd: Issue-10 unresolved in meeting today (from Kerry.Taylor@acm.org on 2015-06-27)
  55. RE: Use of the word 'standard' in the UCR document. (from reh@bgs.ac.uk on 2015-06-26)
  56. Re: Issue-10 unresolved in meeting today (from matthew.perry@oracle.com on 2015-06-26)
  57. Re: Issue-10 unresolved in meeting today (from andrea.perego@jrc.ec.europa.eu on 2015-06-26)
  58. Re: Use of the word 'standard' in the UCR document. (from eparsons@google.com on 2015-06-26)
  59. RE: Issue-10 unresolved in meeting today (from Simon.Cox@csiro.au on 2015-06-26)
  60. Re: Issue-10 unresolved in meeting today (from frans.knibbe@geodan.nl on 2015-06-25)
  61. Re: Use of the word 'standard' in the UCR document. (from frans.knibbe@geodan.nl on 2015-06-25)
  62. Re: Issue-10 unresolved in meeting today (from andrea.perego@jrc.ec.europa.eu on 2015-06-25)
  63. Re: Use of the word 'standard' in the UCR document. (from sserich@opengeospatial.org on 2015-06-25)
  64. Re: Use of the word 'standard' in the UCR document. (from Kerry.Taylor@acm.org on 2015-06-25)
  65. RE: Use of the word 'standard' in the UCR document. (from allaves@fi.upm.es on 2015-06-25)
  66. RE: Issue-10 unresolved in meeting today (from l.vandenbrink@geonovum.nl on 2015-06-25)
  67. Re: Issue-10 unresolved in meeting today (from frans.knibbe@geodan.nl on 2015-06-25)
  68. RE: Issue-10 unresolved in meeting today (from L.Svensson@dnb.de on 2015-06-25)
  69. Re: Issue-10 unresolved in meeting today (from portele@interactive-instruments.de on 2015-06-25)
  70. Re: Issue-10 unresolved in meeting today (from andrea.perego@jrc.ec.europa.eu on 2015-06-25)
  71. Re: Issue-10 unresolved in meeting today (from eparsons@google.com on 2015-06-25)
  72. Re: Issue-10 unresolved in meeting today (from p.baumann@jacobs-university.de on 2015-06-25)
  73. RE: Issue-10 unresolved in meeting today (from l.vandenbrink@geonovum.nl on 2015-06-25)
  74. RE: Use of the word 'standard' in the UCR document. (from l.vandenbrink@geonovum.nl on 2015-06-25)
  75. Issue-10 unresolved in meeting today (from Kerry.Taylor@acm.org on 2015-06-25)
  76. Re: Use of the word 'standard' in the UCR document. (from frans.knibbe@geodan.nl on 2015-06-24)
  77. RE: Issue-10 unresolved in meeting today (from L.Svensson@dnb.de on 2015-06-24)
  78. Re: Use of the word 'standard' in the UCR document. (from jlieberman@tumblingwalls.com on 2015-06-24)
  79. Re: Use of the word 'standard' in the UCR document. (from eparsons@google.com on 2015-06-24)
  80. Re: Use of the word 'standard' in the UCR document. (from frans.knibbe@geodan.nl on 2015-06-24)
  81. Re: Resolving UCR issues (from frans.knibbe@geodan.nl on 2015-06-24)
  82. Re: Use of the word 'standard' in the UCR document. (from eparsons@google.com on 2015-06-24)
  83. Use of the word 'standard' in the UCR document. (from frans.knibbe@geodan.nl on 2015-06-24)
  84. Re: Resolving UCR issues (from eparsons@google.com on 2015-06-24)
  85. Re: Resolving UCR issues (from frans.knibbe@geodan.nl on 2015-06-24)
  86. Re: [SDWWG] Next meeting Wed 24 June (from frans.knibbe@geodan.nl on 2015-06-24)
  87. Re: [SDWWG] Next meeting Wed 24 June (from chaals@yandex-team.ru on 2015-06-24)
  88. Re: [SDWWG] Next meeting Wed 24 June (from Philippe.Thiran@sirris.be on 2015-06-24)
  89. Re: [SDWWG] Next meeting Wed 24 June (from chaals@yandex-team.ru on 2015-06-24)
  90. Re: [SDWWG] Next meeting Wed 24 June (from jeremy.tandy@gmail.com on 2015-06-23)
  91. Re: [SDWWG] Next meeting Wed 24 June (from p.barnaghi@surrey.ac.uk on 2015-06-23)
  92. will put this ISSUE-10 re CRS on the agenda for tomorrow. (from kerry.taylor@acm.org on 2015-06-23)
  93. [SDWWG] Next meeting Wed 24 June (from kerry.taylor@acm.org on 2015-06-23)
  94. Re: Resolving UCR issues (from phila@w3.org on 2015-06-23)
  95. Re: Resolving UCR issues (from frans.knibbe@geodan.nl on 2015-06-23)
  96. Re: Resolving UCR issues (from allaves@fi.upm.es on 2015-06-23)
  97. Re: Resolving UCR issues (from frans.knibbe@geodan.nl on 2015-06-22)
  98. Re: Frozen copy? (from frans.knibbe@geodan.nl on 2015-06-10)
  99. Re: UCR issue: phrasing of CRS requirement(s) [SEC=UNCLASSIFIED] (from B.Bannerman@bom.gov.au on 2015-06-01)
  100. Re: UCR issue: phrasing of CRS requirement(s) [SEC=UNCLASSIFIED] (from p.baumann@jacobs-university.de on 2015-06-01)
  101. Re: UCR issue: phrasing of CRS requirement(s) [SEC=UNCLASSIFIED] (from B.Bannerman@bom.gov.au on 2015-05-31)
  102. Re: UCR issue: phrasing of CRS requirement(s) (from p.baumann@jacobs-university.de on 2015-05-29)
  103. Re: UCR issue: phrasing of CRS requirement(s) (from frans.knibbe@geodan.nl on 2015-05-29)
  104. Re: UCR issue: phrasing of CRS requirement(s) (from eparsons@google.com on 2015-05-29)
  105. Re: UCR issue: phrasing of CRS requirement(s) (from p.baumann@jacobs-university.de on 2015-05-29)
  106. Re: UCR issue: phrasing of CRS requirement(s) (from frans.knibbe@geodan.nl on 2015-05-29)
  107. Re: UCR issue: phrasing of CRS requirement(s) (from eparsons@google.com on 2015-05-27)
  108. Re: UCR issue: phrasing of CRS requirement(s) (from frans.knibbe@geodan.nl on 2015-05-27)
  109. Re: UCR issue: phrasing of CRS requirement(s) (from janowicz@ucsb.edu on 2015-05-26)
  110. Re: UCR issue: phrasing of CRS requirement(s) (from jlieberman@tumblingwalls.com on 2015-05-18)
  111. RE: UCR issue: phrasing of CRS requirement(s) (from Simon.Cox@csiro.au on 2015-05-18)
  112. RE: UCR issue: phrasing of CRS requirement(s) (from Kerry.Taylor@csiro.au on 2015-05-18)
  113. RE: UCR issue: phrasing of CRS requirement(s) (from L.Svensson@dnb.de on 2015-05-18)
  114. Re: UCR issue: phrasing of CRS requirement(s) (from eparsons@google.com on 2015-05-18)
  115. Re: UCR issue: phrasing of CRS requirement(s) (from janowicz@ucsb.edu on 2015-05-15)
  116. Re: UCR issue: phrasing of CRS requirement(s) (from jlieberman@tumblingwalls.com on 2015-05-15)
  117. Re: UCR issue: phrasing of CRS requirement(s) (from p.baumann@jacobs-university.de on 2015-05-15)
  118. Re: UCR issue: phrasing of CRS requirement(s) (from matthew.perry@oracle.com on 2015-05-15)
  119. Re: UCR issue: phrasing of CRS requirement(s) (from p.baumann@jacobs-university.de on 2015-05-15)
  120. Re: UCR issue: phrasing of CRS requirement(s) (from matthew.perry@oracle.com on 2015-05-15)
  121. Re: UCR issue: phrasing of CRS requirement(s) (from jlieberman@tumblingwalls.com on 2015-05-15)
  122. Re: UCR issue: phrasing of CRS requirement(s) (from ashok.malhotra@oracle.com on 2015-05-15)
  123. Re: UCR issue: phrasing of CRS requirement(s) (from p.baumann@jacobs-university.de on 2015-05-15)
  124. RE: UCR issue: phrasing of CRS requirement(s) (from l.vandenbrink@geonovum.nl on 2015-05-15)
  125. Re: UCR issue: phrasing of CRS requirement(s) (from p.baumann@jacobs-university.de on 2015-05-15)
  126. RE: UCR issue: phrasing of CRS requirement(s) (from l.vandenbrink@geonovum.nl on 2015-05-15)
  127. UCR issue: phrasing of CRS requirement(s) (from frans.knibbe@geodan.nl on 2015-05-13)

Related notes:

Proposal:

Replace current CRS requirement to:

"There should be a standard for publishing data about coordinate reference systems (CRS). It should be applicable to any 2D or 3D CRS, not only geographical reference systems. CRS descriptions should be referencable by HTTP URIs."

Also add a separate requirement for having a default CRS.

Frans Knibbe, 27 May 2015, 12:49:36

The requirement for a default CRS has been added to the UCR document: http://w3c.github.io/sdw/UseCases/SDWUseCasesAndRequirements.html#DefaultCRS

Frans Knibbe, 8 Jun 2015, 10:21:19

Set to open 2016-06-24

Phil Archer, 24 Jun 2015, 14:00:56

discussed at length at meeting 25 June 2015 but not resolved

Kerry Taylor, 24 Jun 2015, 14:07:44

We will attempt to make in decision in the meeting of 2015-07-01.

A proposal for rephrasing of the CRS Definition requirement:
"There should be a recommendend way of referencing a CRS with a HTTP URI, and to get useful information about the CRS when that URI is dereferenced."

Furthermore,

Frans Knibbe, 30 Jun 2015, 09:15:41

(Previous note was incomplete and had an error)

We will attempt to make in decision in the meeting of 2015-07-01.

A proposal for rephrasing of the CRS Definition requirement:
"There should be a recommended way of referencing a CRS with a HTTP URI, and to get useful information about the CRS when that URI is dereferenced."

Furthermore, ISSUE-29 (https://www.w3.org/2015/spatial/track/issues/29) has been raised to cover the need for linking a CRS definition to a vector geometry.

Frans Knibbe, 30 Jun 2015, 09:32:18

Accepted proposal in meeting of 2015-07-01: change CRS Definition requirement to "There should be a way of referencing a CRS with a HTTP URI, and to get useful information about the CRS when that URI is dereferenced."

Frans Knibbe, 20 Jul 2015, 12:42:35

Display change log ATOM feed


Ed Parsons <eparsons@google.com>, Kerry Taylor <kerry.taylor@anu.edu.au>, Chairs, Fran├žois Daoust <fd@w3.org>, Staff Contact
Tracker: documentation, (configuration for this group), originally developed by Dean Jackson, is developed and maintained by the Systems Team <w3t-sys@w3.org>.
$Id: index.php,v 1.325 2014-09-10 21:42:02 ted Exp $