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-16) Discovery should include text about vocabulary discovery

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

James Amsden commented on OSLCCORE-16:

The current proposal for v2 discovery compatibility is for ServiceProviderCatalog, ServiceProvider and Service to be subtypes of LDPCs. This extends LDPCs with OSLC2 property values, including oslc:domain. It unifies v2 and v3 discovery and provides a resolution for this issue. 

Closing this issue is pending a resolution of OSLCCORE-23, or some other proposed solution.

> Discovery should include text about vocabulary discovery
> --------------------------------------------------------
>                 Key: OSLCCORE-16
>                 URL: https://issues.oasis-open.org/browse/OSLCCORE-16
>             Project: OASIS OSLC Lifecycle Integration Core (OSLC Core) TC
>          Issue Type: Bug
>            Reporter: James Amsden
>            Assignee: Nick Crossley
>            Priority: Minor
> OSLC Core 3.0 defines common capabilities, protocols and resource types that are reused by OSLC domain specifications. The purpose of OSLC Discovery capabilities is to allow clients to determine what capabilities or services a server provides and adapt their interaction accordingly.
> OSLC domain specifications describe what OSLC core capabilities are required to support that domain, and specify any other capabilities and vocabularies that define the domain. It is highly desirable that these domain vocabularies be open and extensible to enable servers to provide the information needed to meet their business needs while doing so in a standard way. Therefore  the OSLC domain vocabularies could be seen as a specification of the minimum RDF classes and properties that a server is expected to support.
> OSLC Core 3.0 Discovery should specify the means for how clients could discover the actual vocabularies supported by a server implementing an OSLC domain in case they are able to make use of information provided beyond the minimum required to support the domain.

This message was sent by Atlassian JIRA

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