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] (ODATA-653) ATOM format should mention atom:title and atom:updated in description of atom:feed and atom:entry


     [ https://tools.oasis-open.org/issues/browse/ODATA-653?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Ralf Handl updated ODATA-653:
-----------------------------

    Fix Version/s: V4.0_CSD03

> ATOM format should mention atom:title and atom:updated in description of atom:feed and atom:entry
> -------------------------------------------------------------------------------------------------
>
>                 Key: ODATA-653
>                 URL: https://tools.oasis-open.org/issues/browse/ODATA-653
>             Project: OASIS Open Data Protocol (OData) TC
>          Issue Type: Improvement
>          Components: OData ATOM Format 
>    Affects Versions: V4.0_CS02
>            Reporter: Evan Ireland
>            Priority: Minor
>             Fix For: V4.0_CSD03
>
>
> The ATOM format spec doesn't mention atom:title and atom:updated (which are required elements in feeds and entries).
> Since RFC4287 is listed as a normative reference, and it clearly defines that atom:title and atom:updated are required within feeds and entries, this omission is not critical.
> However an implementor who refers to the OData ATOM format spec (the prose, rather than the examples) and who does not also refer to the ATOM Syndication spec, may erroneously conclude that atom:title and atom:updated are not required in feeds and entries.
> Also, in the prose there is no guidance on what the content of these elements should be. Some examples tend to suggest that atom:title should be an entity set name for a feed, and that title should be empty for an element. And for atom:updated, the lexical format is clear, but exactly which date/time value should be specified, and whether a client can use that value in any meaningful way, is not mentioned.



--
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]