You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
To get "actionable" endpoints, we need the full path and we should do this to standardize across the JSON docs. Which mostly means that we need to pass the source URL to the parsers.
The text was updated successfully, but these errors were encountered:
Magic string overlapping fun not with the ID and this is not a step forward in the world. It introduces a kind of ambiguity that is not in the FTP that it is trying to be.
The endpoints should get dumped in the right location, JSON-wise, as well - if has_metadata, then pull those to the metadata element vs the dataset endpoints. catalogRef endpoints remain under the servce_description endpoints.
To get "actionable" endpoints, we need the full path and we should do this to standardize across the JSON docs. Which mostly means that we need to pass the source URL to the parsers.
The text was updated successfully, but these errors were encountered: