[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: [OASIS Issue Tracker] (ODATA-603) Primitive type Edm.Stream: use as type of collection, input parameter, return type, or underlying type of type definition
[ https://tools.oasis-open.org/issues/browse/ODATA-603?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Pizzo updated ODATA-603: -------------------------------- Environment: [Proposed] Proposal: >>Edm.Stream can be used in typedefinition, return type, binding parameter, but not as non-binding parameter or in a collection. > Primitive type Edm.Stream: use as type of collection, input parameter, return type, or underlying type of type definition > ------------------------------------------------------------------------------------------------------------------------- > > Key: ODATA-603 > URL: https://tools.oasis-open.org/issues/browse/ODATA-603 > Project: OASIS Open Data Protocol (OData) TC > Issue Type: Improvement > Components: OData CSDL > Affects Versions: V4.0_OS > Environment: [Proposed] > Reporter: Ralf Handl > Fix For: V4.0_ERRATA01 > > > Edm.Stream is listed as a primitive type. Does this allow properties of type Collection(Edm.Stream)? > What about actions or functions that use Edm.Stream as an input parameter type or return type? > What about its use as an underlying type of a type definition? -- This message was sent by Atlassian JIRA (v6.1.1#6155)
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]