The API allows configuration files to be created on a per-API basis. This is typically per-store, allowing items such as the identifierSpace, schemaSpace, match level, and name property to be tweaked as needed.
This should really be visible to end-users using the store. One way to expose this would be to return it in a custom section of the service metadata.
The API allows configuration files to be created on a per-API basis. This is typically per-store, allowing items such as the identifierSpace, schemaSpace, match level, and name property to be tweaked as needed.
This should really be visible to end-users using the store. One way to expose this would be to return it in a custom section of the service metadata.