The OSLC Open Project (OSLC-OP) has recently published Project Specification OSLC Configuration Management Version 1.0, revision 01. The OSLC-OP believes the specification is stable, and covers the fe

Andrew, Your contribution to OSLC over these last 7 years has been immeasurable. Your contributions include: Eclipse/lyo committer, keeping Eclipse/lyo alive and well, development of Lyo/Designer, ref

The review is over and no comment were received.

#publicreview

I am specifically not proposing to store backlinks. What I’m suggesting is that which link is the forward link depends on the use case the servers are trying to support. So rather I’m proposing using

This is a good start, but we should understand how it supports the use cases and common practice. On the issues we’ve been discussing on links: the OSLC specifications define vocabularies and shapes t

Andrew, Agree in principle, but I want to be sure we maintain focus on getting TRS and Configuration Management specs moved to OASIS Standard too, at least as best we can. From: <oslc-op@...

Agree, can you add your comment to the issue? From: <oslc-op@...> on behalf of David Honey2 <david.honey@...> Reply-To: "oslc-op@..." <oslc-op@l

The oslc-op wishes to request a Special Majority Vote for the PGB to approve the OSLC Open Project Architecture Management 3.0 Specification, Project Specification revision 01 as a Candidate OASIS Sta

Chet, We discovered a copy/paste mistake in one of the above specification’s additional components files. File quality-management-shapes.ttl contains: :TestResultShape a oslc:ResourceShape ; oslc:desc

The OSLC Open Project Architecture Management 3.0 Specification, revision 01 has reached Candidate OASIS Standard. This revision incorporates the insight gained from many implementations, integrations

The OSLC Open Project Architecture Management 3.0 Specification, revision 01 has reached Candidate OASIS Standard. This revision incorporates the insight gained from many implementations, integrations

Ian would know, but I don’t think so. That would be a reasonable instantiation of the Composite pattern, but I don’t think much subclassing was done because it’s not supported by ResourceShapes. From:

OSLC Architecture Management 3.0 is currently an oslc-op Project Specification since September 2021. There are multiple implementations by many vendors, an example implementation in iotp-adapter and p

Looking at the TRS 2.0 spec, the namespaces are http://open-services.net/ns/core/trs# as TRS was originally part of OSLC Core. These cannot be changed as there are existing implementations. -----"Andr

Dear PGB members, The rules require us to notify you at least 14 days before submitting the ballots for the spec drafts publication. We are hereby notifying you of the OP intention to publish OSLC Tra

Dear PGB members, The rules require us to notify you at least 14 days before submitting the ballots for the spec drafts publication. We are hereby notifying you of the OP intention to publish Subject:

I take this as excellent advice and guidance, but its too late for us to follow that guidance. There are lots of headers that have generic names. I actually think that can lead to flexible use of the

Raise an issue and we'll do it in a revision once there are enough issues or new content to justify one. -----oslc-op@... wrote: ----- To: "Jad El-Khoury" <jad@...>, "oslc

Both of those links look ok to me. -----oslc-op@... wrote: ----- To: "OASIS OSLC Open Project (oslc-op@...)" <oslc-op@...>

Please note that the 60-day public review for OSLC Core Version 3.0 PS02 and OSLC Query Version 3.0 PS01 announced on 09 June 2021 in https://lists.oasis-open.org/archives/members/202106/msg00008.html