-
Notifications
You must be signed in to change notification settings - Fork 7
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
add a "capabilities" section #217
Comments
duglin
added a commit
to duglin/xreg-spec
that referenced
this issue
Dec 23, 2024
- clarify errors for bad paths and methods - Remove "origin" - add `/capabilities` API and "capabilities" Registry attr - requires `?inline=capabilities` reads, just presence on writes(like model) Fixes xregistry#199 Fixes xregistry#216 Fixes xregistry#217 Signed-off-by: Doug Davis <[email protected]>
Merged
duglin
added a commit
to duglin/xreg-spec
that referenced
this issue
Dec 28, 2024
- clarify errors for bad paths and methods - Remove "origin" - add `/capabilities` API and "capabilities" Registry attr - requires `?inline=capabilities` reads, just presence on writes(like model) - remove "schemas" from model, moved into "capabilities" - add 'xid'. Change xref to start with / - add "labels" to model schema : Registry, Groups and Resources - add a "compatiblewith" well-known label Fixes xregistry#199 Fixes xregistry#216 Fixes xregistry#217 Fixes xregistry#213 Fixes xregistry#210 Fixes xregistry#211 Signed-off-by: Doug Davis <[email protected]>
duglin
added a commit
to duglin/xreg-spec
that referenced
this issue
Jan 1, 2025
- clarify errors for bad paths and methods - Remove "origin" - add `/capabilities` API and "capabilities" Registry attr - requires `?inline=capabilities` reads, just presence on writes(like model) - remove "schemas" from model, moved into "capabilities" - add 'xid'. Change xref to start with / - add "labels" to model schema : Registry, Groups and Resources - add a "compatiblewith" well-known label - add support for `relation` type of URLs - add text about how to deal with sending incomplete results - error unless you can be tricky via something like pagination spec Fixes xregistry#199 Fixes xregistry#216 Fixes xregistry#217 Fixes xregistry#213 Fixes xregistry#210 Fixes xregistry#211 Fixes xregistry#209 Fixed xregistry#187 Signed-off-by: Doug Davis <[email protected]>
duglin
added a commit
to duglin/xreg-spec
that referenced
this issue
Jan 1, 2025
- clarify errors for bad paths and methods - Remove "origin" - add `/capabilities` API and "capabilities" Registry attr - requires `?inline=capabilities` reads, just presence on writes(like model) - remove "schemas" from model, moved into "capabilities" - add 'xid'. Change xref to start with / - add "labels" to model schema : Registry, Groups and Resources - add a "compatiblewith" well-known label - add support for `relation` type of URLs - add text about how to deal with sending incomplete results - error unless you can be tricky via something like pagination spec Fixes xregistry#199 Fixes xregistry#216 Fixes xregistry#217 Fixes xregistry#213 Fixes xregistry#210 Fixes xregistry#211 Fixes xregistry#209 Fixes xregistry#187 Signed-off-by: Doug Davis <[email protected]>
duglin
added a commit
to duglin/xreg-spec
that referenced
this issue
Jan 4, 2025
- clarify errors for bad paths and methods - Remove "origin" - add `/capabilities` API and "capabilities" Registry attr - requires `?inline=capabilities` reads, just presence on writes(like model) - remove "schemas" from model, moved into "capabilities" - add 'xid'. Change xref to start with / - add "labels" to model schema : Registry, Groups and Resources - add a "compatiblewith" well-known label - add support for `relation` type of URLs - add text about how to deal with sending incomplete results - error unless you can be tricky via something like pagination spec - allow ?export, ?inline, ?filter on all APIs to control responses - explain that "generated" errors != must send back to client - e.g. security Fixes xregistry#199 Fixes xregistry#216 Fixes xregistry#217 Fixes xregistry#213 Fixes xregistry#210 Fixes xregistry#211 Fixes xregistry#209 Fixes xregistry#187 fixes xregistry#200 Signed-off-by: Doug Davis <[email protected]>
duglin
added a commit
to duglin/xreg-spec
that referenced
this issue
Jan 4, 2025
- clarify errors for bad paths and methods - Remove "origin" - add `/capabilities` API and "capabilities" Registry attr - requires `?inline=capabilities` reads, just presence on writes(like model) - remove "schemas" from model, moved into "capabilities" - add 'xid'. Change xref to start with / - add "labels" to model schema : Registry, Groups and Resources - add a "compatiblewith" well-known label - add support for `relation` type of URLs - add text about how to deal with sending incomplete results - error unless you can be tricky via something like pagination spec - allow ?export, ?inline, ?filter on all APIs to control responses - explain that "generated" errors != must send back to client - e.g. security - use highest alphabetical versionid (case insensitive) when all versions have the same "createdat" value. Remove requirement for ?setdefaultversionid Fixes xregistry#199 Fixes xregistry#216 Fixes xregistry#217 Fixes xregistry#213 Fixes xregistry#210 Fixes xregistry#211 Fixes xregistry#209 Fixes xregistry#187 Fixes xregistry#200 Fixes xregistry#202 Signed-off-by: Doug Davis <[email protected]>
duglin
added a commit
to duglin/xreg-spec
that referenced
this issue
Jan 5, 2025
- clarify errors for bad paths and methods - Remove "origin" - add `/capabilities` API and "capabilities" Registry attr - requires `?inline=capabilities` reads, just presence on writes(like model) - remove "schemas" from model, moved into "capabilities" - add 'xid'. Change xref to start with / - add "labels" to model schema : Registry, Groups and Resources - add a "compatiblewith" well-known label - add support for `relation` type of URLs - add text about how to deal with sending incomplete results - error unless you can be tricky via something like pagination spec - allow ?export, ?inline, ?filter on all APIs to control responses - explain that "generated" errors != must send back to client - e.g. security - use highest alphabetical versionid (case insensitive) when all versions have the same "createdat" value. Remove requirement for ?setdefaultversionid - `DELETE RESOURCES` must put `epoch` under `meta` if present Fixes xregistry#199 Fixes xregistry#216 Fixes xregistry#217 Fixes xregistry#213 Fixes xregistry#210 Fixes xregistry#211 Fixes xregistry#209 Fixes xregistry#187 Fixes xregistry#200 Fixes xregistry#202 Fixes xregistry#205 Signed-off-by: Doug Davis <[email protected]>
duglin
added a commit
to duglin/xreg-spec
that referenced
this issue
Jan 5, 2025
- clarify errors for bad paths and methods - Remove "origin" - add `/capabilities` API and "capabilities" Registry attr - requires `?inline=capabilities` reads, just presence on writes(like model) - remove "schemas" from model, moved into "capabilities" - add 'xid'. Change xref to start with / - add "labels" to model schema : Registry, Groups and Resources - add a "compatiblewith" well-known label - add support for `relation` type of URLs - add text about how to deal with sending incomplete results - error unless you can be tricky via something like pagination spec - allow ?export, ?inline, ?filter on all APIs to control responses - explain that "generated" errors != must send back to client - e.g. security - use highest alphabetical versionid (case insensitive) when all versions have the same "createdat" value. Remove requirement for ?setdefaultversionid - `DELETE RESOURCES` must put `epoch` under `meta` if present - Primer: explain why GROUPS and RESOURCES have attribute name restrictions Fixes xregistry#199 Fixes xregistry#216 Fixes xregistry#217 Fixes xregistry#213 Fixes xregistry#210 Fixes xregistry#211 Fixes xregistry#209 Fixes xregistry#187 Fixes xregistry#200 Fixes xregistry#202 Fixes xregistry#205 Fixes xregistry#207 Signed-off-by: Doug Davis <[email protected]>
duglin
added a commit
to duglin/xreg-spec
that referenced
this issue
Jan 5, 2025
- clarify errors for bad paths and methods - Remove "origin" - add `/capabilities` API and "capabilities" Registry attr - requires `?inline=capabilities` reads, just presence on writes(like model) - remove "schemas" from model, moved into "capabilities" - add 'xid'. Change xref to start with / - add "labels" to model schema : Registry, Groups and Resources - add a "compatiblewith" well-known label - add support for `relation` type of URLs - add text about how to deal with sending incomplete results - error unless you can be tricky via something like pagination spec - allow ?export, ?inline, ?filter on all APIs to control responses - explain that "generated" errors != must send back to client - e.g. security - use highest alphabetical versionid (case insensitive) when all versions have the same "createdat" value. Remove requirement for ?setdefaultversionid - `DELETE RESOURCES` must put `epoch` under `meta` if present - Primer: explain why GROUPS and RESOURCES have attribute name restrictions - Primer: encourage domain/company prefix/suffixed on Groups (and Resources) Fixes xregistry#199 Fixes xregistry#216 Fixes xregistry#217 Fixes xregistry#213 Fixes xregistry#210 Fixes xregistry#211 Fixes xregistry#209 Fixes xregistry#187 Fixes xregistry#200 Fixes xregistry#202 Fixes xregistry#205 Fixes xregistry#207 Fixes xregistry#214 Signed-off-by: Doug Davis <[email protected]>
duglin
added a commit
to duglin/xreg-spec
that referenced
this issue
Jan 5, 2025
- clarify errors for bad paths and methods - Remove "origin" - add `/capabilities` API and "capabilities" Registry attr - requires `?inline=capabilities` reads, just presence on writes(like model) - remove "schemas" from model, moved into "capabilities" - add 'xid'. Change xref to start with / - add "labels" to model schema : Registry, Groups and Resources - add a "compatiblewith" well-known label - add support for `relation` type of URLs - add text about how to deal with sending incomplete results - error unless you can be tricky via something like pagination spec - allow ?export, ?inline, ?filter on all APIs to control responses - explain that "generated" errors != must send back to client - e.g. security - use highest alphabetical versionid (case insensitive) when all versions have the same "createdat" value. Remove requirement for ?setdefaultversionid - `DELETE RESOURCES` must put `epoch` under `meta` if present - Primer: explain why GROUPS and RESOURCES have attribute name restrictions - Primer: encourage domain/company prefix/suffixed on Groups (and Resources) - Add `capability.enforcecompatibility` so servers can indicate whether they'll enforce the `compatibility` attribute on the owning Resource Fixes xregistry#199 Fixes xregistry#216 Fixes xregistry#217 Fixes xregistry#213 Fixes xregistry#210 Fixes xregistry#211 Fixes xregistry#209 Fixes xregistry#187 Fixes xregistry#200 Fixes xregistry#202 Fixes xregistry#205 Fixes xregistry#207 Fixes xregistry#214 Fixes xregistry#203 Signed-off-by: Doug Davis <[email protected]>
duglin
added a commit
to duglin/xreg-spec
that referenced
this issue
Jan 6, 2025
- clarify errors for bad paths and methods - Remove "origin" - add `/capabilities` API and "capabilities" Registry attr - requires `?inline=capabilities` reads, just presence on writes(like model) - remove "schemas" from model, moved into "capabilities" - add 'xid'. Change xref to start with / - add "labels" to model schema : Registry, Groups and Resources - add a "compatiblewith" well-known label - add support for `relation` type of URLs - add text about how to deal with sending incomplete results - error unless you can be tricky via something like pagination spec - allow ?export, ?inline, ?filter on all APIs to control responses - explain that "generated" errors != must send back to client - e.g. security - use highest alphabetical versionid (case insensitive) when all versions have the same "createdat" value. Remove requirement for ?setdefaultversionid - `DELETE RESOURCES` must put `epoch` under `meta` if present - Primer: explain why GROUPS and RESOURCES have attribute name restrictions - Primer: encourage domain/company prefix/suffixed on Groups (and Resources) - Add `capability.enforcecompatibility` so servers can indicate whether they'll enforce the `compatibility` attribute on the owning Resource - Clarify rules for updating Resources when dealing with 'xref'. - presence of any attribute on a 'write' to an xref'd resource is an error - xref->normal: - epoch = max(oldEpoch, targetResourceEpoch)+1 - createdat = oldCreatedAt - modifiedat = now Fixes xregistry#199 Fixes xregistry#216 Fixes xregistry#217 Fixes xregistry#213 Fixes xregistry#210 Fixes xregistry#211 Fixes xregistry#209 Fixes xregistry#187 Fixes xregistry#200 Fixes xregistry#202 Fixes xregistry#205 Fixes xregistry#207 Fixes xregistry#214 Fixes xregistry#203 Fixes xregistry#204 Signed-off-by: Doug Davis <[email protected]>
duglin
added a commit
to duglin/xreg-spec
that referenced
this issue
Jan 6, 2025
- clarify errors for bad paths and methods - Remove "origin" - add `/capabilities` API and "capabilities" Registry attr - requires `?inline=capabilities` reads, just presence on writes(like model) - remove "schemas" from model, moved into "capabilities" - add 'xid'. Change xref to start with / - add "labels" to model schema : Registry, Groups and Resources - add a "compatiblewith" well-known label - add support for `relation` type of URLs - add text about how to deal with sending incomplete results - error unless you can be tricky via something like pagination spec - allow ?export, ?inline, ?filter on all APIs to control responses - explain that "generated" errors != must send back to client - e.g. security - use highest alphabetical versionid (case insensitive) when all versions have the same "createdat" value. Remove requirement for ?setdefaultversionid - `DELETE RESOURCES` must put `epoch` under `meta` if present - Primer: explain why GROUPS and RESOURCES have attribute name restrictions - Primer: encourage domain/company prefix/suffixed on Groups (and Resources) - Add `capability.enforcecompatibility` so servers can indicate whether they'll enforce the `compatibility` attribute on the owning Resource - Clarify rules for updating Resources when dealing with 'xref'. - presence of any attribute on a 'write' to an xref'd resource is an error - xref->normal: - epoch = max(oldEpoch, targetResourceEpoch)+1 - createdat = oldCreatedAt - modifiedat = now Fixes xregistry#199 Fixes xregistry#216 Fixes xregistry#217 Fixes xregistry#213 Fixes xregistry#210 Fixes xregistry#211 Fixes xregistry#209 Fixes xregistry#187 Fixes xregistry#200 Fixes xregistry#202 Fixes xregistry#205 Fixes xregistry#207 Fixes xregistry#214 Fixes xregistry#203 Fixes xregistry#204 Signed-off-by: Doug Davis <[email protected]>
duglin
added a commit
to duglin/xreg-spec
that referenced
this issue
Jan 7, 2025
- clarify errors for bad paths and methods - Remove "origin" - add `/capabilities` API and "capabilities" Registry attr - requires `?inline=capabilities` reads, just presence on writes(like model) - remove "schemas" from model, moved into "capabilities" - add 'xid'. Change xref to start with / - add "labels" to model schema : Registry, Groups and Resources - add a "compatiblewith" well-known label - add support for `relation` type of URLs - add text about how to deal with sending incomplete results - error unless you can be tricky via something like pagination spec - allow ?export, ?inline, ?filter on all APIs to control responses - explain that "generated" errors != must send back to client - e.g. security - use highest alphabetical versionid (case insensitive) when all versions have the same "createdat" value. Remove requirement for ?setdefaultversionid - `DELETE RESOURCES` must put `epoch` under `meta` if present - Primer: explain why GROUPS and RESOURCES have attribute name restrictions - Primer: encourage domain/company prefix/suffixed on Groups (and Resources) - Add `capability.enforcecompatibility` so servers can indicate whether they'll enforce the `compatibility` attribute on the owning Resource - Clarify rules for updating Resources when dealing with 'xref'. - presence of any attribute on a 'write' to an xref'd resource is an error - xref->normal: - epoch = max(oldEpoch, targetResourceEpoch)+1 - createdat = oldCreatedAt - modifiedat = now Fixes xregistry#199 Fixes xregistry#216 Fixes xregistry#217 Fixes xregistry#213 Fixes xregistry#210 Fixes xregistry#211 Fixes xregistry#209 Fixes xregistry#187 Fixes xregistry#200 Fixes xregistry#202 Fixes xregistry#205 Fixes xregistry#207 Fixes xregistry#214 Fixes xregistry#203 Fixes xregistry#204 Signed-off-by: Doug Davis <[email protected]>
duglin
added a commit
to duglin/xreg-spec
that referenced
this issue
Jan 8, 2025
- clarify errors for bad paths and methods - Remove "origin" - add `/capabilities` API and "capabilities" Registry attr - requires `?inline=capabilities` reads, just presence on writes(like model) - remove "schemas" from model, moved into "capabilities" - add 'xid'. Change xref to start with / - add "labels" to model schema : Registry, Groups and Resources - add a "compatiblewith" well-known label - add support for `relation` type of URLs - add text about how to deal with sending incomplete results - error unless you can be tricky via something like pagination spec - allow ?export, ?inline, ?filter on all APIs to control responses - explain that "generated" errors != must send back to client - e.g. security - use highest alphabetical versionid (case insensitive) when all versions have the same "createdat" value. Remove requirement for ?setdefaultversionid - `DELETE RESOURCES` must put `epoch` under `meta` if present - Primer: explain why GROUPS and RESOURCES have attribute name restrictions - Primer: encourage domain/company prefix/suffixed on Groups (and Resources) - Add `capability.enforcecompatibility` so servers can indicate whether they'll enforce the `compatibility` attribute on the owning Resource - Clarify rules for updating Resources when dealing with 'xref'. - presence of any attribute on a 'write' to an xref'd resource is an error - xref->normal: - epoch = max(oldEpoch, targetResourceEpoch)+1 - createdat = oldCreatedAt - modifiedat = now - Updating a Version's `createdat` CAN make it the latest/default Fixes xregistry#199 Fixes xregistry#216 Fixes xregistry#217 Fixes xregistry#213 Fixes xregistry#210 Fixes xregistry#211 Fixes xregistry#209 Fixes xregistry#187 Fixes xregistry#200 Fixes xregistry#202 Fixes xregistry#205 Fixes xregistry#207 Fixes xregistry#214 Fixes xregistry#203 Fixes xregistry#204 Fixes xregistry#206 Signed-off-by: Doug Davis <[email protected]>
duglin
added a commit
to duglin/xreg-spec
that referenced
this issue
Jan 8, 2025
- clarify errors for bad paths and methods - Remove "origin" - add `/capabilities` API and "capabilities" Registry attr - requires `?inline=capabilities` reads, just presence on writes(like model) - remove "schemas" from model, moved into "capabilities" - add 'xid'. Change xref to start with / - add "labels" to model schema : Registry, Groups and Resources - add a "compatiblewith" well-known label - add support for `relation` type of URLs - add text about how to deal with sending incomplete results - error unless you can be tricky via something like pagination spec - allow ?export, ?inline, ?filter on all APIs to control responses - explain that "generated" errors != must send back to client - e.g. security - use highest alphabetical versionid (case insensitive) when all versions have the same "createdat" value. Remove requirement for ?setdefaultversionid - `DELETE RESOURCES` must put `epoch` under `meta` if present - Primer: explain why GROUPS and RESOURCES have attribute name restrictions - Primer: encourage domain/company prefix/suffixed on Groups (and Resources) - Add `capability.enforcecompatibility` so servers can indicate whether they'll enforce the `compatibility` attribute on the owning Resource - Clarify rules for updating Resources when dealing with 'xref'. - presence of any attribute on a 'write' to an xref'd resource is an error - xref->normal: - epoch = max(oldEpoch, targetResourceEpoch)+1 - createdat = oldCreatedAt - modifiedat = now - Updating a Version's `createdat` CAN make it the latest/default - add support for "shortself" - add "@" as a valid char for IDs Fixes xregistry#199 Fixes xregistry#216 Fixes xregistry#217 Fixes xregistry#213 Fixes xregistry#210 Fixes xregistry#211 Fixes xregistry#209 Fixes xregistry#187 Fixes xregistry#200 Fixes xregistry#202 Fixes xregistry#205 Fixes xregistry#207 Fixes xregistry#214 Fixes xregistry#203 Fixes xregistry#204 Fixes xregistry#206 Fixes xregistry#212 Signed-off-by: Doug Davis <[email protected]>
duglin
added a commit
to duglin/xreg-spec
that referenced
this issue
Jan 9, 2025
- clarify errors for bad paths and methods - Remove "origin" - add `/capabilities` API and "capabilities" Registry attr - requires `?inline=capabilities` reads, just presence on writes(like model) - remove "schemas" from model, moved into "capabilities" - add 'xid'. Change xref to start with / - add "labels" to model schema : Registry, Groups and Resources - add a "compatiblewith" well-known label - add support for `relation` type of URLs - add text about how to deal with sending incomplete results - error unless you can be tricky via something like pagination spec - allow ?export, ?inline, ?filter on all APIs to control responses - explain that "generated" errors != must send back to client - e.g. security - use highest alphabetical versionid (case insensitive) when all versions have the same "createdat" value. Remove requirement for ?setdefaultversionid - `DELETE RESOURCES` must put `epoch` under `meta` if present - Primer: explain why GROUPS and RESOURCES have attribute name restrictions - Primer: encourage domain/company prefix/suffixed on Groups (and Resources) - Add `capability.enforcecompatibility` so servers can indicate whether they'll enforce the `compatibility` attribute on the owning Resource - Clarify rules for updating Resources when dealing with 'xref'. - presence of any attribute on a 'write' to an xref'd resource is an error - xref->normal: - epoch = max(oldEpoch, targetResourceEpoch)+1 - createdat = oldCreatedAt - modifiedat = now - Updating a Version's `createdat` CAN make it the latest/default - add support for "shortself" - add "@" as a valid char for IDs Fixes xregistry#199 Fixes xregistry#216 Fixes xregistry#217 Fixes xregistry#213 Fixes xregistry#210 Fixes xregistry#211 Fixes xregistry#209 Fixes xregistry#187 Fixes xregistry#200 Fixes xregistry#202 Fixes xregistry#205 Fixes xregistry#207 Fixes xregistry#214 Fixes xregistry#203 Fixes xregistry#204 Fixes xregistry#206 Fixes xregistry#212 Signed-off-by: Doug Davis <[email protected]>
duglin
added a commit
to duglin/xreg-spec
that referenced
this issue
Jan 9, 2025
- clarify errors for bad paths and methods - Remove "origin" - add `/capabilities` API and "capabilities" Registry attr - requires `?inline=capabilities` reads, just presence on writes(like model) - remove "schemas" from model, moved into "capabilities" - add 'xid'. Change xref to start with / - add "labels" to model schema : Registry, Groups and Resources - add a "compatiblewith" well-known label - add support for `relation` type of URLs - add text about how to deal with sending incomplete results - error unless you can be tricky via something like pagination spec - allow ?export, ?inline, ?filter on all APIs to control responses - explain that "generated" errors != must send back to client - e.g. security - use highest alphabetical versionid (case insensitive) when all versions have the same "createdat" value. Remove requirement for ?setdefaultversionid - `DELETE RESOURCES` must put `epoch` under `meta` if present - Primer: explain why GROUPS and RESOURCES have attribute name restrictions - Primer: encourage domain/company prefix/suffixed on Groups (and Resources) - Add `capability.enforcecompatibility` so servers can indicate whether they'll enforce the `compatibility` attribute on the owning Resource - Clarify rules for updating Resources when dealing with 'xref'. - presence of any attribute on a 'write' to an xref'd resource is an error - xref->normal: - epoch = max(oldEpoch, targetResourceEpoch)+1 - createdat = oldCreatedAt - modifiedat = now - Updating a Version's `createdat` CAN make it the latest/default - add support for "shortself" - add "@" as a valid char for IDs Fixes xregistry#199 Fixes xregistry#216 Fixes xregistry#217 Fixes xregistry#213 Fixes xregistry#210 Fixes xregistry#211 Fixes xregistry#209 Fixes xregistry#187 Fixes xregistry#200 Fixes xregistry#202 Fixes xregistry#205 Fixes xregistry#207 Fixes xregistry#214 Fixes xregistry#203 Fixes xregistry#204 Fixes xregistry#206 Fixes xregistry#212 Signed-off-by: Doug Davis <[email protected]>
duglin
added a commit
to duglin/xreg-spec
that referenced
this issue
Jan 9, 2025
- clarify errors for bad paths and methods - Remove "origin" - add `/capabilities` API and "capabilities" Registry attr - requires `?inline=capabilities` reads, just presence on writes(like model) - remove "schemas" from model, moved into "capabilities" - add 'xid'. Change xref to start with / - add "labels" to model schema : Registry, Groups and Resources - add a "compatiblewith" well-known label - add support for `relation` type of URLs - add text about how to deal with sending incomplete results - error unless you can be tricky via something like pagination spec - allow ?export, ?inline, ?filter on all APIs to control responses - explain that "generated" errors != must send back to client - e.g. security - use highest alphabetical versionid (case insensitive) when all versions have the same "createdat" value. Remove requirement for ?setdefaultversionid - `DELETE RESOURCES` must put `epoch` under `meta` if present - Primer: explain why GROUPS and RESOURCES have attribute name restrictions - Primer: encourage domain/company prefix/suffixed on Groups (and Resources) - Add `capability.enforcecompatibility` so servers can indicate whether they'll enforce the `compatibility` attribute on the owning Resource - Clarify rules for updating Resources when dealing with 'xref'. - presence of any attribute on a 'write' to an xref'd resource is an error - xref->normal: - epoch = max(oldEpoch, targetResourceEpoch)+1 - createdat = oldCreatedAt - modifiedat = now - Updating a Version's `createdat` CAN make it the latest/default - add support for "shortself" - add "@" as a valid char for IDs Fixes xregistry#199 Fixes xregistry#216 Fixes xregistry#217 Fixes xregistry#213 Fixes xregistry#210 Fixes xregistry#211 Fixes xregistry#209 Fixes xregistry#187 Fixes xregistry#200 Fixes xregistry#202 Fixes xregistry#205 Fixes xregistry#207 Fixes xregistry#214 Fixes xregistry#203 Fixes xregistry#204 Fixes xregistry#206 Fixes xregistry#212 Signed-off-by: Doug Davis <[email protected]>
Fannon
pushed a commit
to Fannon/xregistry
that referenced
this issue
Jan 23, 2025
- clarify errors for bad paths and methods - Remove "origin" - add `/capabilities` API and "capabilities" Registry attr - requires `?inline=capabilities` reads, just presence on writes(like model) - remove "schemas" from model, moved into "capabilities" - add 'xid'. Change xref to start with / - add "labels" to model schema : Registry, Groups and Resources - add a "compatiblewith" well-known label - add support for `relation` type of URLs - add text about how to deal with sending incomplete results - error unless you can be tricky via something like pagination spec - allow ?export, ?inline, ?filter on all APIs to control responses - explain that "generated" errors != must send back to client - e.g. security - use highest alphabetical versionid (case insensitive) when all versions have the same "createdat" value. Remove requirement for ?setdefaultversionid - `DELETE RESOURCES` must put `epoch` under `meta` if present - Primer: explain why GROUPS and RESOURCES have attribute name restrictions - Primer: encourage domain/company prefix/suffixed on Groups (and Resources) - Add `capability.enforcecompatibility` so servers can indicate whether they'll enforce the `compatibility` attribute on the owning Resource - Clarify rules for updating Resources when dealing with 'xref'. - presence of any attribute on a 'write' to an xref'd resource is an error - xref->normal: - epoch = max(oldEpoch, targetResourceEpoch)+1 - createdat = oldCreatedAt - modifiedat = now - Updating a Version's `createdat` CAN make it the latest/default - add support for "shortself" - add "@" as a valid char for IDs Fixes xregistry#199 Fixes xregistry#216 Fixes xregistry#217 Fixes xregistry#213 Fixes xregistry#210 Fixes xregistry#211 Fixes xregistry#209 Fixes xregistry#187 Fixes xregistry#200 Fixes xregistry#202 Fixes xregistry#205 Fixes xregistry#207 Fixes xregistry#214 Fixes xregistry#203 Fixes xregistry#204 Fixes xregistry#206 Fixes xregistry#212 Signed-off-by: Doug Davis <[email protected]> Signed-off-by: Simon Heimler <[email protected]>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
?inline=capabilities
/capabities
The text was updated successfully, but these errors were encountered: