[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: [OASIS Issue Tracker] Updated: (ODATA-457) Require hash (#) on odata.type
[ http://tools.oasis-open.org/issues/browse/ODATA-457?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Pizzo updated ODATA-457: -------------------------------- Environment: [Applied] (was: [Proposed]) > Require hash (#) on odata.type > ------------------------------ > > Key: ODATA-457 > URL: http://tools.oasis-open.org/issues/browse/ODATA-457 > Project: OASIS Open Data Protocol (OData) TC > Issue Type: Bug > Components: OData ABNF Construction Rules, OData ATOM Format , OData Extension for JSON Data > Affects Versions: V4.0_CSD01 > Environment: [Applied] > Reporter: Michael Pizzo > Fix For: V4.0_CSD02 > > > ODATA-445 made odata.type relative to containing odata.type or (at the root) odata.context. In applying this change the rules around optionality of the hash (#) for type names in the current document seemed arbitrary and overly complex without adding much value. > We should consider making the hash required (as it is in context url) except possibly for built-in primitive types (which are already special in that we require them not to specify the edm prefix) -- 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]