[OASIS Issue Tracker] Issue Comment Edited: (ODATA-258) Advertise function imports in service document

[OASIS Issues Tracker <workgroup_mailer@lists.oasis-open.org>]

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

Ralf Handl edited comment on ODATA-258 at 3/5/13 7:05 AM:
----------------------------------------------------------

Changed kind constant "Function" to "FunctionImport" as we have both Function and FunctionImport in CSDL, and this kind of service document entry refers to a FunctionImport.

Also named element metadata:function-import.

I'm wondering why we have a title attribute for the metadata:function-import and metadata:entity elements (added with ODATA-169) instead of using an atom:title child element for symmetry with the app:collection element.

      was (Author: ralfhandl):
    Changed kind constant "Function" to "FunctionImport" as we have both Function and FunctionImport in CSDL, and this kind of service document entry refers to a FunctionImport.

Also named element metadata:function-import.

I'm wondering why we have a title attribute for the metadata:function-import and metadata:entity elements instead of using an atom:title child element for symmetry with the app:collection element.
  
> Advertise function imports in service document
> ----------------------------------------------
>
>                 Key: ODATA-258
>                 URL: http://tools.oasis-open.org/issues/browse/ODATA-258
>             Project: OASIS Open Data Protocol (OData) TC
>          Issue Type: Improvement
>          Components: OData ATOM Format , OData CSDL, OData JSON Format
>    Affects Versions: V4.0_WD01
>         Environment: [Proposed]
>            Reporter: Ralf Handl
>            Assignee: Ralf Handl
>             Fix For: V4.0_WD01
>
>
> The service document is an entry point for hypermedia-driven clients, so function imports that can be called "directly from the service root" should also be advertised.
> Function imports that require a binding parameter don't fall into that category.
> Ideally the advertised function imports would require no parameters to be passed, i.e. only have parameters with default values or no parameters at all, so they behave to GET requests similar to named entities and entity sets.
> As in real life we also encounter entity sets that e.g. respond with errors if queried without a sufficiently selective $filter query parameter, I hesitate to make "only parameters with default values" a requirement for being advertised.

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