do not use publication date into the future
Nobody has claimed this yet.
Assessment
- Difficulty
- 1/5
- Estimated time
- Under an hour
- Newbie friendliness
- 65/100
- Issue type
- Bug
- Clarity
- Mostly clear
- Activity status
- Quiet
- Domain
- documentation
Research direction
Open sources/mod-spec-user-guide/document.adoc and inspect the :published-date: metadata alongside the received and issued dates. Determine which recorded date should be used instead of the future value, update the metadata, and verify that the generated document shows a non-future publication date.
Written by the indexing model from the issue text.
Description
FYI, in https://raw.githubusercontent.com/opengeospatial/ogc-modspec/refs/heads/main/sources/mod-spec-user-guide/document.adoc, the publication date is set as :published-date: 2029-03-30. Should this date be closer to the received or issued date (or at least not into the future)?
cc @anitagraser
- Dominant language
- HTML
- Stars
- 1
- Forks
- 5
- PR merge metrics
- No merged PRs in 30d
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from opengeospatial/ogc-modspec
-
Difficulty 2/5 1-3 hours Newbie friendliness 45/100
opengeospatial/ogc-modspec#98 · 4 comments ·
-
Difficulty 4/5 3-5 days Newbie friendliness 25/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 45/100
opengeospatial/ogc-modspec#96 · 1 comment ·
-
Part 3: REQ008 Openfixed Part 3
Difficulty 5/5 Over a week Newbie friendliness 25/100
opengeospatial/ogc-modspec#93 · 2 comments ·
-
fixed Part 3
Difficulty 4/5 3-5 days Newbie friendliness 35/100
opengeospatial/ogc-modspec#92 · 6 comments ·
All issues in opengeospatial/ogc-modspec
Similar issues
-
user-reported
Difficulty 2/5 1-3 hours Newbie friendliness 85/100
Kong/developer.konghq.com#7316 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
HarperFast/skills#96 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
infinispan/infinispan#18150 ·
-
bug triage:deciding
Difficulty 1/5 Under an hour Newbie friendliness 88/100
open-telemetry/otel-arrow#4132 ·
-
Ecosystem: ClawMetry — the Qwen Code reader is now free and open source (follow-up to #9294 / #9338) Opencategory/integration priority/P3 scope/documentation status/ready-for-human type/feature-request
Difficulty 1/5 Under an hour Newbie friendliness 84/100