[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: [OASIS Issue Tracker] (ODATA-687) Prepare clients to deal with type annotations without the leading "#"
[ https://tools.oasis-open.org/issues/browse/ODATA-687?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Pizzo updated ODATA-687: -------------------------------- Description: ODATA-561 calls out the fact that the leading "#" is not really required (and doesn't really make sense) for primitive types (because they are not really a fragment located within the metadata document) and suggests (for backward compatibility) allowing, but not requiring, services to omit the "#" for primitive types. We should make clients aware that this change is expected, so that they can write their code appropriately. Ideally we would say: "Services should not include a leading # for primitive types but clients should be prepared to handle primitive types with or without a leading" was: ODATA-561 calls out the fact that the leading "#" is not really required (and doesn't really make sense) for primitive types (because they are not really a fragment located within the metadata document) and suggests (for backward compatibility) allowing, but not requiring, services to omit the "#" for primitive types. We should make clients aware that this change is expected, so that they can write their code appropriately. > Prepare clients to deal with type annotations without the leading "#" > --------------------------------------------------------------------- > > Key: ODATA-687 > URL: https://tools.oasis-open.org/issues/browse/ODATA-687 > Project: OASIS Open Data Protocol (OData) TC > Issue Type: Sub-task > Components: OData ATOM Format , OData JSON Format > Affects Versions: V4.0_OS > Environment: [Proposed] > Reporter: Michael Pizzo > Fix For: V4.0_ERRATA01 > > > ODATA-561 calls out the fact that the leading "#" is not really required (and doesn't really make sense) for primitive types (because they are not really a fragment located within the metadata document) and suggests (for backward compatibility) allowing, but not requiring, services to omit the "#" for primitive types. > We should make clients aware that this change is expected, so that they can write their code appropriately. > Ideally we would say: "Services should not include a leading # for primitive types but clients should be prepared to handle primitive types with or without a leading" -- This message was sent by Atlassian JIRA (v6.2.2#6258)
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]