OSLC 2020 Reference Implementation ready for review
Hello,
I am glad to submit finished OSLC 2020 Reference Implementation for your review and approval following the work we've done under the PGB contract: https://github.com/oslc-op/refimpl/tree/v0.2.0 We are ready to present it at the next scheduled PGB meeting. -- Best regards, Andrew
|
||||||||||
|
||||||||||
OSLC4TDB project
Hi,
Did anyone hear about https://github.com/ld4mbse/oslc4tdb before? Seems like something new Axel and Mario are working on. Axel, will be glad to see a demo and discuss when you are ready! -- Best regards, Andrew
|
||||||||||
|
||||||||||
Re: Handling a GET request that depends on client paramters
Nick Crossley <nick_crossley@...>
The URI for a single
resource with parameterized results could be one with the query string
included - this might be appropriate if the response was repeatable for
the same query string. Or it could be a unique URI including a hash of
the query string, which might be appropriate if the results were not repeatable
(for example, if the embedded query is something involving a time period
relative to the current time).
Nick. From: Jad El-Khoury <jad@...> To: Nicholas Crossley <nick_crossley@...>, "oslc-op@..." <oslc-op@...> Date: 11/03/2020 07:44 AM Subject: [EXTERNAL] RE: [oslc-op] Handling a GET request that depends on client paramters I considered using an OSLC Query. The problem though is that the response is a query...
I considered using an OSLC Query. The problem though is that the response is a query result. So the client cannot simply link to that. It needs to get it’s first member (The client knows that the response has exactly one member)
Even so, the query response will consist of a set (or one) of resource URLs. We are back to square one: What should the URL for these resources be?
regards ______________________________ Jad El-khoury, PhD KTH Royal Institute of Technology School of Industrial Engineering and Management, Mechatronics Division Brinellvägen 83, SE-100 44 Stockholm, Sweden Phone: +46(0)8 790 6877 Mobile: +46(0)70 773 93 45
From:Nicholas Crossley <nick_crossley@...>
It
seems that following OSLC Query here might be appropriate if the resources
in question are a key part of your application.
Hi
It would be appreciated to hear from the OSLC experts, if you have any advice on this topic https://forum.open-services.net/t/handling-a-get-request-that-depends-on-client-paramters/424
regards ______________________________ Jad El-khoury, PhD KTH Royal Institute of Technology School of Industrial Engineering and Management, Mechatronics Division Brinellvägen 83, SE-100 44 Stockholm, Sweden Phone: +46(0)8 790 6877 Mobile: +46(0)70 773 93 45
|
||||||||||
|
||||||||||
Re: Handling a GET request that depends on client paramters
Jad El-Khoury
I considered using an OSLC Query. The problem though is that the response is a query result. So the client cannot simply link to that. It needs to get it’s first member (The client knows that the response has exactly one member)
Even so, the query response will consist of a set (or one) of resource URLs. We are back to square one: What should the URL for these resources be?
regards ______________________________ Jad El-khoury, PhD KTH Royal Institute of Technology School of Industrial Engineering and Management, Mechatronics Division Brinellvägen 83, SE-100 44 Stockholm, Sweden Phone: +46(0)8 790 6877 Mobile: +46(0)70 773 93 45
From: Nicholas Crossley <nick_crossley@...>
It seems that following OSLC Query here might be appropriate if the resources in question are a key part of your application.
Hi
It would be appreciated to hear from the OSLC experts, if you have any advice on this topic https://forum.open-services.net/t/handling-a-get-request-that-depends-on-client-paramters/424
regards ______________________________ Jad El-khoury, PhD KTH Royal Institute of Technology School of Industrial Engineering and Management, Mechatronics Division Brinellvägen 83, SE-100 44 Stockholm, Sweden Phone: +46(0)8 790 6877 Mobile: +46(0)70 773 93 45
|
||||||||||
|
||||||||||
Re: CCM Primer
Jad El-Khoury
Hi David
I am afraid that an agnostic approach in the primer may make the primer as generic as the specs. One suggestion would be to take one specific versioning model, and demonstrate the specs through that. Hypothesis: if I can understand the OSLC CCM concepts by relating them to a common & familiar versioning model, then I can apply these concepts to my specific versioning model.
regards ______________________________ Jad El-khoury, PhD KTH Royal Institute of Technology School of Industrial Engineering and Management, Mechatronics Division Brinellvägen 83, SE-100 44 Stockholm, Sweden Phone: +46(0)8 790 6877 Mobile: +46(0)70 773 93 45
From: David Honey1 <DavidHoney@...>
I don't think that the OSLC Configuration Management specification makes any statements about how versioning is implemented, whether parallel versioning is supported, how merging
of parallels might be implemented etc. The spec says this about versioned resources:
Hej
David started, and I merged some initial content on the CCM Primer we started discussing on Thursday. https://github.com/oslc-op/oslc-specs/blob/master/notes/ccm-primer/ccm-primer.md
It would be a good first step if we can explain linear versioning to start with. I put together a very rough explanation, based on how I understood part 2 of the specs. The text is rough, but I hope it is good enough to raise all the questions we want to answer in this section.
If someone can help me understand it better, I would be very happy to further refine the text.
We can then tackle more advanced scenarios.
regards ______________________________ Jad El-khoury, PhD KTH Royal Institute of Technology School of Industrial Engineering and Management, Mechatronics Division Brinellvägen 83, SE-100 44 Stockholm, Sweden Phone: +46(0)8 790 6877 Mobile: +46(0)70 773 93 45
|
||||||||||
|
||||||||||
Re: Handling a GET request that depends on client paramters
Nick Crossley <nick_crossley@...>
It seems that following
OSLC Query here might be appropriate if the resources in question are a
key part of your application.
But if you want a lighter-weight solution, I see nothing in OSLC that prevents use of query strings on any GET request, and having a response that varies according to that request, without necessarily satisfying the full OSLC Query spec. Nick. From: "Jad El-Khoury" <jad@...> To: "OASIS OSLC Open Project (oslc-op@...)" <oslc-op@...> Date: 11/03/2020 07:23 AM Subject: [EXTERNAL] [oslc-op] Handling a GET request that depends on client paramters Sent by: oslc-op@... Hi It would be appreciated to hear from the OSLC experts, if you have any advice on...
Hi
It would be appreciated to hear from the OSLC experts, if you have any advice on this topic https://forum.open-services.net/t/handling-a-get-request-that-depends-on-client-paramters/424
regards ______________________________ Jad El-khoury, PhD KTH Royal Institute of Technology School of Industrial Engineering and Management, Mechatronics Division Brinellvägen 83, SE-100 44 Stockholm, Sweden Phone: +46(0)8 790 6877 Mobile: +46(0)70 773 93 45
|
||||||||||
|
||||||||||
Handling a GET request that depends on client paramters
Jad El-Khoury
Hi
It would be appreciated to hear from the OSLC experts, if you have any advice on this topic https://forum.open-services.net/t/handling-a-get-request-that-depends-on-client-paramters/424
regards ______________________________ Jad El-khoury, PhD KTH Royal Institute of Technology School of Industrial Engineering and Management, Mechatronics Division Brinellvägen 83, SE-100 44 Stockholm, Sweden Phone: +46(0)8 790 6877 Mobile: +46(0)70 773 93 45
|
||||||||||
|
||||||||||
Re: CCM Primer
David Honey1 <DavidHoney@...>
I don't think that
the OSLC Configuration Management specification makes any statements about
how versioning is implemented, whether parallel versioning is supported,
how merging of parallels might be implemented etc. The spec says this about
versioned resources:
A versioned resource server MAY support the following operations on version resources: [CONFIG-21]
There are a lot of MAYs in this. In short, there is no mechanism described for creating new versions other than a PUT, and even so, that might not create a new version. There is no mention of parallel versions or branching. I think this is intentional. There are are many versioning tools that provide differing version models. For example, some tools provide specific file versions. Tools like SVN don't version individual files; rather they version the whole repository. Some tools support explicit branching and others do not. Some tools support versioning of directories/folders and others do not. Some tools support true configurations while others only support tagging. So the spec wisely avoids defining versioning models. Given the primer is meant to be a partner document to the spec, I think it should take a similar agnostic approach. David. From: "Jad El-Khoury" <jad@...> To: "OASIS OSLC Open Project (oslc-op@...)" <oslc-op@...> Date: 02/11/2020 22:45 Subject: [EXTERNAL] [oslc-op] CCM Primer Sent by: oslc-op@... Hej David started, and I merged some initial content on the CCM Primer we started...
Hej
David started, and I merged some initial content on the CCM Primer we started discussing on Thursday. https://github.com/oslc-op/oslc-specs/blob/master/notes/ccm-primer/ccm-primer.md
It would be a good first step if we can explain linear versioning to start with. I put together a very rough explanation, based on how I understood part 2 of the specs. The text is rough, but I hope it is good enough to raise all the questions we want to answer in this section.
If someone can help me understand it better, I would be very happy to further refine the text.
We can then tackle more advanced scenarios.
regards ______________________________ Jad El-khoury, PhD KTH Royal Institute of Technology School of Industrial Engineering and Management, Mechatronics Division Brinellvägen 83, SE-100 44 Stockholm, Sweden Phone: +46(0)8 790 6877 Mobile: +46(0)70 773 93 45
Unless stated otherwise above: IBM United Kingdom Limited - Registered in England and Wales with number 741598. Registered office: PO Box 41, North Harbour, Portsmouth, Hampshire PO6 3AU
|
||||||||||
|
||||||||||
CCM Primer
Jad El-Khoury
Hej
David started, and I merged some initial content on the CCM Primer we started discussing on Thursday. https://github.com/oslc-op/oslc-specs/blob/master/notes/ccm-primer/ccm-primer.md
It would be a good first step if we can explain linear versioning to start with. I put together a very rough explanation, based on how I understood part 2 of the specs. The text is rough, but I hope it is good enough to raise all the questions we want to answer in this section.
If someone can help me understand it better, I would be very happy to further refine the text.
We can then tackle more advanced scenarios.
regards ______________________________ Jad El-khoury, PhD KTH Royal Institute of Technology School of Industrial Engineering and Management, Mechatronics Division Brinellvägen 83, SE-100 44 Stockholm, Sweden Phone: +46(0)8 790 6877 Mobile: +46(0)70 773 93 45
|
||||||||||
|
||||||||||
Re: Can't make today's oslc-op telecon
Jad El-Khoury
Jim
Concerning the SysML v2 OSLC PSM, I was at the call today.
The current Sysml specs only covers basic versioning, but they do seem have plans to have a more complete Config. Specs. (Not clear though how far they plan to go).
Given the discussions on the CCM Primer, I’m pretty sure we can support versioning in the Sysml implementation, with little guidance from the OSLC team. Ian offered today some help to get me started.
That’s at the least. And then we can reference the CCM specs. This way, we are at least at the same pace as the Sysml API.
regards ______________________________ Jad El-khoury, PhD KTH Royal Institute of Technology School of Industrial Engineering and Management, Mechatronics Division Brinellvägen 83, SE-100 44 Stockholm, Sweden Phone: +46(0)8 790 6877 Mobile: +46(0)70 773 93 45
From: oslc-op@... <oslc-op@...>
On Behalf Of Jim Amsden
Due to time change, the oslc-op call overlaps with customer calls, same with the SysML Track 5 call.
My status: I have made some progress on updating the automation spec. I will split the vocab and shapes into two documents because we may want to publish the vocab and shapes for Automation to open-services.net.
We are probably close to ready to send out the call for statements of use once we verify all the specs in scope have: 1. published PS revisions: RM, CM, QM, Query, Core. 2. finalized the email 3. determine who we want to send the emal to
SysML Things to consider:
1. Relevant OSLC specifications - a Configuration Management PS01 would be ideal PSD01 minimally required
2. Reference SysML OSLC implementation - will not support versioning becase 1) not supported by eclipse/Lyo, 2) not supported by Lyo Designer, and 3) not supported by Lyo/Store.
3. What is delivered to OMG SysML v2 OSLC PSM initial submission. With the reference implementation created by Lyo Designer, we can generate Swagger.io for the non-versioning OSLC server. We could explore ways to generate Swaggger.io from JavaDoc, or directly from the spec vocab and shape files. Or we could simply reference the Configuration Mangement spec in the SysML initial submission and indicate the OSLC PSM must follow that specification. This may be approproate given that the config spec isn't complete at this time.
|
||||||||||
|
||||||||||
Re: OP note
Chet Ensign
Yep, I see no problem with that. I'll revisit those parts of the rules but I see nothing to block you producing Project Notes the same as a Committee Note from a TC. /chet
On Thu, Oct 29, 2020 at 10:28 AM Andrii Berezovskyi <andriib@...> wrote: Hello Chet, --
/chet ---------------- Chet Ensign Chief Technical Community Steward OASIS: Advancing open source & open standards for the information society http://www.oasis-open.org Mobile: +1 201-341-1393
|
||||||||||
|
||||||||||
Statements of Use for OSLC Core 3.0 PS01
Hello, The OSLC Core Version 3.0 Project Specification 01 represents a milestone in the standardization process for open-services.net specifications. This revision incorporates the insight gained from many implementations, integrations with other lifecycle management tools, and user experience, while maintaining compatibility with open-services.net OSLC specification. Implementations of these earlier OSLC specifications are therefore applicable for Statements of Use for OSLC Core Version 3.0 Project Specification 01. The OASIS OSLC Open Project welcomes all implementers to submit Statements of Use for this specification. This is an essential part of the OASIS standardization process and will enable us to progress from Project Specification (PS) to Candidate OASIS Standard (COS) and eventually to OASIS Standard. Please see Section 8 of the OP handbook for more information. We need your help to gather 3 statements for each spec for it to progress to the Candidate OASIS Standard stage. To submit a statement, please send a simple declaration to the oslc-op@... (this mailing list) that your organisation has successfully used or implemented that specification in accordance with all or some of its conformance clauses, identifying those clauses that apply, and stating whether its use included the interoperation of multiple independent implementations (reference). A typical statement of use could be:
Please remember that if your company is an OASIS Organizational Member, a Statement of Use must be endorsed by the Organizational Member's Primary Representative. Best regards,
|
||||||||||
|
||||||||||
Statements of Use for OSLC CM 3.0 PS01
Hello, The OSLC Change Management Version 3.0 Project Specification 01 represents a milestone in the standardization process for open-services.net specifications. This revision incorporates the insight gained from many implementations, integrations with other lifecycle management tools, and user experience, while maintaining compatibility with open-services.net OSLC specification. Implementations of these earlier OSLC specifications are therefore applicable for Statements of Use for OSLC Change Management Version 3.0 Project Specification 01. The OASIS OSLC Open Project welcomes all implementers to submit Statements of Use for this specification. This is an essential part of the OASIS standardization process and will enable us to progress from Project Specification (PS) to Candidate OASIS Standard (COS) and eventually to OASIS Standard. Please see Section 8 of the OP handbook for more information. We need your help to gather 3 statements for each spec for it to progress to the Candidate OASIS Standard stage. To submit a statement, please send a simple declaration to the oslc-op@... (this mailing list) that your organisation has successfully used or implemented that specification in accordance with all or some of its conformance clauses, identifying those clauses that apply, and stating whether its use included the interoperation of multiple independent implementations (reference). A typical statement of use could be:
Please remember that if your company is an OASIS Organizational Member, a Statement of Use must be endorsed by the Organizational Member's Primary Representative. Best regards,
|
||||||||||
|
||||||||||
Statements of Use for OSLC RM 2.1 PS01
Hello, The OSLC Requirements Management Version 2.1 Project Specification 01 represents a milestone in the standardization process for open-services.net specifications. This revision incorporates the insight gained from many implementations, integrations with other lifecycle management tools, and user experience, while maintaining compatibility with open-services.net OSLC specification. Implementations of these earlier OSLC specifications are therefore applicable for Statements of Use for OSLC Requirements Management Version 2.1 Project Specification 01. The OASIS OSLC Open Project welcomes all implementers to submit Statements of Use for this specification. This is an essential part of the OASIS standardization process and will enable us to progress from Project Specification (PS) to Candidate OASIS Standard (COS) and eventually to OASIS Standard. Please see Section 8 of the OP handbook for more information. We need your help to gather 3 statements for each spec for it to progress to the Candidate OASIS Standard stage. To submit a statement, please send a simple declaration to the oslc-op@... (this mailing list) that your organisation has successfully used or implemented that specification in accordance with all or some of its conformance clauses, identifying those clauses that apply, and stating whether its use included the interoperation of multiple independent implementations (reference). A typical statement of use could be:
Please remember that if your company is an OASIS Organizational Member, a Statement of Use must be endorsed by the Organizational Member's Primary Representative. Best regards,
|
||||||||||
|
||||||||||
Statements of Use for OSLC QM 2.1 PS01
Hello, The OSLC Quality Management Version 2.1 Project Specification 01 represents a milestone in the standardization process for open-services.net specifications. This revision incorporates the insight gained from many implementations, integrations with other lifecycle management tools, and user experience, while maintaining compatibility with open-services.net OSLC specification. Implementations of these earlier OSLC specifications are therefore applicable for Statements of Use for OSLC Quality Management Version 2.1 Project Specification 01. The OASIS OSLC Open Project welcomes all implementers to submit Statements of Use for this specification. This is an essential part of the OASIS standardization process and will enable us to progress from Project Specification (PS) to Candidate OASIS Standard (COS) and eventually to OASIS Standard. Please see Section 8 of the OP handbook for more information. We need your help to gather 3 statements for each spec for it to progress to the Candidate OASIS Standard stage. To submit a statement, please send a simple declaration to the oslc-op@... (this mailing list) that your organisation has successfully used or implemented that specification in accordance with all or some of its conformance clauses, identifying those clauses that apply, and stating whether its use included the interoperation of multiple independent implementations (reference). A typical statement of use could be:
Please remember that if your company is an OASIS Organizational Member, a Statement of Use must be endorsed by the Organizational Member's Primary Representative. Best regards,
|
||||||||||
|
||||||||||
OP note
Hello Chet,
Can the OP release an OP note similar to https://www.w3.org/TR/rdf11-primer/ without going through PSD..OS process? I think we have such flag in ReSpec but no mention of it under https://www.oasis-open.org/oasis-open-projects-handbook#progression-of-work -- Best regards, Andrew
|
||||||||||
|
||||||||||
oslc-op Weekly Contributors Meeting - Thu, 10/29/2020
#cal-notice
oslc-op@lists.oasis-open-projects.org Calendar <noreply@...>
oslc-op Weekly Contributors Meeting When: Where: Organizer: Description: One tap audio Dial In: +15124022718,,,,2979764690# (US) or +498938038719,,,,2979764690# (Germany) Looking for a different dial in number? Please see: https://meet.jit.si/static/dialInInfo.html?room=oslc-op Meeting ID: 2979764690#
The meeting minutes are edited in https://hackmd.io/@driib/oslc-op-minutes/edit
Previous minutes can be found under https://github.com/oslc-op/oslc-admin/tree/master/minutes/2019 OASIS OSLC Open Project group home: https://lists.oasis-open-projects.org/g/oslc-op oslc-op GitHub Organization: https://github.com/oslc-op Mailing list: oslc-op@... (archives: https://lists.oasis-open-projects.org/g/oslc-op)
|
||||||||||
|
||||||||||
Can't make today's oslc-op telecon
Due to time change, the oslc-op call overlaps with customer calls, same with the SysML Track 5 call. My status: I have made some progress on updating the automation spec. I will split the vocab and shapes into two documents because we may want to publish the vocab and shapes for Automation to open-services.net. We are probably close to ready to send out the call for statements of use once we verify all the specs in scope have: 1. published PS revisions: RM, CM, QM, Query, Core. 2. finalized the email 3. determine who we want to send the emal to SysML Things to consider: 1. Relevant OSLC specifications - a Configuration Management PS01 would be ideal PSD01 minimally required 2. Reference SysML OSLC implementation - will not support versioning becase 1) not supported by eclipse/Lyo, 2) not supported by Lyo Designer, and 3) not supported by Lyo/Store. 3. What is delivered to OMG SysML v2 OSLC PSM initial submission. With the reference implementation created by Lyo Designer, we can generate Swagger.io for the non-versioning OSLC server. We could explore ways to generate Swaggger.io from JavaDoc, or directly from the spec vocab and shape files. Or we could simply reference the Configuration Mangement spec in the SysML initial submission and indicate the OSLC PSM must follow that specification. This may be approproate given that the config spec isn't complete at this time.
|
||||||||||
|
||||||||||
Re: Link to today's meeting
Jad El-Khoury
Hej
I can’t yet see the changes under “contribute”. Don’t like TimBL’s photo? You can use mine.
For the meetings, I haven’t seen an “invite” since we moved to OP. If there is a proper calender invite, then the time zone doesn’t matter. Most mail/calendar clients can handle it properly.
regards ______________________________ Jad El-khoury, PhD KTH Royal Institute of Technology School of Industrial Engineering and Management, Mechatronics Division Brinellvägen 83, SE-100 44 Stockholm, Sweden Phone: +46(0)8 790 6877 Mobile: +46(0)70 773 93 45
From: Andrii Berezovskyi <andriib@...>
Hello,
Jad, good catch! I have done the updates to the page: https://github.com/oslc-op/website/commits/master. I also updated the text a bit on https://open-services.net/contribute/ under "Working Groups" but would be better to try merging the info in the README into the page. Also, how did a photo of TimBL end up there?!
Regarding the meeting today, I suggested many times to use a UTC invite but Jim sets it up in US Eastern. Today we will meet at 14:00 UTC: https://www.timeanddate.com/worldclock/fixedtime.html?msg=OSLC+OP+call+W44&iso=20201029T14&p1=1440&ah=1
-- Best regards, Andrew
|
||||||||||
|
||||||||||
Re: Link to today's meeting
Hello,
toggle quoted messageShow quoted text
Jad, good catch! I have done the updates to the page: https://github.com/oslc-op/website/commits/master. I also updated the text a bit on https://open-services.net/contribute/ under
"Working Groups" but would be better to try merging the info in the README into the page. Also, how did a photo of TimBL end up there?!
Regarding the meeting today, I suggested many times to use a UTC invite but Jim sets it up in US Eastern. Today we will meet at 14:00 UTC: https://www.timeanddate.com/worldclock/fixedtime.html?msg=OSLC+OP+call+W44&iso=20201029T14&p1=1440&ah=1
--
Best regards,
Andrew
|
||||||||||
|