[OASIS Issue Tracker] (OSLCCORE-38) Create a Quickstart guide for OSLC

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

     [ https://issues.oasis-open.org/browse/OSLCCORE-38?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Jim Ruehlin updated OSLCCORE-38:
--------------------------------

    Description: 
The information in the OSLC specifications is necessarily robust enough to build an entire OSLC implementation. However, many people adopting OSLC will only implement "just enough" OSLC to address their needs, or they may only be consuming a limited amount of data from an OSLC provider. Review the detailed specifications and understanding the underlying technology and semantics (RDF, LDP, etc) is a lot to ask from these types of OSLC users. 

It would be helpful, and encourage wider adoption, to provide some form of quickstart guide that helps potential OSLC consumers get just enough information to help them with simple or common integration scenarios. Such a document would also be useful for anyone just starting with OSLC to guide them on where to go for a deeper understanding of OSLC. This guide should be no longer than 3 pages, and the shorter the better.

For example, such a guide could provide:
   * Specific examples of common ways to query information in OSLC servers.
   * A list of things OSLC should be used for, and a list of things OSLC can't be used for.
   * The location of OSLC documents and the relationship between OASIS and open-services.net.
   * An introduction to Lyo.
   * etc.



  was:
The information in the OSLC specifications is necessarily robust enough to build an entire OSLC implementation. However, many people adopting OSLC will only implement "just enough" OSLC to address their needs, or they may only be consuming a limited amount of data from an OSLC provider. Review the detailed specifications and understanding the underlying technology and semantics (RDF, LDP, etc) is a lot to ask from these types of OSLC users. 



       Proposal:   (was: It would be helpful, and encourage wider adoption, to provide some form of quickstart guide that helps potential OSLC consumers get just enough information to help them with simple or common integration scenarios. Such a document would also be useful for anyone just starting with OSLC to guide them on where to go for a deeper understanding of OSLC. This guide should be no longer than 3 pages, and the shorter the better.

For example, such a guide could provide:
   * Specific examples of common ways to query information in OSLC servers.
   * A list of things OSLC should be used for, and a list of things OSLC can't be used for.
   * The location of OSLC documents and the relationship between OASIS and open-services.net.
   * An introduction to Lyo.
   * etc.)

> Create a Quickstart guide for OSLC
> ----------------------------------
>
>                 Key: OSLCCORE-38
>                 URL: https://issues.oasis-open.org/browse/OSLCCORE-38
>             Project: OASIS OSLC Lifecycle Integration Core (OSLC Core) TC
>          Issue Type: Task
>            Reporter: Jim Ruehlin
>            Assignee: James Amsden
>
> The information in the OSLC specifications is necessarily robust enough to build an entire OSLC implementation. However, many people adopting OSLC will only implement "just enough" OSLC to address their needs, or they may only be consuming a limited amount of data from an OSLC provider. Review the detailed specifications and understanding the underlying technology and semantics (RDF, LDP, etc) is a lot to ask from these types of OSLC users. 
> It would be helpful, and encourage wider adoption, to provide some form of quickstart guide that helps potential OSLC consumers get just enough information to help them with simple or common integration scenarios. Such a document would also be useful for anyone just starting with OSLC to guide them on where to go for a deeper understanding of OSLC. This guide should be no longer than 3 pages, and the shorter the better.
> For example, such a guide could provide:
>    * Specific examples of common ways to query information in OSLC servers.
>    * A list of things OSLC should be used for, and a list of things OSLC can't be used for.
>    * The location of OSLC documents and the relationship between OASIS and open-services.net.
>    * An introduction to Lyo.
>    * etc.



--
This message was sent by Atlassian JIRA
(v6.2.2#6258)