[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: [OASIS Issue Tracker] (OSLCCORE-10) Normalizing Preview and Dialog
[ https://issues.oasis-open.org/browse/OSLCCORE-10?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=59641#comment-59641 ] Martin Pain commented on OSLCCORE-10: -------------------------------------- To me, in OSLC "Dialog" refers to something that can be submitted & returns a URI (analogous to an HTTP POST) and "[Rich] Preview" refers to somethign that displays information about a resource (analogous to an HTTP GET) and "Delegated UI" is the super-term that applies to both. Under that understanding, the descriptor might be called DelegatedUIDescriptor instead of DialogDescriptor. However, I think it's more important to address: 1. Consistency within v3 (e.g. not having a DelegatedUIDescriptor with an oslc:dialog property) 2. Backwards-compatibility with v2 (maybe minimising repeated properties needed for backwards-compatibility) than to have use the view that I have of the terminology. > Normalizing Preview and Dialog > ------------------------------ > > Key: OSLCCORE-10 > URL: https://issues.oasis-open.org/browse/OSLCCORE-10 > Project: OASIS OSLC Lifecycle Integration Core (OSLC Core) TC > Issue Type: Bug > Reporter: James Amsden > Assignee: James Amsden > Priority: Minor > > Resource-preview uses Compact, Preview and oslc:document to manage previews. Compact defines the preview descriptor and contains properties for small and large previews. Preview contains the size hings and oslc:document link to the actual HTML preview dialog. > Dialogs-v3 uses Dialog and oslc:dialog with different Link headers for the creationDialog and selectionDialog. > Should we consider normalizing these different approaches to dialog management? -- 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]