Normalizing Preview and Dialog

XMLWordPrintable

    • Type: Bug
    • Resolution: Won't Fix
    • Priority: Minor
    • Component/s: None
    • None
    • Hide

      Normalize Preview and Dialog:
      1. use four Link headers: smallPreview, largePreview, creationDialog, selectionDialog - all referencing some DialogDescriptor

      2. Use one DialogDescriptor class for all dialogs - preview, selection, creation. That is, rename Dialog to DialogDescriptor and reuse the resource instead of Preview.

      3. DialogDescriptor::oslc:dialog would reference the actual HTML dialog.

      4. Compact no longer refers to the Preview, decoupling compact resource representations from any dialogs. Rather clients access the small or large preview from the Link headers. Compact is only about the compact representation of a link.

      5. Describe DialogDescriptor, size hints and resize rules in the dialogs-v3.html specification, and refer to this resource type in Preview, eliminating the redundant information between the two specifications.

      This makes dialog management more uniform, simpler, and eliminates an extra hop for Compact>Preview>document to access one of the preview dialogs.

      Show
      Normalize Preview and Dialog: 1. use four Link headers: smallPreview, largePreview, creationDialog, selectionDialog - all referencing some DialogDescriptor 2. Use one DialogDescriptor class for all dialogs - preview, selection, creation. That is, rename Dialog to DialogDescriptor and reuse the resource instead of Preview. 3. DialogDescriptor::oslc:dialog would reference the actual HTML dialog. 4. Compact no longer refers to the Preview, decoupling compact resource representations from any dialogs. Rather clients access the small or large preview from the Link headers. Compact is only about the compact representation of a link. 5. Describe DialogDescriptor, size hints and resize rules in the dialogs-v3.html specification, and refer to this resource type in Preview, eliminating the redundant information between the two specifications. This makes dialog management more uniform, simpler, and eliminates an extra hop for Compact>Preview>document to access one of the preview dialogs.
    • Hide

      Proposal should be rejected since it introduces significant incompatibilities with OSLC 2.0 without addressing any insurmountable problem.

      Show
      Proposal should be rejected since it introduces significant incompatibilities with OSLC 2.0 without addressing any insurmountable problem.

      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?

            Assignee:
            James Amsden (Inactive)
            Reporter:
            James Amsden (Inactive)
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: