[OASIS Issue Tracker] (OSLCCORE-59) Should Delegated Dialogs specify prefill for selectionDialogs?

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

James Amsden created OSLCCORE-59:
------------------------------------

             Summary: Should Delegated Dialogs specify prefill for selectionDialogs?
                 Key: OSLCCORE-59
                 URL: https://issues.oasis-open.org/browse/OSLCCORE-59
             Project: OASIS OSLC Lifecycle Integration Core (OSLC Core) TC
          Issue Type: Bug
            Reporter: James Amsden
            Assignee: James Amsden


I see from the change history in dialogs.html that Steve generalized dialog prefill to include selection dialogs. But everything in the document describes prefill only in the context of resource creation. It looks like prefill for selection dialogs never got finished. 

How clients would discover prefill support, and POST prefill content to the selection dialog descriptor is clear enough. The larger question is what a server would be expected to do with the entity request body POSTed to the dialog descriptor URI for a selectionDialog. 

The actual content of that entity request body could in general be unpredictable, even if resourceShapes are specified for the selection dialog, we don't know what those shapes might allow. The best we could say is that servers would use the information in the entity request body to inform the creation of the selection dialog, perhaps including resource URIs in that dialog that somehow match the POSTed prefill content. 

This seems useful, but a bit wide open. It could represent a simple query by example mechanism for resources of a particular type, or something as complex as sift or mongoDB query language. Without specifying what the POSTed request body means, is prefill on selection dialogs meaningful in the standard?




--
This message was sent by Atlassian JIRA
(v6.2.2#6258)