[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: [OASIS Issue Tracker] Created: (ODATA-573) atom:id must be absolute according to Atom rules
atom:id must be absolute according to Atom rules ------------------------------------------------ Key: ODATA-573 URL: http://tools.oasis-open.org/issues/browse/ODATA-573 Project: OASIS Open Data Protocol (OData) TC Issue Type: Bug Components: OData ATOM Format Affects Versions: V4.0_CSD03 Environment: [Proposed] Reporter: Michael Pizzo Fix For: V4.0_CS02 According to atom (rfc4287), the atom:id must be an IRI which must be absolute: (section 4.2.6) The "atom:id" element conveys a permanent, universally unique identifier for an entry or feed. atomId = element atom:id { atomCommonAttributes, (atomUri) } Its content MUST be an IRI, as defined by [RFC3987]. Note that the definition of "IRI" excludes relative references. Though the IRI might use a dereferencable scheme, Atom Processors MUST NOT assume it can be dereferenced. In [ATOM] we talk about relative urls in section 4.3, and explicitly support relative ids in places we don't use atom:id, such as entity references, the ref attribute of deleted entry (is this legal according to atom-tombstone?), source and target for added/deleted links, etc. Attribute id The id attribute MUST be present. For entities the id attribute MUST be the atom:id of the referenced entity. It may be relative or absolute -- 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]