[OASIS Issue Tracker] (OSLCCORE-175) OASIS Modified the IPR statement

[OASIS Issues Tracker <workgroup_mailer@lists.oasis-open.org>]

     [ https://issues.oasis-open.org/browse/OSLCCORE-175?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

James Amsden updated OSLCCORE-175:
----------------------------------
    Description: 
OASIS have modified the wording of the IPR statement (in the third paragraph of "Status", and in the initial section of the Introduction (only in Part 1 in your documents), so that it will use the word "specification" instead of the specific stage (like "Committee Specification").  This simplifies things by removing this extra "moving part".

Also - the text immediately adjacent to "specification" should be changed from "is being developed under" to "is provided under", in every occurrence. ("is being developed under" is intended only for Working Drafts)

If your document preparation system already handles this, you are not required to change it, but we think it will simplify things.

 

> OASIS Modified the IPR statement
> --------------------------------
>
>                 Key: OSLCCORE-175
>                 URL: https://issues.oasis-open.org/browse/OSLCCORE-175
>             Project: OASIS OSLC Lifecycle Integration Core (OSLC Core) TC
>          Issue Type: Bug
>          Components: ReSpec
>            Reporter: James Amsden
>            Assignee: James Amsden
>            Priority: Minor
>
> OASIS have modified the wording of the IPR statement (in the third paragraph of "Status", and in the initial section of the Introduction (only in Part 1 in your documents), so that it will use the word "specification" instead of the specific stage (like "Committee Specification").  This simplifies things by removing this extra "moving part".
> Also - the text immediately adjacent to "specification" should be changed from "is being developed under" to "is provided under", in every occurrence. ("is being developed under" is intended only for Working Drafts)
> If your document preparation system already handles this, you are not required to change it, but we think it will simplify things.
>  



--
This message was sent by Atlassian JIRA
(v7.7.2#77003)