Technical Committee AdministrationIcon indicating the project type

Technical Committee Administration

Uploaded image for project: 'Technical Committee Administration'
  1. Technical Committee Administration
  2. TCADMIN-4135

Publish Summary of changes in OSLC Core 3.0 from OSLC Open Project as a Project Note

    Details

    • Type: Task
    • Status: Closed
    • Priority: Major
    • Resolution: Fixed
    • Component/s: Document Upload Request
    • Labels:
      None
    • Environment:

      OSLC

      Description

      Your name:
        Andrii Berezovskyi
      Project name:
        OSLC Open Project
      Project email address:
        [1]oslc-op@lists.oasis-open-projects.org
      Title and version number:
        Summary of changes in OSLC Core 3.0
      Approval:
        [2]https://lists.oasis-open-projects.org/g/oslc-op-pgb/message/210
      ----------------------------------------------------------------------------------------
      [1] oslc-op@lists.oasis-open-projects.org
      [2] https://lists.oasis-open-projects.org/g/oslc-op-pgb/message/210

        Attachments

          Activity

          Ascending order - Click to sort in descending order
          Hide
          Permalink
          paul.knight1 Paul Knight added a comment -

          Source documents are listed in the announcement of intent to publish: https://lists.oasis-open-projects.org/g/oslc-op-pgb/message/204
          Ballot results are listed in the ballot: https://lists.oasis-open-projects.org/g/oslc-op-pgb/message/209

          Closing date of the ballot (approval date) is 16 December 2021.

          This is one of a set of five Project Notes which we expect to publish and announce together. The titles and approved source documents (individual HTML files) are:

          Quick review shows that some changes for the title and URIs will be needed.
          I'll assemble a list of the expected changes - likely for all of the PNs together.

          Show
          paul.knight1 Paul Knight added a comment - Source documents are listed in the announcement of intent to publish: https://lists.oasis-open-projects.org/g/oslc-op-pgb/message/204 Ballot results are listed in the ballot: https://lists.oasis-open-projects.org/g/oslc-op-pgb/message/209 Closing date of the ballot (approval date) is 16 December 2021. This is one of a set of five Project Notes which we expect to publish and announce together. The titles and approved source documents (individual HTML files) are: OSLC Core Version 3.0: Link Guidance ( TCADMIN-4132 ) https://lists.oasis-open-projects.org/g/oslc-op-pgb/attachment/204/2/oslc-link-guidance.html Configuration Management 1.0 Primer ( TCADMIN-4134 ) https://lists.oasis-open-projects.org/g/oslc-op-pgb/attachment/204/0/config-primer.html Summary of changes in OSLC Core 3.0 ( TCADMIN-4135 ) https://lists.oasis-open-projects.org/g/oslc-op-pgb/attachment/204/1/core-3.0-changes.html OSLC Tracked Resource Set Guidance ( TCADMIN-4136 ) https://lists.oasis-open-projects.org/g/oslc-op-pgb/attachment/204/3/trs-guidance.html Tracked Resource Set 1.0 Primer ( TCADMIN-4137 ) https://lists.oasis-open-projects.org/g/oslc-op-pgb/attachment/204/4/trs-primer.html Quick review shows that some changes for the title and URIs will be needed. I'll assemble a list of the expected changes - likely for all of the PNs together.
          Hide
          Permalink
          paul.knight1 Paul Knight added a comment -

          List of expected changes (Word document) has been attached to https://issues.oasis-open.org/browse/TCADMIN-4132.

          Link to Word document:

          Show
          paul.knight1 Paul Knight added a comment - List of expected changes (Word document) has been attached to https://issues.oasis-open.org/browse/TCADMIN-4132 . Link to Word document: https://issues.oasis-open.org/secure/attachment/11898/11898_project-notes-changes.docx
          Hide
          Permalink
          berezovskyi Andrii Berezovskyi added a comment -

          Paul, please find the updated document attached.

          Show
          berezovskyi Andrii Berezovskyi added a comment - Paul, please find the updated document attached.
          Hide
          Permalink
          paul.knight1 Paul Knight added a comment -

          Quick review of the updated document:

          • The front page needs to have a link for the PDF in addition to the HTML for "This stage". I'll add that.
          • Also needs Previous stage" and "Latest stage" URIs. I'll add those.
          • no References section, although several other works are mentioned and linked in the text
          • no Acknowledgments section
          Show
          paul.knight1 Paul Knight added a comment - Quick review of the updated document: The front page needs to have a link for the PDF in addition to the HTML for "This stage". I'll add that. Also needs Previous stage" and "Latest stage" URIs. I'll add those. no References section, although several other works are mentioned and linked in the text no Acknowledgments section
          Hide
          Permalink
          berezovskyi Andrii Berezovskyi added a comment -

          Thanks Paul,

          Can we skip Acknowledgments, please? Also, References are already linked in the text. We would like project notes as lean as possible. We can make fixes to these if you wish but will consider blog posts or Github Wiki for publication in the future. Or can we find a leaner approach for PNs? The first two issues you mentioned were because in ReSpec there is a "std_track" switch that removes some content from PNs on purpose.

          /Andrew

          Show
          berezovskyi Andrii Berezovskyi added a comment - Thanks Paul, Can we skip Acknowledgments, please? Also, References are already linked in the text. We would like project notes as lean as possible. We can make fixes to these if you wish but will consider blog posts or Github Wiki for publication in the future. Or can we find a leaner approach for PNs? The first two issues you mentioned were because in ReSpec there is a "std_track" switch that removes some content from PNs on purpose. /Andrew
          Hide
          Permalink
          paul.knight1 Paul Knight added a comment -

          Checking on possible relaxation of publication rules for these Project Notes...

          Show
          paul.knight1 Paul Knight added a comment - Checking on possible relaxation of publication rules for these Project Notes...
          Hide
          Permalink
          paul.knight1 Paul Knight added a comment -

          Hi Andrew,

          I discussed this with Chet, and he confirmed that if these are published as Project Notes they will need to have the Acknowledgments section.

          If you agree, I can set this up as follows, using the structure similar to CM, QM, and RM.

          That structure lists the PGB members, TSC members (currently the same, I think - Jim Amsden, Andrew Berezovskyi, Axel Reichwein), and "Additional Participants".

          For "Additional Participants", I will just list the Editor, if not already listed in PGB/TSC:

          • config-primer, core-3.0-changes, trs-primer: add David Honey
          • link-guidance: Jim Amsden (don't add)
          • trs-guidance: add Nick Crossley

          (Of course, if you think some others should be added to "Additional Participants", please let me know.)

          Show
          paul.knight1 Paul Knight added a comment - Hi Andrew, I discussed this with Chet, and he confirmed that if these are published as Project Notes they will need to have the Acknowledgments section. If you agree, I can set this up as follows, using the structure similar to CM, QM, and RM. That structure lists the PGB members, TSC members (currently the same, I think - Jim Amsden, Andrew Berezovskyi, Axel Reichwein), and "Additional Participants". For "Additional Participants", I will just list the Editor, if not already listed in PGB/TSC: config-primer, core-3.0-changes, trs-primer: add David Honey link-guidance: Jim Amsden (don't add) trs-guidance: add Nick Crossley (Of course, if you think some others should be added to "Additional Participants", please let me know.)
          Hide
          Permalink
          berezovskyi Andrii Berezovskyi added a comment -

          Thanks Paul,

          Let's then cancel any manual edits from your side and we will do another round of updates to the notes and to respec. If you did them already, please send them to me so that I can diff them as I make my edits to make sure I don't miss anything.

          We will get back to you with the updates notes shortly.

          /Andrew

          Show
          berezovskyi Andrii Berezovskyi added a comment - Thanks Paul, Let's then cancel any manual edits from your side and we will do another round of updates to the notes and to respec. If you did them already, please send them to me so that I can diff them as I make my edits to make sure I don't miss anything. We will get back to you with the updates notes shortly. /Andrew
          Hide
          Permalink
          paul.knight1 Paul Knight added a comment -

          Yes, I think that is probably the best way to do this, so the documents in github will be the same as what is published.

          I think I have added notes to all of the TCADMIN tickets (see the list in the first comment above). I have not made enough changes to the files yet to be very helpful.

          However, please look carefully at the Word document in TCADMIN-4132 (https://issues.oasis-open.org/secure/attachment/11898/11898_project-notes-changes.docx), and especially the LAST FIVE PAGES, which contain specific fixes for each of the five PNs.

          Show
          paul.knight1 Paul Knight added a comment - Yes, I think that is probably the best way to do this, so the documents in github will be the same as what is published. I think I have added notes to all of the TCADMIN tickets (see the list in the first comment above). I have not made enough changes to the files yet to be very helpful. However, please look carefully at the Word document in TCADMIN-4132 ( https://issues.oasis-open.org/secure/attachment/11898/11898_project-notes-changes.docx ), and especially the LAST FIVE PAGES , which contain specific fixes for each of the five PNs.
          Hide
          Permalink
          berezovskyi Andrii Berezovskyi added a comment -

          Thanks Paul, we will focus on this PN for now, Jim will take a look at your comments and your feedback document and come back with another package. Once this PN is published, will replicate the outstanding changes to the rest of the PNs and check the document with the feedback again.

          Show
          berezovskyi Andrii Berezovskyi added a comment - Thanks Paul, we will focus on this PN for now, Jim will take a look at your comments and your feedback document and come back with another package. Once this PN is published, will replicate the outstanding changes to the rest of the PNs and check the document with the feedback again.
          Hide
          Permalink
          paul.knight1 Paul Knight added a comment -

          I'll set this issue to "Stop Progress" for now.

          Show
          paul.knight1 Paul Knight added a comment - I'll set this issue to "Stop Progress" for now.
          Hide
          Permalink
          berezovskyi Andrii Berezovskyi added a comment -

          Paul,

          Please find the updated spec under the core-3.0-changes.html_2022-04-16.zip attachment.

          Please tell us if this fixes all your feedback on the Core PN. If it does, we will produce similar updates for the rest of PNs.

          Thanks,
          Andrew

          Show
          berezovskyi Andrii Berezovskyi added a comment - Paul, Please find the updated spec under the core-3.0-changes.html_2022-04-16.zip attachment. Please tell us if this fixes all your feedback on the Core PN. If it does, we will produce similar updates for the rest of PNs. Thanks, Andrew
          Hide
          Permalink
          paul.knight1 Paul Knight added a comment -

          This looks good. Thanks!

          I noted one set of changes for all of the Project Notes, and one invalid link in this one.

          Since the OASIS website was redesigned recently, some of the "boilerplate" URIs should now include a terminal slash, to avoid extra redirection. This will apply to all publications from the OSLC OP. I believe that all of these are in the "Notices" section:

          I noted one invalid link:

          • Section 12 - link to "Cross-origin resource sharing" is broken ("https://%5Bhttps://en.wikipedia.org/wiki/Cross-origin_resource_sharing")
          Show
          paul.knight1 Paul Knight added a comment - This looks good. Thanks! I noted one set of changes for all of the Project Notes, and one invalid link in this one. Since the OASIS website was redesigned recently, some of the "boilerplate" URIs should now include a terminal slash, to avoid extra redirection. This will apply to all publications from the OSLC OP. I believe that all of these are in the "Notices" section: https://www.oasis-open.org/policies-guidelines/ipr/ (add final "/") (linked to word "Policy" near top) https://www.oasis-open.org/policies-guidelines/trademark/ (add final "/") (last line) https://www.oasis-open.org/ (add final "/") (linked to word "OASIS" in the last paragraph) https://www.oasis-open.org/policies-guidelines/open-projects-process/#individual-cla-exhibit (add the final slash before the hashtag) (linked to " OASIS Contributor License Agreement (CLA)") I noted one invalid link: Section 12 - link to "Cross-origin resource sharing" is broken ("https://%5Bhttps://en.wikipedia.org/wiki/Cross-origin_resource_sharing")
          Hide
          Permalink
          berezovskyi Andrii Berezovskyi added a comment -

          Thanks, Paul!

          I just just fixed the link in Section 12. Regarding the rest, is it wise to fix them on our side? We'll have to fix the templates but all specs in the archive already will have broken links. Maybe better to fix redirects on your side?

          /Andrew

          Show
          berezovskyi Andrii Berezovskyi added a comment - Thanks, Paul! I just just fixed the link in Section 12. Regarding the rest, is it wise to fix them on our side? We'll have to fix the templates but all specs in the archive already will have broken links. Maybe better to fix redirects on your side? /Andrew
          Hide
          Permalink
          berezovskyi Andrii Berezovskyi added a comment -

          Paul Knight I have uploaded the PN file with the link in the Section 12 fixed.

          Show
          berezovskyi Andrii Berezovskyi added a comment - Paul Knight I have uploaded the PN file with the link in the Section 12 fixed.
          Hide
          Permalink
          paul.knight1 Paul Knight added a comment -

          Thanks! I should be able to handle this tomorrow.

          Show
          paul.knight1 Paul Knight added a comment - Thanks! I should be able to handle this tomorrow.
          Hide
          Permalink
          paul.knight1 Paul Knight added a comment - - edited

          Downloaded latest PN file:

          Regarding the links for the new URIs in the "Notices" section (adding the terminating slash, as described in the earlier comment) - we already have the redirects in place so existing publications will not be broken, but if possible, we would like to use the new URIs for new publications. It's not a critical item, but we want the newly-published specifications to have as few redirects as possible.

          The only issue I noted with this PN file is that the links for "Latest stage" are not correct.
          The "Latest stage" links refer to the symbolic links installed in the OASIS OP Library (https://docs.oasis-open-projects.org/), and are required by the OASIS naming directives.

          I had included the expected "Latest stage" links in the document "project-notes-changes" attached to one of the related tickets (TCADMIN-4132) and listed in the Dec. 28 comment above (https://issues.oasis-open.org/secure/attachment/11898/11898_project-notes-changes.docx). (At the end of that document, there is one page per PN with the details specific to that individual document.)

          They follow the same pattern used in all of the earlier specifications...

          For "OSLC Core v3.0 Changes Version 1.0", the "Latest stage" links will be:

          (If you would like to also include the two github links which are now listed as "Latest stage", they would need a different label, like "Latest stage in OSLC OP github repository". However, since you already have the link to "Latest editor's draft", it seems redundant.)

          Show
          paul.knight1 Paul Knight added a comment - - edited Downloaded latest PN file: https://issues.oasis-open.org/secure/attachment/11937/core-3.0-changes.html_20220509.zip Regarding the links for the new URIs in the "Notices" section (adding the terminating slash, as described in the earlier comment) - we already have the redirects in place so existing publications will not be broken, but if possible, we would like to use the new URIs for new publications. It's not a critical item, but we want the newly-published specifications to have as few redirects as possible. The only issue I noted with this PN file is that the links for "Latest stage" are not correct. The "Latest stage" links refer to the symbolic links installed in the OASIS OP Library ( https://docs.oasis-open-projects.org/ ), and are required by the OASIS naming directives. I had included the expected "Latest stage" links in the document "project-notes-changes" attached to one of the related tickets ( TCADMIN-4132 ) and listed in the Dec. 28 comment above ( https://issues.oasis-open.org/secure/attachment/11898/11898_project-notes-changes.docx ). (At the end of that document, there is one page per PN with the details specific to that individual document.) They follow the same pattern used in all of the earlier specifications... For "OSLC Core v3.0 Changes Version 1.0", the "Latest stage" links will be: https://docs.oasis-open-projects.org/oslc-op/core-3.0-changes/v1.0/core-3.0-changes.html https://docs.oasis-open-projects.org/oslc-op/core-3.0-changes/v1.0/core-3.0-changes.pdf (If you would like to also include the two github links which are now listed as "Latest stage", they would need a different label, like "Latest stage in OSLC OP github repository". However, since you already have the link to "Latest editor's draft", it seems redundant.)
          Hide
          Permalink
          paul.knight1 Paul Knight added a comment -

          I also attached the document "project-notes-changes.docx" to this issue:

          Show
          paul.knight1 Paul Knight added a comment - I also attached the document "project-notes-changes.docx" to this issue: https://issues.oasis-open.org/secure/attachment/11938/project-notes-changes.docx .
          Hide
          Permalink
          berezovskyi Andrii Berezovskyi added a comment -

          Paul, the updated note is uploaded under core-3.0-changes.html_2022-05-18.zip

          ReSpec 2.1.32 fixes slashes: https://github.com/oasis-tcs/tab-respec/releases/tag/v2.1.32

          We will update other notes shortly. Thank you for your help and patience!

          Show
          berezovskyi Andrii Berezovskyi added a comment - Paul, the updated note is uploaded under core-3.0-changes.html_2022-05-18.zip ReSpec 2.1.32 fixes slashes: https://github.com/oasis-tcs/tab-respec/releases/tag/v2.1.32 We will update other notes shortly. Thank you for your help and patience!
          Hide
          Permalink
          paul.knight1 Paul Knight added a comment - - edited

          Downloaded the ZIP file https://issues.oasis-open.org/secure/attachment/11940/core-3.0-changes.html_2022-05-18.zip.
          Initial inspection looks good.

          TBD:
          [x] Generate the PDF format
          [x] set up installation scripts

          This will be prepared for staging review along with the other four Project Notes, as noted in earlier comments.

          Show
          paul.knight1 Paul Knight added a comment - - edited Downloaded the ZIP file https://issues.oasis-open.org/secure/attachment/11940/core-3.0-changes.html_2022-05-18.zip . Initial inspection looks good. TBD: [x] Generate the PDF format [x] set up installation scripts This will be prepared for staging review along with the other four Project Notes, as noted in earlier comments.
          Hide
          Permalink
          paul.knight1 Paul Knight added a comment -

          Should be ready for staging.

          Show
          paul.knight1 Paul Knight added a comment - Should be ready for staging.
          Hide
          Permalink
          paul.knight1 Paul Knight added a comment -

          Installed files for staging review:

          • prepared files with timestamps, ZIP, and manifest in personal directory
          • verified sync between canonical directory and OASIS Library
          • synced canonical OP directory to ztest to create staging directory
          • created new WP, Version, and stage directory
          • copied files into stage directory
          • added new symlinks
          • installed README warning file
          • set timestamps for directory and symlinks, also for version directory.
          • checked installation
          • requested OASIS staff staging review:

          Please review the staging server installation of OSLC Core v3.0 Changes v1.0 PN01.

          This is the first of five similar Project Notes. It is the model for the others. If this one looks good, I'll go ahead and set up the other four, but if something needs changing, I'll arrange corrections before preparing the others.

          Note that the URIs here are following the OSLC pattern in which the file name does not contain the Version and stage tokens. (This simplifies processing for the OSLC publication system based on GitHub and ReSpec, since the filename itself doesn't change over time.)

          The files are:

          OSLC Core v3.0 Changes Version 1.0
          Project Note 01
          16 December 2021

          https://docs-staging.oasis-open-projects.org/ztest/oslc-op/core-3.0-changes/v1.0/pn01/core-3.0-changes.html
          https://docs-staging.oasis-open-projects.org/ztest/oslc-op/core-3.0-changes/v1.0/pn01/core-3.0-changes.pdf

          Please add comments to https://issues.oasis-open.org/browse/TCADMIN-4135.

          Show
          paul.knight1 Paul Knight added a comment - Installed files for staging review: prepared files with timestamps, ZIP, and manifest in personal directory verified sync between canonical directory and OASIS Library synced canonical OP directory to ztest to create staging directory created new WP, Version, and stage directory copied files into stage directory added new symlinks installed README warning file set timestamps for directory and symlinks, also for version directory. checked installation requested OASIS staff staging review: Please review the staging server installation of OSLC Core v3.0 Changes v1.0 PN01. This is the first of five similar Project Notes. It is the model for the others. If this one looks good, I'll go ahead and set up the other four, but if something needs changing, I'll arrange corrections before preparing the others. Note that the URIs here are following the OSLC pattern in which the file name does not contain the Version and stage tokens. (This simplifies processing for the OSLC publication system based on GitHub and ReSpec, since the filename itself doesn't change over time.) The files are: OSLC Core v3.0 Changes Version 1.0 Project Note 01 16 December 2021 https://docs-staging.oasis-open-projects.org/ztest/oslc-op/core-3.0-changes/v1.0/pn01/core-3.0-changes.html https://docs-staging.oasis-open-projects.org/ztest/oslc-op/core-3.0-changes/v1.0/pn01/core-3.0-changes.pdf Please add comments to https://issues.oasis-open.org/browse/TCADMIN-4135 .
          Hide
          Permalink
          chet-oasis Chet Ensign added a comment -

          The files look fine. No issues seen. I approve to promote to docs.oasis-open.org

          Show
          chet-oasis Chet Ensign added a comment - The files look fine. No issues seen. I approve to promote to docs.oasis-open.org
          Hide
          Permalink
          paul.knight1 Paul Knight added a comment -

          This will be promoted along with the other four, after their reviews.

          Show
          paul.knight1 Paul Knight added a comment - This will be promoted along with the other four, after their reviews.
          Hide
          Permalink
          paul.knight1 Paul Knight added a comment -

          Promoted approved files to OASIS Library (docs.oasis-open-projects.org) for final reviews

          • Synced files from /ztest to canonical directory (/htdocs)
          • Synced to OASIS OP Library (docs.oasis-open-projects.org)
          • checked links, etc.
            • no link issues found in any of the five PNs
          • requested sanity check:

          Please review the OASIS Library installation of the files for five OSLC PN01s.
          I did not find any broken links or other issues.

          Configuration Management Primer Version 1.0
          Project Note 01
          16 December 2021

          https://docs.oasis-open-projects.org/oslc-op/config-primer/v1.0/pn01/config-primer.html
          https://docs.oasis-open-projects.org/oslc-op/config-primer/v1.0/pn01/config-primer.pdf

          OSLC Core v3.0 Changes Version 1.0
          Project Note 01
          16 December 2021

          https://docs.oasis-open-projects.org/oslc-op/core-3.0-changes/v1.0/pn01/core-3.0-changes.html
          https://docs.oasis-open-projects.org/oslc-op/core-3.0-changes/v1.0/pn01/core-3.0-changes.pdf

          OSLC Core Version 3.0: Link Guidance Version 1.0
          Project Note 01
          16 December 2021

          https://docs.oasis-open-projects.org/oslc-op/link-guidance/v1.0/pn01/link-guidance.html
          https://docs.oasis-open-projects.org/oslc-op/link-guidance/v1.0/pn01/link-guidance.pdf

          OSLC Tracked Resource Set Guidance Version 1.0
          Project Note 01
          16 December 2021

          https://docs.oasis-open-projects.org/oslc-op/trs-guidance/v1.0/pn01/trs-guidance.html
          https://docs.oasis-open-projects.org/oslc-op/trs-guidance/v1.0/pn01/trs-guidance.pdf

          Tracked Resource Set Primer Version 1.0
          Project Note 01
          16 December 2021

          https://docs.oasis-open-projects.org/oslc-op/trs-primer/v1.0/pn01/trs-primer.html
          https://docs.oasis-open-projects.org/oslc-op/trs-primer/v1.0/pn01/trs-primer.pdf

          Show
          paul.knight1 Paul Knight added a comment - Promoted approved files to OASIS Library (docs.oasis-open-projects.org) for final reviews Synced files from /ztest to canonical directory (/htdocs) Synced to OASIS OP Library (docs.oasis-open-projects.org) checked links, etc. no link issues found in any of the five PNs requested sanity check: Please review the OASIS Library installation of the files for five OSLC PN01s. I did not find any broken links or other issues. Configuration Management Primer Version 1.0 Project Note 01 16 December 2021 https://docs.oasis-open-projects.org/oslc-op/config-primer/v1.0/pn01/config-primer.html https://docs.oasis-open-projects.org/oslc-op/config-primer/v1.0/pn01/config-primer.pdf Please add comments to https://issues.oasis-open.org/browse/TCADMIN-4134 . *************************************** OSLC Core v3.0 Changes Version 1.0 Project Note 01 16 December 2021 https://docs.oasis-open-projects.org/oslc-op/core-3.0-changes/v1.0/pn01/core-3.0-changes.html https://docs.oasis-open-projects.org/oslc-op/core-3.0-changes/v1.0/pn01/core-3.0-changes.pdf Please add comments to https://issues.oasis-open.org/browse/TCADMIN-4135 . *************************************** OSLC Core Version 3.0: Link Guidance Version 1.0 Project Note 01 16 December 2021 https://docs.oasis-open-projects.org/oslc-op/link-guidance/v1.0/pn01/link-guidance.html https://docs.oasis-open-projects.org/oslc-op/link-guidance/v1.0/pn01/link-guidance.pdf Please add comments to https://issues.oasis-open.org/browse/TCADMIN-4132 . *************************************** OSLC Tracked Resource Set Guidance Version 1.0 Project Note 01 16 December 2021 https://docs.oasis-open-projects.org/oslc-op/trs-guidance/v1.0/pn01/trs-guidance.html https://docs.oasis-open-projects.org/oslc-op/trs-guidance/v1.0/pn01/trs-guidance.pdf Please add comments to https://issues.oasis-open.org/browse/TCADMIN-4136 . *************************************** Tracked Resource Set Primer Version 1.0 Project Note 01 16 December 2021 https://docs.oasis-open-projects.org/oslc-op/trs-primer/v1.0/pn01/trs-primer.html https://docs.oasis-open-projects.org/oslc-op/trs-primer/v1.0/pn01/trs-primer.pdf Please add comments to https://issues.oasis-open.org/browse/TCADMIN-4137 .
          Hide
          Permalink
          chet-oasis Chet Ensign added a comment -

          looks good. i approve to release

          Show
          chet-oasis Chet Ensign added a comment - looks good. i approve to release
          Hide
          Permalink
          paul.knight1 Paul Knight added a comment -
          • Removed README warning file and reset directory timestamp in canonical directory on staging server.
          • synced to OASIS OP Library (docs.oasis-open-projects.org)
          • Ready for announcements.
          Show
          paul.knight1 Paul Knight added a comment - Removed README warning file and reset directory timestamp in canonical directory on staging server. synced to OASIS OP Library (docs.oasis-open-projects.org) Ready for announcements.
          Hide
          Permalink
          paul.knight1 Paul Knight added a comment -

          Sent out announcement message to:

          Submitted announcement to OASIS website for review.

          Assigning to Chet to review and complete announcement, etc.

          Show
          paul.knight1 Paul Knight added a comment - Sent out announcement message to: project-announce@lists.oasis-open.org, members@lists.oasis-open.org, oslc-op@lists.oasis-open-projects.org, oslc-op-pgb@lists.oasis-open-projects.org emails: https://lists.oasis-open.org/archives/members/202205/msg00006.html https://lists.oasis-open-projects.org/g/oslc-op/message/835 Submitted announcement to OASIS website for review. Assigning to Chet to review and complete announcement, etc.
          Hide
          Permalink
          chet-oasis Chet Ensign added a comment -

          The article is published on the website and announced on social media. I'm closing this ticket. 

          Show
          chet-oasis Chet Ensign added a comment - The article is published on the website and announced on social media. I'm closing this ticket. 

            People

            • Assignee:
              chet-oasis Chet Ensign
              Reporter:
              berezovskyi Andrii Berezovskyi
            • Watchers:
              3 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: