-
Notifications
You must be signed in to change notification settings - Fork 5
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Styles: Changes to a style with multiple occurrences in an API #37
Comments
I can imagine a situation whereby different encodings of a portrayal specification are developed by different people at different points in time. This would require the encodings to be separate resources, perhaps associated through some declared relationship (ebRIM has association objects and SKOS has |
@ghobona - That would be a separate issue. In the Styles API, the Style is the resource, independent how many encodings are available. One can update specific encodings using PUT, but that should be done in sync since it is the same style. If different encodings are considered separate styles by a publisher and are managed separately, these are separate styles with separate URIs. This issue is about having a "night" style at, for example, |
My view on this is that That's the way CubeWerx has implemented it anyways. I have the DELETE operation enabled at our style endpoints at "https://test.cubewerx.com/cubewerx/cubeserv/demo/ogcapi/Daraa". Feel free to experiment with this behaviour. If you do so, please let me know so that I can rebuild the nominal state of things once you're done. |
@pomakis - We have not implemented it that way, but it does make sense to me, so I will update our implementation. Our implementation currently derives the style |
@ghobona in our implementation, the server automatically generates all encodings from a single style, so the different encodings are always in sync. |
I propose adding something like the following statement to the "OGC API - Styles" specification:
|
@cportele We discussed this Issue earlier today during the 'short stand up' session. The participants liked the statement proposed by @pomakis in https://github.com/opengeospatial/ogcapi-code-sprint-2021-05/issues/18#issuecomment-849843553. Let us know during the Daily Brief Back today if you would like to revise the statement or discuss it further. |
@ghobona - I have no problem with the statement per se, but to include something normative in the spec, it needs more work, because the spec does not explicitly have normative statements about |
Meeting 2021-11-02: The behaviour should be server-dependent. Servers may prohibit update or replace operations on derived styles (derived resources) in general. This is related, but somewhat different from the case discussed in #40, which is about derived representations of the same resource. |
Question from the Sprint kickoff:
If a style
foo
is used in several places in an API (that is, there are several resources where the path includes/styles/foo
somewhere), does a PUT/DELETE on that style affect all occurrences of the style or only the one on which the operation is executed? In other words, is it only one resource with multiple URIs or are these separate resources?The text was updated successfully, but these errors were encountered: