Types of schemes

ip:

The “ip” scheme is used to identify an Ip Host instance. Ords starting with “ip” are always absolute and ignore any base that may be specified. The body of a “ip” query is a DNS hostname or an IP address of the format “dd.dd.dd.dd”.
fox:

The “fox” scheme is used to establish a Fox session. Fox is the primary protocol used by Niagara for IP communication. A “fox” query is formatted as “fox:” or “fox:<port>”. If port is unspecified then the default 1911 port is assumed.
file:

The “file” scheme is used to identify files on the file system. All file ords resolve to instances of javax.baja.file.BIFile. File queries always parse into a FilePath. File ords include the following examples:
- Authority Absolute: “//hostname/dir1/dir2”
- Local Absolute: “/dir1/dir2”
- Sys Absolute: “!lib/system.properties”
  
  Sys absolute paths indicate files rooted under the Niagara installation directory identified via Sys.getBajaHome().
- User Absolute: “^config.bog”
  
  User absolute paths are rooted under the user home directory identified via Sys.getUserHome(). In the case of station VMs, user home is the directory of the station database.
- Relative: “myfile.txt”
- Relative with Backup: “../myfile.txt”
module

The “module” scheme is used to access BIFiles inside the module jar files. The module scheme uses the “file:” scheme's formatting where the authority name is the module name. Module queries can be relative also. If the query is local absolute then it is assumed to be relative to the current module. Module queries always parse into a FilePath:
- module://icons/x16/file.png
- module://baja/javax/baja/sys/BObject.bajadoc
- module:/doc/index.html
station:

The “station” scheme is used to resolve the BComponentSpace of a station database.
slot:

The “slot” scheme is used to resolve a BValue within a BComplex by walking down a path of slot names. Slot queries always parse into a SlotPath.
h:

The “h” scheme is used to resolve a BComponent by its handle. Handles are unique String identifiers for BComponents within a BComponentSpace. Handles provide a way to persistently identify a component independent of any renames which modify a component's slot path.
service:

The “service” scheme is used to resolve a BComponent by its service type. The body of the query should be a type spec.
spy:

The “spy” scheme is used to navigate spy pages. The javax.baja.spy APIs provide a framework for making diagnostics information easily available.
bql:

The “bql” scheme is used to encapsulate a BQL query.