The WoTAssetFileType ObjectType represents a TD File that is used to define an WoTAsset. It is defined in Table 14.
All instances shall support a mode of Write + EraseExisting when Open is called. They may support mode of Read. Other modes are not allowed.
When writing, if Close is called the file is discard and nothing changes. If CloseAndUpdate is called the file is parsed and the variables are updated to match the WoT TD file.
Table 14 – WoTAssetFileType Definition
|
Attribute |
Value |
||||
|
BrowseName |
WoTAssetFileType |
||||
|
IsAbstract |
False |
||||
|
References |
NodeClass |
BrowseName |
DataType |
TypeDefinition |
Modelling Rule |
|
Subtype of the 0:FileType defined in OPC 10000-5. |
|||||
|
0:HasComponent |
Method |
CloseAndUpdate |
Defined in 6.3.9.2 |
Mandatory |
|
|
|
|||||
|
Conformance Units |
|||||
|
WoT Connectivity Base Functionality |
|||||
The CloseAndUpdate Method parses the TD and creates Variables from the TD properties.
CloseAndUpdate Method parses the TD and creates Variables from the TD properties. If the built-in Close Method is called instead, all changes are discarded.
Signature
CloseAndUpdate (
[in] 0:UInt32 FileHandle);
Table 15 – CloseAndUpdate Method Arguments
|
Argument |
Description |
|
FileHandle |
The handle for a file opened for writing. |
Method Result Codes
|
Result Code Symbolic Id |
Description |
|
Bad_InvalidState |
The file was not opened for writing. |
|
Bad_DecodingError |
The WoT Thing Description could not be parsed. |
|
Bad_NotSupported |
The TD is valid but cannot be mapped to OPC UA. |
|
Bad_NotFound |
The asset was not found on the network |
|
Bad_UserAccessDenied |
The session does not have the permissions required. |