OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.


Help: OASIS Mailing Lists Help | MarkMail Help

oslc-core message

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]

Subject: Re: [oslc-core] helping out with TRS spec

Thanks Axel for looking into it,

Regarding TBD2, I fully agree on the term “TRS client” (we use “TRS Client” in our writing at KTH to denote it as a separate entity).

Regarding TBD3, we should discuss the relaxation of the SHOULD to MAY for the support of the features in question in a Jira issue. See https://issues.oasis-open.org/browse/OSLCCORE-167

Regarding your proposal on TBD4, I think sounds a non-normative to me, but please file an issue for it and add the OSLC Core TC meeting agenda next Thursday.

Regarding TBD5, I think it was discussed many times in the Core TC call and deserves a separate issue. I think we agreed there that HTTP is stateless protocol and adding state to track each TRS Client will be burdensome. So we agreed that mismatch is unavoidable. Can anyone remind me of the notes regarding that? The best I could find is https://wiki.oasis-open.org/oslc-core/Meetings/Telecon2017.11.09 which only briefly mentions that the “guidance on base page is incomplete, esp. how to proceed with the base update."

Regarding TBD6, I appended your comment to the issue and added my response there.

In general, I think you should capture everything as issues unless no action is needed on that. Regarding the priorities, I think you should just go around TRS issues and update their priorities according to your own gut feeling and see if anyone disagrees.


On 2018-02-26 , at 16:31, Jim Amsden <jamsden@us.ibm.com> wrote:

Jim Amsden, Senior Technical Staff Member
OSLC and Linked Lifecycle Data

----- Forwarded by Jim Amsden/Raleigh/IBM on 02/26/2018 10:29 AM -----

From:        Axel Reichwein <axel.reichwein@koneksys.com>
To:        Jim Amsden <jamsden@us.ibm.com>
Cc:        "Sarabura, Martin" <msarabura@ptc.com>
Date:        01/28/2018 10:25 PM
Subject:        RE: helping out with TRS spec

Hello Jim,
I just reviewed the TBDs in
1.       TBD1 is related to updating the CSS o make all uses of RFC2119 words use the rfc2119 style
2.       TBD2 - TRS Client, or simply, client – my preference would be to use the term “TRS client”, and no definition is needed according to me
3.       TBD3: “The TRS Server should support ETags, caching, and conditional GETs for Tracked Resources; TBD: TRS Servers may support ETags, caching, and conditional GETs for Tracked Resource Sets and Base resources.” -  replace “should” by “may”
4.       TBD4: Paged Base definition is missing.
5.       TBD5: “TBD: If paging of the base is supported (see other TBD section), then the server should take care to avoid mismatching pairing of a new change log with the old base and vice versa.” – I personally think that this does not need to be explained as the Base and the Change Log are of different type and would  be segmented each in their own way.
6.       TBD6: Access Context - https://issues.oasis-open.org/browse/OSLCCORE-82
How about this text for TBD4: “”Often, the number of member Resources in the Base will grow to the point where it is not reasonable to contain all the Resources in a single HTTP response. In this case, the base member Resources may be segmented into separate resources. There can be any number of such base member Resource segments, each one containing a subset of all  base member Resource segments.
Regarding TBD6: Access Context, it seems to me that Access Context is an orthogonal topic to OSLC resources in general, and it is not specific to TRS. I don’t think that Access Context should be standardized in an OSLC spec.
I’m not sure if the TBDs all correspond to an existing issue. I guess the list of existing issues is more specifically what I should be looking at
I guess that I should add my comments to the issues? Or should I just review the existing spec at
and potentially create new issues?
There are really many issues related to TRS…Are there any issues that I should tackle first? Do we have a deadline?
Best regards,
From: Jim Amsden [mailto:jamsden@us.ibm.com]
Tuesday, November 14, 2017 7:16 AM
Axel Reichwein
Re: helping out with TRS spec

Thanks for volunteering, we welcome broader input in order to promote effective integration technologies.

Instructions for editing documents are from the OSLC Domains TC Wiki:
https://github.com/oasis-tcs/oslc-domains/wiki. These apply to OSLC Core spec too.

OSLC Core issues are in Jira:
https://issues.oasis-open.org/browse/OSLCCORE-93?jql=project%20%3D%20OSLCCORE. TRS issues are in the TRS Component. Create whatever issues you want to manage your work.

Subversion is used for SCM:

TRS specs are here:

Send Robin Cover <
robin@oasis-open.org> a note to get write access to SVN. I use Subclipse, but there are other SVN clients you can use.

I have done and checked in the following based on the actions from last week's meeting:

1. added the tracked-resource-set-vocab.html document. This needs some editing, I just copied a template and added the ReSpec processing of the TRS domain vocabulary and shapes. This is also part 2 of a multi-part specification. So those two parts need to be added to the tracked-resource-set.html document too. See the CM spec for an example on how to do this:

2. I added the TRS Patch section back into the tracked-resource-set.html document

3. I was suppose to add the Access Control section back, but I found it was already there. Maybe I missed something.

4. I created an initial draft of the trs-guidance.html document and put the old content in there.

Jim Amsden, Senior Technical Staff Member

OSLC and Linked Lifecycle Data


Axel Reichwein <axel.reichwein@koneksys.com>
"nick_crossley@us.ibm.com" <nick_crossley@us.ibm.com>
Jim Amsden <jamsden@us.ibm.com>, "msarabura@ptc.com" <msarabura@ptc.com>
11/14/2017 09:46 AM
helping out with TRS spec

Hello Nick, Jim, Martin,

As I volunteered to help out with the TRS spec, could you share with me some documents on how to do it? Will I be assigned Jira issues to keep track of my tasks?

Best regards,

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]