[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: RE: [etmf] We have encountered a show stopper on the eTMF submission
Chet and All, I’m pleased you indicate below this is not a showstopper. Actually, this is an easy fix: it is CareLex’s full intention and practice to donate our work to the OASIS TC and make any work contributed open for OASIS’ use, we simply failed to remove copyright references in our haste. We do wish to retain our rights outside of Oasis to avoid having CareLex misrepresented. We will work diligently to fix this issue today along with the other items mentioned below and will reconvene the TC at the earliest possible time to vote again. For TC members, can we shoot for this Friday (6/20) at 9AM PDT for a 15 minute call and vote? Separate invite and updated docs to follow. Best, Jennifer Alpert Palchak, CEO CareLex Direct: 916-600-8388 www.carelex.org This e-mail and any accompanying attachments are confidential. The information is intended solely for the use of the individual(s) to whom it is addressed. Any review, disclosure, copying, distribution, or use of this e-mail communications by others is strictly prohibited. If you are not the intended recipient, please notify us immediately by returning this message to the sender and delete all copies. Thank you for your cooperation. From: etmf@lists.oasis-open.org [mailto:etmf@lists.oasis-open.org] On Behalf Of Chet Ensign Members of the eTMF TC, We have been working on the TC's Committee Specification Draft and unfortunately we've encountered something in the content that we cannot allow. Please see the notes below, take appropriate corrective action, approve the corrected working draft as a CSD and approve for public review again. Problem: In the draft, each illustration includes the words "copyright Carelex" in its caption. This is a bad practice because it encourages the lack of clarity about the rights that could muddy the waters for adoption, but more critically, it violates our policies and rules. It appears to apply a special rule to that component that overrides our general rules. Contributions to OASIS TCs come with a grant of rights to OASIS and the TC to reproduce the contribution in the TC's work product. The final work product is copyright OASIS. The contributors ongoing rights are implicit from the terms of the contribution and the contributor is free to use the contributions elsewhere and include their own copyright claims when they do. As the TC needs to revise the working draft and approve a new CSD, I include some other things we noticed that you may want to address now. I would have provided these as feedback during the public review but if you address them now, that'll be that many fewer comments to track and address: - The name OASIS is in mixed case throughout the draft. The proper name is all caps. - Sections 1.2 and 1.3 contain only the template boilerplate. Except for [RFC2119] the boilerplate text should be removed. In addition, it looks like you have all your references in a section 8 at the end of the document. The proper place for those references is in sections 1.2 and 1.3 where they can be seen as Normative or Non-Normative. Also, our recommendation/preference is that links in the references be made live, not left as text only. - Section 7 has a # in the title. Not sure why that is there & it should probably be removed. - Appendix C Revision History is in the middle of the appendices and should be moved to be last section of the document. - The link in Section 5.3.1 to http://protege.stanford.edu/download/download.html looks like it may be broken. - The TC's use of extra blank lines for page positioning causes a lot of blank space in the HTML version. The TC should use other formatting options for avoiding tables and images breaking across pages. (e.g., Table 2, Figure 12, etc.) to avoid this if possible. As I say, these are not show stoppers but as you need to revise the draft, you can address them now and avoid having to deal with them in a subsequent review. I will put the current TC Admin JIRA tickets on hold rather than close them. That way, as soon as we have the revised draft, we can pick back up on the work. So to recap, what I need the TC to do is: - Remove the copyright language from the draft and make any of the other fixes you want to address now. - Package the materials - the revised CSD, vocabulary, and owl file in a ZIP file and load it to the Kavi repository. - Approve this working draft as a Committee Spec Draft and approve for 45 day public review. - Send me the link to the meeting minutes with the motion so that I can update the tickets and recommence the work. Thanks and again, my apologies that I didn't see this sooner. Let me know if you have any questions on any of the above. -- Check your work using the Support Request Submission Checklist at http://www.oasis-open.org/committees/download.php/47248/tc-admin-submission-checklist.html |
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]