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-10) Normalizing Preview and Dialog

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

Martin Pain  commented on OSLCCORE-10:

I think my point about DelegatedUIDescriptor with oslc:dialog being inconsistent is that in the type name we're calling it "delegated UI" and in the predicate we're calling it "dialog". So I would prefer DelegatedUiDescriptor and oslc:document.

And then dialogs-v3.html would be delegated-ui-v3.html.

However, this would mean a new RDF class rather than reusing the v2 DialogDescriptor, just to satisfy my pedantry...

But then again the descriptor could always have "rdf:type oslc:DelegatedUIDescriptor, oslc:DialogDescriptor" for dialogs and "rdf:type oslc:DelegatedUIDescriptor, oslc:Preview" (or whatever the correct type is) for previews. That might be a good thing, as only dialogs (creation, selection) support returning a URL via postMessage - so it might be a good thing to distinguish them in the descriptors' RDF.

> Normalizing Preview and Dialog
> ------------------------------
>                 Key: OSLCCORE-10
>                 URL: https://issues.oasis-open.org/browse/OSLCCORE-10
>             Project: OASIS OSLC Lifecycle Integration Core (OSLC Core) TC
>          Issue Type: Bug
>            Reporter: James Amsden
>            Assignee: James Amsden
>            Priority: Minor
> Resource-preview uses Compact, Preview and oslc:document to manage previews. Compact defines the preview descriptor and contains properties for small and large previews. Preview contains the size hings and oslc:document link to the actual HTML preview dialog.
> Dialogs-v3 uses Dialog and oslc:dialog with different Link headers for the creationDialog and selectionDialog. 
> Should we consider normalizing these different approaches to dialog management?

This message was sent by Atlassian JIRA

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