Re: [dxwg] Content for the Abstract Model section

How should we define a list of actions (methods?) in the abstract that a client and server must/may etc implement? What formal function description languages are available? Should it be something like this:

    function request_available_profiles:
        a client requests the available profiles for a resource

    function get_profile:
        a client requests a profile preference list from a server

    function list_profiles:
        a server lists the profiles for a resource    

    function send_profile
        a server responds to a get_profile request with either a specific profile or a defalt profile if the requested profile(s) is unavailable

GitHub Notification of comment by nicholascar
Please view or discuss this issue at using your GitHub account

Received on Wednesday, 10 October 2018 19:46:50 UTC