Ah so the path forward then would be to not use a ...
# spicedb
m
Ah so the path forward then would be to not use a prefix at all or keep a constant prefix then I would assume? What is the roadmap for prefixes? Is there any desire to support more than one prefix? I think it would be interesting if prefixes were "scoped" where a schema could be written for one prefix then separately written for another prefix and they would be joined as one. Example:
Copy code
// Write 1
definition core/user {}
Copy code
// Write 2
definition myservice/thing {}
Copy code
// Results in 
definition core/user {}
definition myservice/thing {}
Copy code
// Write 3 
definition myservice/thing {
  relation owner: core/user
}
definition myservice/specificthing {
  relation thing: myservice/thing
}
Copy code
// Results in 
definition core/user {}
definition myservice/thing {
  relation owner: core/user
}
definition myservice/specificthing {
  relation thing: myservice/thing
}
So the writes are scoped to a prefix and won't wipe out other prefixes.