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

[OASIS Issues Tracker <workgroup_mailer@lists.oasis-open.org>]

    [ https://issues.oasis-open.org/browse/OSLCCORE-41?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=61069#comment-61069 ] 

Martin Pain commented on OSLCCORE-41:
-------------------------------------

So would this mean hiding resources where they explicitly specify oslc:instanceShape, or would you expect the clients to be doing something else to determine which resources to hide.

Although you didn't talk about hiding resources, you talked about hiding shapes or classes. Can you give an example of how report builders would use this?

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