URIs for locating/identifying resources and assets
Currently resource management is largely done in the client app, which includes URIs and resource namespaces/schemes. This functionality needs to be reconsidered in the context of FS2, packages, assets, and other domain specific objects/assets like maps, etc.
URIs should be domain-neutral so that they can be used universally to refer to objects of various kinds. The role of schemes should also be reconsidered to more generally just identify the object that is responsible for locating the object referred to by the URI's path and possible "&a=b" parameters.
#5 Updated by skyjake over 7 years ago
To avoid confusing two concepts that should be kept separate, URIs should not be thought of as object identifiers, just addresses using which objects can be found. That is, when declaring an object, one does not specify its URI but rather just an ID/name — the exact form of URIs referring to the object depend on the scheme that interprets them.