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: RE: Map/list without entry_schema


Hi Gabor,

 

This topic was discussed during Tuesdayâs TOSCA Language Ad-Hoc meeting. The team decided that entry_schema should be mandatory for property definitions of type âlistâ or âmapâ. We will make sure this is properly documented in TOSCA v2.0.

 

Thanks,

 

Chris

 

From: Arturo Martin De Nicolas <arturo.martin-de-nicolas@ericsson.com>
Sent: Monday, July 20, 2020 11:44 PM
To: Chris Lauwers <lauwers@ubicity.com>; Marton, Gabor (Nokia - HU/Budapest) <gabor.marton@nokia.com>; tosca@lists.oasis-open.org
Cc: Nemeth, Denes (Nokia - HU/Budapest) <denes.nemeth@nokia.com>; Nguyenphu, Thinh (Nokia - US/Dallas) <thinh.nguyenphu@nokia.com>
Subject: RE: Map/list without entry_schema

 

Hello Chris, GÃbor,

 

If the type of the entries can be anything how can the parser validate a property assignment, in particular if they are of a complex type? Is there any case in which you see it useful not to specify the type?

 

I am thinking that it should be made mandatory, or?

 

Best regards,

Arturo

 

 

 

From: tosca@lists.oasis-open.org <tosca@lists.oasis-open.org> On Behalf Of Chris Lauwers
Sent: Monday, July 20, 2020 11:46 PM
To: Marton, Gabor (Nokia - HU/Budapest) <gabor.marton@nokia.com>; tosca@lists.oasis-open.org
Cc: Nemeth, Denes (Nokia - HU/Budapest) <denes.nemeth@nokia.com>; Nguyenphu, Thinh (Nokia - US/Dallas) <thinh.nguyenphu@nokia.com>
Subject: [tosca] RE: Map/list without entry_schema

 

Hi GÃbor,

 

  1. When the entry_schema is not provided, there is no type specified, meaning the type of the entries in the collection could be anything. The only condition that must hold true is that all the entries must be of the same type.
  2. The comment in v1.3, 3.3.1.1 is not correct, since âtypeâ is a mandatory keyword for property definitions, so there is never a situation where a âdefaultâ type must be used. While it is true that âtypeâ is not required for parameter definitions, in practice those definitions will also always have a type:
    1. If the parameter definition defines a ârefinementâ of a property definition, and the parameter definition does specify a type, then then type of the refined property definition is used.
    2. If the parameter definition defines and input or an output definition, and there is not type specified, the orchestrator will be able to determine an âimpliedâ type by looking at the type of the âvalueâ or the âmappingâ fields in the parameter definition.

 

Hope this helps,

 

Chris

 

From: tosca@lists.oasis-open.org <tosca@lists.oasis-open.org> On Behalf Of Marton, Gabor (Nokia - HU/Budapest)
Sent: Friday, July 17, 2020 8:08 AM
To: tosca@lists.oasis-open.org
Cc: Nemeth, Denes (Nokia - HU/Budapest) <denes.nemeth@nokia.com>; Nguyenphu, Thinh (Nokia - US/Dallas) <thinh.nguyenphu@nokia.com>
Subject: [tosca] Map/list without entry_schema

 

Dear TOSCA Experts,

 

what is the type of the entries in a map or list when the entry_schema is not provided?

 

data_types:

  provider.datatypes.Example:

    derived_from: tosca.datatypes.Root

    properties:

      map_without_entry_schema:

        type: map

 

Is it string? For properties and parameters at least, the default type is explicitly stated to be string (v1.3, 3.3.1.1), but I found no similar statement for entry_schema.

 

Greetings,

 

GÃbor



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