|
Call for Statements of Use for OSLC Configuration Management 1.0
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
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
|
By
Jim Amsden
· #876
·
|
|
[oslc-op-pgb] Stepping down as a co-chair
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
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
|
By
Jim Amsden
· #872
·
|
|
Invitation to comment on OSLC Architecture Management Version 3.0 before call for consent as OASIS Standard - ends June 24
#publicreview
The review is over and no comment were received.
The review is over and no comment were received.
|
By
Jim Amsden
· #871
·
|
|
Link profiles
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
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
|
By
Jim Amsden
· #834
·
|
|
Link profiles
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
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
|
By
Jim Amsden
· #830
·
|
|
OSLC Linking Profile discussion tomorrow
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@...
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@...
|
By
Jim Amsden
· #817
·
|
|
Survey among OSLC TRS implementers
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
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
|
By
Jim Amsden
· #798
·
|
|
Request for SMV to promote OSLC Architecture Management Specification Version 3.0, PS01 to Candidate Oasis Standard
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
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
|
By
Jim Amsden
· #773
·
|
|
Errata in OSLC Quality Management Specification Version 2.1 OASIS Standard 19 January 2022
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
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
|
By
Jim Amsden
· #772
·
|
|
Call for Statements of Use for OSLC Architecture Management Specification Version 3.0
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
|
By
Jim Amsden
· #755
·
|
|
Call for Statements of Use for OSLC Architecture Management Specification Version 3.0
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
|
By
Jim Amsden
· #754
·
|
|
[OSLC forum] ClassCastException with Lyo 4.1
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:
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:
|
By
Jim Amsden
· #749
·
|
|
Are we ready for Architecture Management 3.0 COS?
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
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
|
By
Jim Amsden
· #738
·
|
|
[oslc-op-pgb] Formal notice of intent to publish OSLC Tracked Resource Set Version 3.0
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
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
|
By
Jim Amsden
· #732
·
|
|
Formal notice of intent to publish OSLC Tracked Resource Set Version 3.0
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 OSLC Tra
|
By
Jim Amsden
· #729
·
|
|
Formal notice of intent to publish OSLC Configuration Management Version 1.0
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:
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:
|
By
Jim Amsden
· #728
·
|
|
FW: Registration request for the Configuration-Context field
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
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
|
By
Jim Amsden
· #684
·
|
|
Is dcterms:description missing from the ResourceShape Shape?
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
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
|
By
Jim Amsden
· #651
·
|
|
RM Specs page
Both of those links look ok to me. -----oslc-op@... wrote: ----- To: "OASIS OSLC Open Project (oslc-op@...)" <oslc-op@...>
Both of those links look ok to me. -----oslc-op@... wrote: ----- To: "OASIS OSLC Open Project (oslc-op@...)" <oslc-op@...>
|
By
Jim Amsden
· #630
·
|
|
The 60-day public review of Core V3.0 PS02 and OSLC Query V3.0 PS01 has closed. No comments were received
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
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
|
By
Jim Amsden
· #610
·
|