[example:] OSLC should be limited on engineering environments and not be used in IoT target environments because …
the underlying concept of OSLC LDP (Linked Data Platform, see…) is very well suited to be used in IoT target systems
2. Ownership of ‘open-services.net’ [RE] 2016/02/12
currently open-services.net is owned by IBM
specification name spaces depend on open-services.net
Q1: should the OSLC community seek ownership?
Q2: can it be owned by OASIS-OSLC?
Q3: can it be funded by OASIS-OSLC funding?
We need a communication plan / strategy to point interested people to the right content on the right web site
open-services.net should be the “community web site” for the entire OSLC ecosystem
what content needs to be there?
who owns the web site (see topic above) / who pays for it (incl. webmaster, etc.)
3. Executing on the vision [WC] 2016/07/03
The OSLC vision statement paints a compelling picture of how systems should integrate and the necessary standards that need to be in place. Not sure if this belongs in the vision statement, but should we describe in more detail how we envision executing on the next phase? What are the specific outcomes that are desired? Do we need a certain threshold of industry adoption to realize this vision or is it sufficient for the spec to be available for those who want to use it? How to we ensure there is incentive for the community to contribute to the envisioned standards and adopt them? Will OSLC prioritize certain domains over others? This next level of detail will help focus the efforts of the OSLC-MS to achieve this vision.
n. topic template [initals] datecopy this template and change number, initials and date