Next in thread → Next in month →

[OASIS Issue Tracker] (OSLCCORE-41) Extend use of oslc:hidden to suggest that entire shapes be hidden from the UI

From
OASIS Issues Tracker <>
Date
2015-10-14T14:00:58+00:00
ID
Thread
[OASIS Issue Tracker] (OSLCCORE-41) Extend use of oslc:hidden to suggest that entire shapes be hidden from the UI
[ https://issues.oasis-open.org/browse/OSLCCORE-41?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=61072#comment-61072 ] 

James Amsden commented on OSLCCORE-41:
--------------------------------------

I created a Wiki page to capture some of the potential overlap and incompatibilities between OSLC and LDP, including a section on constraints: https://wiki.oasis-open.org/oslc-core/OslcAndLdp#preview.

> Extend use of oslc:hidden to suggest that entire shapes be hidden from the UI
> -----------------------------------------------------------------------------
>
>                 Key: OSLCCORE-41
>                 URL: https://issues.oasis-open.org/browse/OSLCCORE-41
>             Project: OASIS OSLC Lifecycle Integration Core (OSLC Core) TC
>          Issue Type: Bug
>            Reporter: Nick Crossley
>            Assignee: Nick Crossley
>            Priority: Minor
>
> The predicate oslc:hidden is currently used within oslc:PropertyDefinition resources to mark a given property of a shape as something to be hidden from the normal UI.
> There is no currently well-defined way to suggest that an entire shape (or classes using that shape) be hidden from a UI. Such a property would be useful for report builders, to hide classes that are a supporting part of the representation of some top-level type and not intended for primary querying.



--
This message was sent by Atlassian JIRA
(v6.2.2#6258)
Next in thread → Next in month →