Skip to content

PR #564 finetuning of back-end "availability" terminology#565

Merged
m-mohr merged 1 commit intoOpen-EO:m-mohr-patch-1from
soxofaan:clarify-fed-ext-fields
Jul 1, 2025
Merged

PR #564 finetuning of back-end "availability" terminology#565
m-mohr merged 1 commit intoOpen-EO:m-mohr-patch-1from
soxofaan:clarify-fed-ext-fields

Conversation

@soxofaan
Copy link
Member

@soxofaan soxofaan commented Jun 30, 2025

This is an auxiliary PR for #564 . To be merged or cherry-picked from

Main goal is to eliminate/reduce "permanent"/"temporary" terminology which might make cause a mismatch in expectations as I tried to argue in #564 (comment)

contents:

  • explicitly mention properties federation:backends and federation:missing in the descriptions
  • eliminate the word "permanently" (used once for federation:backends), which was redundant in my opinion
  • put list of resources in bold to (hopefully) make it more clear that federation:backends is for individual resources and federation:missing is for compiled listings
  • reduce usage of "temporary" and replace it with a neutral "not available". I kept it when used in combination "temporarily or unintentionally" where it has value.
  • small typo fix of "the a combination"

@soxofaan soxofaan force-pushed the clarify-fed-ext-fields branch from 04fd3cf to 8055ab4 Compare June 30, 2025 16:33
@m-mohr m-mohr self-requested a review June 30, 2025 18:40
@m-mohr
Copy link
Member

m-mohr commented Jul 1, 2025

Thanks, that sounds good.

@m-mohr m-mohr merged commit 6e431e9 into Open-EO:m-mohr-patch-1 Jul 1, 2025
1 check passed
@soxofaan soxofaan deleted the clarify-fed-ext-fields branch July 1, 2025 09:13
@m-mohr m-mohr linked an issue Jul 1, 2025 that may be closed by this pull request
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Clarifications for the Federation extension

2 participants