`prefix/resource:<id>` questions & possibilities
# spicedbv
verdverm.com
09/22/2025, 8:44 PMWhat are these prefix/resource things called? What can I do with them?
Copy code
blog/user, blog/post, ...
bsky/user, bsky/post, ...verdverm.com
09/22/2025, 8:46 PMCan I for example have a lot of these, and they can cross reference each other? Or more so have a set of shared resources that other "namespaces" (?) can build on? (more like a tree than a graph with potential cycles)
y
yetitwo
09/22/2025, 8:55 PMthey're a convention - there's nothing in SpiceDB that explicitly references or handles them
j
Joey
09/22/2025, 8:56 PMin SpiceDB OSS and AuthZed Cloud; AuthZed serverless uses them
Joey
09/22/2025, 8:56 PMbut yeah, they are convention in standard SpiceDB and can have whatever nesting you like
Joey
09/22/2025, 8:56 PMits equivalent of naming them
defnition foo_bar_bazdefinition foo/bar/bazJoey
09/22/2025, 8:56 PMbasically the same thing
v
verdverm.com
09/22/2025, 9:52 PMI could use them for a "namespacing" concept then, such that my app has the core, and user apps can add extra?
(not sure if this is a great idea generally, opens lots of security issues, but could be a vetting and PR process such that they can only come from the official source)
j
Joey
09/22/2025, 9:53 PMif you want to generate schema, yes
v
verdverm.com
09/22/2025, 10:01 PMalready code gen'n the spicedb schema :]
https://github.com/blebbit/atproto/tree/main/packages/pds/src/authz/spicedb/schema
verdverm.com
09/22/2025, 10:03 PMfyi, this is related to bringing "permissioned spaces" to https://atproto.com via spicedb. This particular question is about... what do apps do that cannot model their needs on the common schema. There are so many things that would be easier if they had some ability to extend the schema, however there be dragons lurking about down this path too...
verdverm.com
09/22/2025, 10:04 PMdef a day 2 problem, trying to keep it as simple as possible for now
6 Views