Skip to main content

Notice

The new RDA web platform is still being rolled out. Existing RDA members PLEASE REACTIVATE YOUR ACCOUNT using this link: https://rda-login.wicketcloud.com/users/confirmation. Please report bugs, broken links and provide your feedback using the UserSnap tool on the bottom right corner of each page. Stay updated about the web site milestones at https://www.rd-alliance.org/rda-web-platform-upcoming-features-and-functionalities/.

Fwd: [rda-legalinterop-ig] Legal Interoperability review responses and revisions

  • Author
    Replies
  • #133410

    Paul Uhlir
    Member

    Hi all: I have not finished restructuring and editing the Implementation
    Guidelines. I will send both the redlined and clean versions in full early
    next week.
    However, I think we would benefit from a telcon tomorrow to address any
    final issues regarding the revised Principles and Summary comments, and
    also discuss the draft responses to the Implementation Guidelines that I
    sent earlier this week and that Simon resent yesterday. There were several
    comments that indicate we need to still resolve.
    There is one issue that we did not address and that we should, I think. We
    only provide guidance to data producers and/or the rights holder in sharing
    their data from a legal perspective. We do not address, however, data that
    researchers receive that may have various restriction on them, that they
    wish to reuse, combine, etc. This is real-world problem that faces all
    researchers to which they presumably wish some guidance.
    Should they not use restricted data, which would infect the combined
    product? Should they use the data with the restrictions and not
    redistribute? Should they try to find a substitutable data source? Should
    they go back to to the source and try to negotiate more reasonable terms
    for their intended use(s)? Should they ignore the restrictions and
    redistribute their derivative dataset?
    These options are all plausible, although we certainly don’t want to
    recommend the last one, and there may be other options. Do we want to
    address this topic in the Guidelines, and if so, where and to what extent?
    We clearly can’t anticipate the considerations that affect each instance,
    but it seems to me that we want to provide some general guidance on this.
    I look forward to our discussion tomorrow.
    Cheers,
    Paul

  • #133407

    Paul Uhlir
    Member

    Hi all, Simon appears to be indisposed today, so we will have a longer
    telcon next week, which also will take into account the revised Guidelines
    document.
    Best wishes,
    Paul

  • #133406

    Simon Hodson
    Member

    Dear Paul, all;
    I don’t follow – I’m available but the call is scheduled for 14.00 UTC.
    Best wishes,
    Simon.
    ___________________________
    Nominations for SciDataCon 2016 Programme Committee, Deadline 15 February 2016: http://goo.gl/forms/VoIxPFLWS5
    Call for Session Proposals, SciDataCon 2016, Deadline 7 March 2016: http://www.scidatacon.org/2016/
    Data Science Journal, Call for Papers: Advances in Data Modelling and Knowledge Representation for Research Data, deadline 31 March 2016: http://datascience.codata.org/
    Applications are now invited for the CODATA-RDA School of Research Data Science, hosted at the International Centre of Theoretical Physics, 1-12 August 2016: http://indico.ictp.it/event/7658/
    For further news from the CODATA community, please consider joining the CODATA International list at http://lists.codata.org/mailman/listinfo/codata-international_lists.coda
    ___________________________
    Dr Simon Hodson | Executive Director CODATA | http://www.codata.org
    E-Mail: ***@***.*** | Twitter: @simonhodson99 | Skype: simonhodson99
    Blog: http://www.codata.org/blog
    Diary: http://bit.ly/simonhodson99-calendar
    Tel (Office): +33 1 45 25 04 96 | Tel (Cell): +33 6 86 30 42 59
    CODATA (ICSU Committee on Data for Science and Technology), 5 rue Auguste Vacquerie, 75016 Paris, FRANCE

  • #133405

    Simon Hodson
    Member

    Paul… It’s not – it is now 12.21 UTC/GMT – which is 7.21 Eastern…
    The call is at 14.00 is about 1 hour and 40 minutes…
    Please can someone corroborate: http://www.timeanddate.com/time/map/
    S.

Log in to reply.