[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: RE: [tosca] key_schema in TOSCA 1.3?
My understanding is that YAML allows pretty much anything to be used as a key in a map, including complex objects. This might be a good topic to revisit during our Tuesday meeting. Thanks, Chris From: tosca@lists.oasis-open.org <tosca@lists.oasis-open.org>
On Behalf Of Tal Liron I'm confused by the intent for new grammar for key_schema. How do you assign values if the key_schema is not a string? YAML does not have such syntax. Would it be a list a tuples, perhaps? Is this in the spec somewhere but I missed it? Also, it seems the the new "schema definition" itself has keywords for key_schema and entry_schema. Is this a mistake? Shouldn't those only be in attribute/property definitions? Also, a long-standing issue: the entry_schema and key_schema keywords are marked as non-required. However, if the type is a list or map then they should be required, no? Or is there a default value (string?) that is expected. This behavior
is not specified. |
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]