OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.


Help: OASIS Mailing Lists Help | MarkMail Help

odata message

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]

Subject: [OASIS Issue Tracker] Commented: (ODATA-254) Selection of individual properties in [ATOM] should not include property name

    [ http://tools.oasis-open.org/issues/browse/ODATA-254?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=32571#action_32571 ] 

Ralf Handl commented on ODATA-254:

Using metadata:type and metadata:null attributes within an metadata:value element feels odd, and we already use a local attribute "type" for the metadata:annotation element, so I defined the metadata:value element with local attributes "type" and "null":

  <!-- payload format for property value responses -->
  <xs:element name="value">
    <xs:complexType mixed="true">
        <xs:any namespace="http://docs.oasis-open.org/odata/ns/data"; processContents="lax" minOccurs="0"
          maxOccurs="unbounded" />
      <xs:attribute name="type" type="edm:TPropertyType" />
      <xs:attribute name="null" type="xs:boolean" />

Looking at how collections of primitive or complex scalar values are now represented, it feels extremely odd that the "element" element is "defined" in the (probably forever) schema-less "data" namespace instead of also being defined in the metadata namespace like its siblings metadata:annotation and metadata:value. 

> Selection of individual properties in [ATOM] should not include property name
> -----------------------------------------------------------------------------
>                 Key: ODATA-254
>                 URL: http://tools.oasis-open.org/issues/browse/ODATA-254
>             Project: OASIS Open Data Protocol (OData) TC
>          Issue Type: Bug
>          Components: OData ATOM Format 
>    Affects Versions: V4.0_WD01
>         Environment: [Proposed]
>            Reporter: Michael Pizzo
>             Fix For: V4.0_WD01
> Currently, the example in Section 10 of [ATOM] implies that when selecting a single property (i.e., ~Customers('ALFKI')/FirstName), the payload would contain the name of the property in the d: namespace:
>     <Title xmlns="http://schemas.microsoft.com/ado/2007/08/dataservices";>CEO<Title> 
> This implies that what is represented is a property with a given name, which is not the case; what should be represented is the *value* of the property, which is independent of the property itself (and can thus be used, for example, in passing as a parameter to an action). This is also inconsistent with how a function that returns a single property is represented, and is inconsistent with the JSON format (which represents this as a name/value pair with the name "value").
> We should specify that an individual property is serialized in ATOM as an element named "value" in the odata metadata namespace. 

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]