[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: [OASIS Issue Tracker] Created: (ODATA-364) Remove restriction that a property MUST NOT have the same name as its containing type
Remove restriction that a property MUST NOT have the same name as its containing type ------------------------------------------------------------------------------------- Key: ODATA-364 URL: http://tools.oasis-open.org/issues/browse/ODATA-364 Project: OASIS Open Data Protocol (OData) TC Issue Type: Improvement Components: OData CSDL Affects Versions: V4.0_WD01 Environment: [Proposed] Reporter: Ralf Handl Fix For: V4.0_WD01 Chapters 8 and 9 state that - Properties MUST NOT have the same name as the declaring entity type. - Properties MUST NOT have the same name as the declaring complex type. This sometimes prevents using natural names for properties, e.g. - EntityType Employee - EntityType Manager inherits from Employee - EntityType Employee has NavigationProperty that leads to the manager The natural name for the navigation property is Manager, but prevented by the above rule. So the navigation property has to be named "TheManager" or "manager" (using different case) -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://tools.oasis-open.org/issues/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]