Giter Club home page Giter Club logo

w3c-ipr's People

Contributors

fantasai avatar frivoal avatar

w3c-ipr's Issues

Provide upgrade path for existing specifications

Documents under the current Patent Policy should be able to trivially transition to the new Patent Policy by republication of a Review Draft. This particular republication would need to make all previous commitments live.

FPWD or equivalent

The classic W3C Patent Policy has specific rules for FPWD (and subsequent WDs prior to "Last Call"). The WHATWG has no equivalent to FPWD (or to WDs), and therefore no specific clause in their IPR Policy, but they do have a requirement that a Review Draft be published within 6 months of the Workstream being formed. Evergreen has "Preliminary Drafts", which are equivalent to WDs (and of which there is a first one). Even if an Evergreen REC is published without Preliminary Drafts first, it may be 24 months from the First Everegreen REC before the first Review Draft, during which there's no clarity on the Patent situation. The Contribution Licensing Obligations provides some measure of comfort, but there could still be WG participants who did not contribute but have claims they will eventually exclude, but are keeping initially silent about. The concern is stronger if incubation of that specification happened outside of the Working Group. An Evergreen Patent policy should either:

  • restore the relevant clauses from the classic W3C Patent Policy into the Evergreen Patent Policy (pros: reusing the existing rules probably results in easier acceptance by the AC, especially given that we want to apply the improvements of the evergreen/whatwg policy to the REC track as well; cons: the rules are more complex)
  • declare the first publication of an Evergreen REC (or even possibly of the first Preliminary Draft?) to be a Review Draft (pros: simple, maximum coverage; cons: more limited exclusion opportunity than in the classic Patent Policy)
  • Require a Review Draft within 6 months an evergreen deliverable being included in a charter (pro: same as WHATWG; cons: more complicated than First-Draft=Review-Draft, 6 months without clarity)

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    ๐Ÿ–– Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. ๐Ÿ“Š๐Ÿ“ˆ๐ŸŽ‰

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google โค๏ธ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.