OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.

 


Help: OASIS Mailing Lists Help | MarkMail Help

oslc-core message

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]


Subject: [OASIS Issue Tracker] (OSLCCORE-15) Allow client to request different icon sizes for resource preview


     [ https://issues.oasis-open.org/browse/OSLCCORE-15?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Nick Crossley updated OSLCCORE-15:
----------------------------------

    Proposal: 
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.

One way to achieve this would be to allow another parameter on the Prefer: return=representation; include="http://open-services.net/ns/core#PreferCompact"; header:

Prefer: return=representation; include="http://open-services.net/ns/core#PreferCompact";; iconSize=48

  was:
One way to achieve this would be to allow another parameter on the Prefer: return=representation; include="http://open-services.net/ns/core#PreferCompact"; header:

Prefer: return=representation; include="http://open-services.net/ns/core#PreferCompact";; size=48


> Allow client to request different icon sizes for resource preview
> -----------------------------------------------------------------
>
>                 Key: OSLCCORE-15
>                 URL: https://issues.oasis-open.org/browse/OSLCCORE-15
>             Project: OASIS OSLC Lifecycle Integration Core (OSLC Core) TC
>          Issue Type: Improvement
>            Reporter: Nick Crossley
>            Priority: Minor
>
> 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. 



--
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]