OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.

 


Help: OASIS Mailing Lists Help | MarkMail Help

tosca message

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]


Subject: Tosca.meta block 0 clarification


Dear Colin

 

After reading the Tosca 1.x and the Tosca 2.0 draft I am not able to deduct if it is allowed to populate the block 0 with additional keys or only the other blocks may be populated with additional key-value pairs. The current draft states the following:

 

The first block, called block_0, contains metadata about the CSAR itself and is further defined below. Other blocks may be used to represent custom generic metadata or metadata pertaining to files in the CSAR.

 

Besides using the normative keynames in block_0 (i.e. CSAR-Version, Created-By, Entry-Definitions, Other-Definitions) users can populate further blocks in the TOSCA.meta file with custom key-value pairs that follow the entry syntax of the TOSCA.meta file, but which are outside the scope of the TOSCA specification.

 

Would it be possible to add a clarification sentence into the specs to define if extension of the block 0 is allowed or not.

 

Cheers Denes

 



[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]