FRINK Linked Data Fragments server

Matches in SemOpenAlex for { <https://semopenalex.org/work/W272547392> ?p ?o ?g. }

• W272547392 abstract "Protection for software produced under the GPL is well known and shown to be successful, based upon copyright protection and licensing. It is not so obvious that the same model can be moved over to hardware, since historically engineers have been allowed to reverse engineer products at will, so long as they are not protected by patents etc. The heart of the problem, so far as opens source hardware goes, is that the open source philosophy relies on the key principle that you are free to use my work, but only if you subsequently share your derived work, so the benefit continues. It relies on a suitable legal framework to enforce this contract. Current developments in hardware are moves away from the traditional 'Von Neumann' architecture to multi-core, parallel processing forms and also system-on-a-chip approaches. These are very complex and difficult to produce and this is where companies seek to make money. Protection is important since special purpose chips are now part of almost every device being manufactured and markets can be large. It is not clear how best protection for these can be enabled--earlier forms such as 'mask protection' are no longer so relevant when the whole process of design and manufacture is through special purpose languages. The question we are setting in this call for papers is: what is the best method to enforce the open source philosophy for hardware, to ensure that contributions based upon the work of others remain open for others to develop. One example of the attempt to produce relevant licensing is the TAPR Open Hardware License--http://www.tapr.org/OHL which has been discussed by the open access community. However, since 'Open Source Hardware' is relatively unexplored in terms of legal issues, articles will be important contributions to the legal debate. We are seeking papers which look into the relevant issues and which might help to move the open source model into this new arena. Topics could include: 1. What are the issues which separate software and hardware open source models? 2. What elements of the GPL are appropriate or not appropriate for protecting hardware developments from freeloading? 3. Is a new 'Hardware GPL' model required? 4. Is hardware protection possible through the programming which underpins development? 5. What problems arise from 'contractual' models of protection? 6. Is it possible to develop an 'international' consensus on protection? 7. Can hardware--where it is not subject to patent--ever be protected anyway? These, of course, are the issues which lawyers looked at in terms of software in the 1980s. The developments in hardware ('chip') protection now mean that the same kinds of questions asked then, must be asked now, as the economics and manufacturing of chip technology moves into a new phase. Technical advice will be available to legal authors to ensure full understanding of these issues. An overview of current design and manufacturing contexts is attached. If you wish to contribute to the Special Edition, then please contact Philip Leith at p.leith@qub.ac.uk More Information 1. Technical Background There are two types of logic silicon chip in widespread use: (1) application specific integrated circuits (ASICs) and (2) programmable hardware chips of various types. In addition to these there are a number of different types of memory chips, which can be divided into (1) those that lose their memory when power is turned off (the Dynamic Random Access Memory (DRAM), and (2) those which retain their memory when power is turned off (Static Random Access Memory (SRAM) and flash programmable memory). Typically software programs are stored in the memory chip(s) and their behaviour executed on the logic chip. ASICs are a one-off manufacture. Once you have made one, its hardware logic is fixed. …" @default.
• W272547392 created "2016-06-24" @default.
• W272547392 creator A5059592278 @default.
• W272547392 date "2009-09-01" @default.
• W272547392 modified "2023-09-23" @default.
• W272547392 title "Protecting Open Source Hardware" @default.
• W272547392 hasPublicationYear "2009" @default.
• W272547392 type Work @default.
• W272547392 sameAs 272547392 @default.
• W272547392 citedByCount "0" @default.
• W272547392 crossrefType "journal-article" @default.
• W272547392 hasAuthorship W272547392A5059592278 @default.
• W272547392 hasConcept C111919701 @default.
• W272547392 hasConcept C115903868 @default.
• W272547392 hasConcept C123657996 @default.
• W272547392 hasConcept C127413603 @default.
• W272547392 hasConcept C142362112 @default.
• W272547392 hasConcept C153349607 @default.
• W272547392 hasConcept C18762648 @default.
• W272547392 hasConcept C26517878 @default.
• W272547392 hasConcept C2777904410 @default.
• W272547392 hasConcept C3018397939 @default.
• W272547392 hasConcept C38652104 @default.
• W272547392 hasConcept C41008148 @default.
• W272547392 hasConcept C548595372 @default.
• W272547392 hasConcept C78519656 @default.
• W272547392 hasConcept C80469333 @default.
• W272547392 hasConcept C98045186 @default.
• W272547392 hasConceptScore W272547392C111919701 @default.
• W272547392 hasConceptScore W272547392C115903868 @default.
• W272547392 hasConceptScore W272547392C123657996 @default.
• W272547392 hasConceptScore W272547392C127413603 @default.
• W272547392 hasConceptScore W272547392C142362112 @default.
• W272547392 hasConceptScore W272547392C153349607 @default.
• W272547392 hasConceptScore W272547392C18762648 @default.
• W272547392 hasConceptScore W272547392C26517878 @default.
• W272547392 hasConceptScore W272547392C2777904410 @default.
• W272547392 hasConceptScore W272547392C3018397939 @default.
• W272547392 hasConceptScore W272547392C38652104 @default.
• W272547392 hasConceptScore W272547392C41008148 @default.
• W272547392 hasConceptScore W272547392C548595372 @default.
• W272547392 hasConceptScore W272547392C78519656 @default.
• W272547392 hasConceptScore W272547392C80469333 @default.
• W272547392 hasConceptScore W272547392C98045186 @default.
• W272547392 hasIssue "2" @default.
• W272547392 hasLocation W2725473921 @default.
• W272547392 hasOpenAccess W272547392 @default.
• W272547392 hasPrimaryLocation W2725473921 @default.
• W272547392 hasRelatedWork W1485601746 @default.
• W272547392 hasRelatedWork W161115369 @default.
• W272547392 hasRelatedWork W1789644271 @default.
• W272547392 hasRelatedWork W202990094 @default.
• W272547392 hasRelatedWork W2045152518 @default.
• W272547392 hasRelatedWork W2055219718 @default.
• W272547392 hasRelatedWork W2060510412 @default.
• W272547392 hasRelatedWork W2123250466 @default.
• W272547392 hasRelatedWork W2188337452 @default.
• W272547392 hasRelatedWork W2235557676 @default.
• W272547392 hasRelatedWork W2294527225 @default.
• W272547392 hasRelatedWork W2325064446 @default.
• W272547392 hasRelatedWork W2496144377 @default.
• W272547392 hasRelatedWork W286530006 @default.
• W272547392 hasRelatedWork W314367489 @default.
• W272547392 hasRelatedWork W330432313 @default.
• W272547392 hasRelatedWork W96958750 @default.
• W272547392 hasRelatedWork W972446296 @default.
• W272547392 hasRelatedWork W2170261893 @default.
• W272547392 hasRelatedWork W2407867723 @default.
• W272547392 hasVolume "2009" @default.
• W272547392 isParatext "false" @default.
• W272547392 isRetracted "false" @default.
• W272547392 magId "272547392" @default.
• W272547392 workType "article" @default.