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-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=61071#comment-61071 ] 

James Amsden commented on OSLCCORE-41:

This feels a little like model/view coupling. Generally the MVC architecture uses the controller as a mediator between models and views, allowing each to be more reusable and less coupled. Note that such mediation patterns might be a useful way to use OSLC to integrate different domains, using things like bridge ontologies, that avoid adding coupling to each domain. 

The counter argument is that a shape could be used to provide metadata to more reflective controllers. Since the same vocabulary can be constrained by different shapes in different contexts, this doesn't actually overly constrain the vocabulary, or necessarily create undesirable coupling. Shapes associated with data validation and shapes associated with UI controls could be completely separate, or even arranged in a hierarchy.

So I think this is a simple, good, and useful proposal. However, oslc:hidden is currently not supported on properties or shapes in the current SHACL draft. Not sure if this was intentional or what the reasoning would be.

> 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

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