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

James Amsden commented on OSLCCORE-16:

See https://wiki.oasis-open.org/oslc-core/Discovery which says "In V2, things were organized by oslc:Service which was chained by a unique oslc:domain. In addition to this, there were resource types, shapes and usages associated with various creation, query and dialog capability. All these things, while made to work, provided for a web of relationships and concepts that made it had to navigate and use. To fix some of this, one approach is just to say things are done based on the type of resources they support."

This could be similar to the discussion we had on (somewhat) static/document centric discovery in V2 vs. incremental/dynamic discovery in v3. V2 allowed you do get the domain link from Service.domain. V3 lets you get the supported RDF resource types from the LPD container that supports them. The difference is that V2 provides a place for the server to advertise its supported domain vocabularies in the Service Provider Document, as well as the individual domain vocabulary classes in a Service (container). V3 only does the latter.

If we address the 2.0/3.0 compatibility issue, that will automatically resolve this issue.

> 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: James Amsden
>            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]