4. Namespaces & schemas¶
A namespace must be identified for each prefix using the @xmlns:prefix
attribute.
Important
The client must use the same version of a namespace as the server!
The current namespace versions are listed in the greeting
(see Service discovery).
If the versions in the documentation differ from the versions in the greeting
,
follow the versions in the greeting
.
To enable XML validation on the client side, depending on the selected XML-validation tool, there are 2 options:
to link a namespace to the location of a schema (see the table below) inside messages using the
@xsi:schemaLocation
attribute, for the tool to locate the schema from here – this option is illustrated in structure descriptions, orto pass the location of the global schema as an argument to the XML-validation tool directly, such as:
xmllint --noout --schema "/usr/share/fred-client/schemas/all.xsd" -
The FRED EPP server as such does NOT require schema locations inside messages and ignores them if they are present.
The global schema all-2.4.0.xsd
(alias all.xsd
) imports the following
partial schemas and thus provides the definitions of all namespaces in a single file.
Prefix [1] |
Namespace identifier |
Schema file (partial) |
Description |
---|---|---|---|
|
|
|
Extensible Provisioning Protocol v1.0 |
|
|
|
Extensible Provisioning Protocol v1.0 |
|
|
|
FRED EPP protocol extensions |
|
|
|
FRED EPP protocol extensions |
|
|
|
FRED object extension for domain provisioning |
|
|
|
FRED object extension for contact provisioning |
|
|
|
FRED object extension for nsset provisioning |
|
|
|
FRED object extension for keyset provisioning |
|
|
|
FRED command/response extensions for ENUM domains |
|
|
|
FRED command/response extensions for a mailing address in contacts |
|
|
N/A |
Namespace for an XML Schema instance |
|
|
N/A |
Namespace for the XML Schema |