[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: [OASIS Issue Tracker] Updated: (ODATA-478) Clarify format for values of Content-ID header in $batch parts
[ http://tools.oasis-open.org/issues/browse/ODATA-478?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ralf Handl updated ODATA-478: ----------------------------- Resolution: https://tools.oasis-open.org/version-control/browse/wsvn/odata/trunk/spec/ABNF/odata-abnf-construction-rules.txt?rev=480 https://tools.oasis-open.org/version-control/browse/wsvn/odata/trunk/spec/ABNF/odata-abnf-testcases.xml?rev=480 > Clarify format for values of Content-ID header in $batch parts > -------------------------------------------------------------- > > Key: ODATA-478 > URL: http://tools.oasis-open.org/issues/browse/ODATA-478 > Project: OASIS Open Data Protocol (OData) TC > Issue Type: Improvement > Components: OData Protocol > Affects Versions: V4.0_CS01 > Environment: [Applied] > Reporter: Ralf Handl > Fix For: V4.0_CSD03 > > > Part 1 refers to RFC2045, which in turn refers to RFC822, which limits values to email-address-like strings enclosed in "<" and ">" that are globally unique. -- 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]