Online OIOUBL Dokumentation
|
|
Code
Code types are used to delimit the values allowed for an element (BBIE) from a list of options. Code types differ from IDs in that the allowed values are public known, and may be determined at the time of receipt. OIOUBL operates with the following code types:
- Static codes, which are embedded in the standard.
- Public known codes which can be updated, e.g. ISO 4217.
- Bilateral agreed codes
| Attribute |
Use |
Example |
OIOUBL Recommendation |
| listID |
Identifies the list |
urn:oioubl:codelist: addressformatcode-1.1 |
Required for OIOUBL codes |
| listAgencyID |
Identifies the issuer of the list |
320 |
Required for OIOUBL codes |
| listAgencyName |
Specifies the name of the issuer of the list |
|
Optional |
| listVersionID |
Version of the list |
|
Optional |
| name |
Name of the list |
|
Not used |
| languageID |
The language in which the list is specified. |
|
Not used |
| listURI |
Link to the location of the list. |
|
Not used |
| listSchemeURI |
Link to the location of the list schema. |
|
Not used |
| Content |
Xsd:normalizedString |
|
Specified exactly as in the list. Please note the distinguishing between upper and lower case letters. |
Static and bilateral agreed codes are typically specified without attributes, whereas public known codes may benefit from the use of the metadata that may be provided by the attributes. In these, both the listAgencyID and listID must be specified. For the Danish OIOUBL customization a series of code lists has been prepared. When these are used, the attribute listAgencyID and listID must be filled out with the value that identifies the code list. This type of code lists are named a "codelist" in the urn, e.g. "urn:oioubl:codelist:[name]-1.1".
|
|
