Uploaded image for project: 'OASIS OSLC Lifecycle Integration Core (OSLC Core) TC'
  1. OASIS OSLC Lifecycle Integration Core (OSLC Core) TC
  2. OSLCCORE-15

Allow client to request different icon sizes for resource preview

    Details

    • Type: Improvement
    • Status: Applied
    • Priority: Minor
    • Resolution: Fixed
    • Component/s: None
    • Labels:
    • Proposal:
      Hide

      Extend the resource preview Prefer header to include an icon size parameter:
      Prefer: return=representation; include="http://open-services.net/ns/core#PreferCompact"; iconSize=48

      The server SHOULD return the an icon of the requested size, or the largest icon available that is smaller than the requested size.

      Note that the OSLC Compact resource shape icon property is zero-or-one, and has no size property. So the icons available are not currently discoverable. Changing a property from zero-or-one to zero-or-many would be OSLC2 client breaking because the client would be getting a collection of icon URIs when they are expecting one.

      If an OSLC2 client requests a Compact resource (or an OSLC3 client without a Prefer header), the Compact resource could contain zero-or-one icons with the default size of 16x16. So this would preserve compatibility, but would not allow the available icon sizes to be discoverable.

      Show
      Extend the resource preview Prefer header to include an icon size parameter: Prefer: return=representation; include="http://open-services.net/ns/core#PreferCompact"; iconSize=48 The server SHOULD return the an icon of the requested size, or the largest icon available that is smaller than the requested size. Note that the OSLC Compact resource shape icon property is zero-or-one, and has no size property. So the icons available are not currently discoverable. Changing a property from zero-or-one to zero-or-many would be OSLC2 client breaking because the client would be getting a collection of icon URIs when they are expecting one. If an OSLC2 client requests a Compact resource (or an OSLC3 client without a Prefer header), the Compact resource could contain zero-or-one icons with the default size of 16x16. So this would preserve compatibility, but would not allow the available icon sizes to be discoverable.

      Description

      In OSLC Core 2.0, the icon referenced from a compact resource SHOULD be 16x16 pixels. In the current OSLC 3.0 draft, this recommendation is removed, and the size is unspecified.

      The OSLC 2.0 approach is too restrictive, and the OSLC 3.0 approach too vague. The client should have some way of suggesting the desired size.

      OSLC3 should provide some means for the client to request a specific icon size for resource preview.

        Attachments

          Activity

            People

            • Assignee:
              Unassigned
              Reporter:
              ndjc Nick Crossley
            • Watchers:
              3 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: