Tools : Validation Error Code

This tool allows the validation of an Object that is publicly reachable by the tool: http://dev_devtoolkit.openmobilealliance.org/OEditor/OMNAVerify 

  • The error codes relevant to single Object Validation are from (403 to 499). 
  • In addition, the user needs to validate by hand the criteria provided by error codes (400 to 402).

The information in the OMNA LwM2M Registry is contained in two files:

  • DDF.xml: this file contains all the Object information that is displayed in the OMA LwM2M registry (with the exception of the Reusable Resources that are contained in the "Common.xml" file.
  • Common.xml: this file contains the Reusable Resources information that is displayed in the OMA LwM2M registry.

Error Codes

General Requirements

Fault ID.Resolve ByDescription
001MaintainerIt cannot be downloaded from the Registry API.
002Maintainer
  1. Internal server error, Unknown error code when finding files from the repository to validate
  2. Other errors that prevent the validator to validate the remaining tasks
  3. The validation tool is configured to not do full validation of external links, for example, the object contains a link to the TS but the validation is requested to ignore validating that
005MaintainerSenML units were not possible to load and therefore not used during validation
010MaintainerThe API does not return the same number of objects for DDF.XML
011MaintainerThe API does not return the same number of resources for Common.XML - NOT SUPPORTED, THE API DOES NOT SUPPORT Common.XML
021MaintainerThe XML File is NOT 1) well-formatted or 2) valid according to the schema in DDF.XML
022

Maintainer

The XML File is NOT 1) well-formatted or 2) valid according to the schema in Common.XML
023MaintainerValidate that the API return MIME Type application/json
031Maintainer

Validate that the file contains at least one object in DDF.XML

032Maintainer

Validate that the file contains at least one resource in Common.XML

041MaintainerInvalid content or element that is not expected in DDF.XML
050MaintainerIndicate that there are one or more files in the repository that does not exist in DDF.xml.


Elements in the DDF.xml

Fault IDResolve ByElementsDescription
200MaintainerObjectID

Version is the same between two objects with the same Object ID
201MaintainerName is different for a different version of the same Object ID
202MaintainerThe description is different for a different version of the same Object ID
210MaintainerURN

The URN or ObjectID not correct according to the Technical Specification

The URN or Source category is not correct according to the Technical Specification

The URN or Ver is not correct according to the Technical Specification

The ID is not in the range allowed by Source

220MaintainerNameIs not allowed to be empty
230MaintainerDescriptionIs not allowed to be empty
240MaintainerOwnerIs not allowed to be empty
250MaintainerSourceIs not allowed to be empty
251MaintainerMust be either "0", "1" or "2" without quotes
260MaintainerVerMust be either empty or 3 character with the format <Digit>.<Digit> according to the Technical Specification
270SubmitterDDF


Must be either Empty or a valid link that does not return HTTP 404 (Not Found) and any error while downloading the object or processing the object
271MaintainerThe MIME type of the response must be text/xml
272SubmitterThe link contains an invalid Object
273SubmitterThe link should contain an Object with a minimum of one resource
274Maintainer

For each entry in the <DDF> element there MUST be a file name <ObjectID>-<Ver> in the "version_history" folder. "The error is the file for this ObjectID is missing  from the "version_history" folder" or the content of both Objects are not the same.

In addition these are possible issues:

  1. An Object that is not the latest version MUST be prefixed with "version_history"
  2. An Object that is the latest version MUST NOT be prefixed with "version_history"
275MaintainerPrevious version exist twice, which is not allowed
276MaintainerPrevious version missing. For example if an object contains ver 2.4, then the following version must exist: 2.3, 2.2, 2.1, 2.0, 1.0
280n/a

LWM2M

(Void)


Must either be empty if DDF is empty or a valid link to the tool with the URL to load the object into the tool

A valid URL must start with the call to the tool:

http://devtoolkit.openmobilealliance.org/OEditor/LWMOView?url=
Followed by the URL, (URL-encoded), to the Object.

For example http://devtoolkit.openmobilealliance.org/OEditor/LWMOView?url=http%3A%2F%2Fwww.openmobilealliance.org%2Ftech%2Fprofiles%2FLWM2M_APN_connection_profile-v1_0.xml

Note: this error code is not longer in used. The element that contained the link to the LwM2M Editor was removed from the DDF.

290MaintainerVortoMust be either Empty or a valid link that does not return HTTP 404 (Not Found)
291n/a
DISABLED - The MIME Type of the response must not be "html" to avoid web page with HTTP 404
300MaintainerDDFLinkIs not allowed to be empty
301MaintainerMust be either "0", or "1" without the quotes
310MaintainerTSTechnical Specification (TS) must be either empty or a valid link that does not return HTTP 404 (Not Found)
311n/aDISABLED - The MIME Type of the response must not be "html" to avoid web page with HTTP 404
320MaintainerTSLinkIs not allowed to be empty
321MaintainerMust be either "0", or "1" without the quotes
330SubmitterLicenseType

Under development

Must either be empty or string - Will not be verified, empty or non-existing is treated equally

Note: to be changed to, it cannot be empty

400SubmitterContent of Object







"ObjectID" inside the object is not the same as in the DDF.XML File
401Submitter

"Object URN" inside the object is not the same as in the DDF.XML File

402Submitter"Object Name" inside the object is not the same as in the DDF.XML File
403SubmitterIncorrect content of LWM2MVersion
404SubmitterNon-existent xml schema reference
405

Submitter

Invalid XML schema reference.
406SubmitterThe object is missing Line Feed (LF) characters in the end of the file
407SubmitterObject contains Carriage Return (CR) which is not allowed in LwM2M Object and Resource Registry and is required in Object XML files
408SubmitterObject missing several Line Feed (LF), which is not allowed
700SubmitterInvalid XML characters in Description1, e.g. usage of smart quotes (“ExtDevInfo”) rather than straight quotes ("ExtDevInfo")
701MaintainerThe Description1 in the DDF and in the Object doesn't match
705SubmitterInvalid XML characters in Description2, e.g. usage of smart quotes (“ExtDevInfo”) rather than straight quotes ("ExtDevInfo")
410SubmitterContent of the objects resources







Empty Name
411SubmitterInvalid Operations according to the Technical Specification (TS)
412SubmitterInvalid Type according to the Technical Specification (TS)
413SubmitterInvalid Type for an resource with Operation = "E" (Execute). Also, "E" operation, MUST have "Single" as value of the "Instances" field as indicated in the TS.
414SubmitterInvalid MultipleInstances value
415SubmitterInvalid Mandatory value
416SubmitterEmpty Description
420SubmitterInvalid XML characters in Description, e.g. usage of smart quotes (“ExtDevInfo”) rather than straight quotes ("ExtDevInfo")
417SubmitterInvalid Unit value according to SenML
418Submitter

In the description of a range it is not possible to use "-" or "to" instead it should be used ".."

  • Correct Example: "0..23"
  • Incorrect: "0 to 23"
450SubmitterContent of the object's reusable resources





The object uses an non existing reusable resource
451SubmitterSame reusable resource already included
460SubmitterMismatch with reusable resources on: Name
461SubmitterMismatch with reusable resources on: Operation
462SubmitterMismatch with reusable resources on: Type
463SubmitterMismatch with reusable resources on: RangeEnumeration
464SubmitterMismatch with reusable resources on: Unit
465Submitter

Mismatch with reusable resources on: Description

  • Ignore blank space, tab character, line feed and new line character.
  • This rule implies that description doesn't change the meaning.

Elements in the Common.xml 

Fault IDResolve byElementDescription
500MaintainerItem IDThe ID is already used in another registration, it must be unique
501MaintainerThe ID is not in the range of (2048 - 26240)
510MaintainerNameIs not allowed to be empty
520SubmitterOperationsInvalid Operations according to the Technical Specification, TS
530SubmitterTypeInvalid Type according to the Technical Specification, TS
531SubmitterInvalid Type for an resource with Operation = "E" (Executable)
540n/aRangeEnumerationN/A, No validation done
541Submitter

In the description of a range it is not possible to use "-" or "to" instead it should be used ".."

  • Correct Example: "0..23"
  • Incorrect: "0 to 23"
551SubmitterUnitsInvalid Unit according to SenML
570SubmitterDescriptionIs not allowed to be empty
571MaintainerVOID. Description is not CDATA encoded
580MaintainerTSTechnical Specification (TS), must be either Empty or a valid link that does not return HTTP 404 (Not Found)
581MaintainerThe MIME Type of the response must not be "html" to avoid web page with HTTP 404
590MaintainerTSLinkIs not allowed to be empty
591MaintainerMust be either "0" or "1" without quotes
601SubmitterNameInvalid XML characters in Name, e.g. "smart quotes"
602SubmitterDescriptionInvalid XML characters in Description, e.g. "smart quotes"
603SubmitterTS LinkInvalid XML characters in TS Link
604SubmitterOperationsInvalid XML characters in Operations according to the Microsoft XML parser in addition "smart quotes" will generate this error.
605

Submitter

TSInvalid XML characters in Technical Specification (TS), e.g. "smart quotes"


Elements inside of the Object

Fault IDResolve ByElementsDescription
800SubmitterLwM2MVersion or ObjectVersionOne or both of these elements (LwM2MVersion, ObjectVersion) are missing from the Object.