Re: Tosca.meta block 0 clarification

[Calin Curescu <calin.curescu@ericsson.com>]

Hi Gabor, Denes,

 

As it is now, the standard only allows custom key-value pairs in other blocks than block 0. In TOSCA v2.0 this is specification is kept.

So yes you are right, SOL004 is not legal, you need an empty line before the non-standard keynames, signifying a new block.

 

BR/Calin

 

From: "Marton, Gabor (Nokia - HU/Budapest)" <gabor.marton@nokia.com>
Date: Wednesday, 5 August 2020 at 17:35
To: Chris Lauwers <lauwers@ubicity.com>, Calin Curescu <calin.curescu@ericsson.com>
Cc: "Nguyenphu, Thinh (Nokia - US/Dallas)" <thinh.nguyenphu@nokia.com>, "tosca@lists.oasis-open.org" <tosca@lists.oasis-open.org>, "Nemeth, Denes (Nokia - HU/Budapest)" <denes.nemeth@nokia.com>
Subject: RE: Tosca.meta block 0 clarification

 

Hi Calin,

 

what is your standpoint in this question?

 

In case it is not legal to use non-standard keynames in block 0, SOL 004 is not legal either.

 

Greetings,

 

GÃbor

 

From: tosca@lists.oasis-open.org <tosca@lists.oasis-open.org> On Behalf Of Chris Lauwers
Sent: Thursday, July 23, 2020 9:56 PM
To: Calin Curescu <calin.curescu@ericsson.com>
Cc: Nguyenphu, Thinh (Nokia - US/Dallas) <thinh.nguyenphu@nokia.com>; tosca@lists.oasis-open.org; Nemeth, Denes (Nokia - HU/Budapest) <denes.nemeth@nokia.com>
Subject: [tosca] RE: Tosca.meta block 0 clarification

 

Hi Denes,

 

I assume this email was intended for Calin? Calin has contributed the TOSCA v2.0 text defining the updated CSAR format, so he is in the best position to respond. That said, I believe it is not legal to use non-standard keynames in block 0. Calin, do you have a different understanding?

 

Thanks,

 

Chris

 

From: tosca@lists.oasis-open.org <tosca@lists.oasis-open.org> On Behalf Of Nemeth, Denes (Nokia - HU/Budapest)
Sent: Tuesday, July 14, 2020 10:37 PM
To: tosca@lists.oasis-open.org
Cc: Nguyenphu, Thinh (Nokia - US/Dallas) <thinh.nguyenphu@nokia.com>
Subject: [tosca] 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