...
| Section | ||||||||||||||||||||||||||||||||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| ||||||||||||||||||||||||||||||||||||||||||||||||
The
URIs are defined either as space properties, shortcuts, or application links (see System Identifier to URL URI Resolution Algorithm for details). This way an identifier is bound to an URI which defines an information system. This binding is used by the Information System Macros to decouple the URI from the macro. Autoconverters register themselves with their default identifier to the URI Autoconverter Service. The individual default system identifier suggested by the macros is one of such an identifier. So users who stick to the defaults do not need to add any configuration. In case the default identifiers cannot be used, some of the URIs are so specific so that the URI Autoconverter Service can determine which on to use for a given URI. So in this case nothing needs to configured either. In case users want to limit the autoconversion to a list of autoconverters, the
It is recommended to bind an information system to a system type defined by the autoconverter. This is done by binding a system identifier to a system type. Here is the list of autoconverters that bind to a type.
|
...
