Technical Developments Sample Clauses

Technical Developments. Biocept shall keep Clarient fully informed as to all discoveries and technical developments (including, without limitations, any inventions) made by Biocept during the Term related to the Diagnostic Tests.

Technical Developments. 10.1 The intellectual property rights to any improvements to the Products produced by TF Ltd shall be the property of TF Ltd. TF Ltd agrees that the irrevocable exclusive rights to manufacture and market such improvements outside the Territory will ~e assigned back to TF Inc. on a similar royalty free basis to the assignment granted herein save that TF Ltd gives no warranty as to it's ability to grant such rights or that the exploitation of the same will not infringe the rights

Technical Developments. To enable a continuous integration in the whole workflow system, we implemented a Silk Web service. This Web service acts like every other Web service in OmNom. It takes as input a URI to a Silk configuration file and generates the links based on this configuration. Therefore, we used the Silk Single Server Machine and built our implementation around it to fit our needs. Usually, Silk takes as input in the configuration either a local RDF dump or a SPARQL endpoint. Since the user cannot manually upload any files on our server, it is not possible to specify RDF dumps but not every resource has a SPARQL endpoint. Thus, we need to provide the possibility to specify URIs as input in the configuration. Whenever an URI is given, we download the content and write it into a local file on the server. Afterwards, we internally rewrite the configuration and replace it with the local file input. With this workaround, we enable the usage of URIs as input without the need to directly adapt Silk. Nevertheless, the input sources must either be available via a SPARQL endpoint or be provided as an RDF dump in the Web. Furthermore, the Silk configuration file must also be accessible via a URI. As result of the Silk Web service, a linkset is created, containing the links between the instances. These linksets can then be published in the triple store similar to the ingested data. Using the Linked Data API, whole linksets can be displayed or only the links which have been generated for a certain instance. Thus, additional information about the instances is provided. Using the linksets, it is obvious that the links have been generated by Silk and were not included in the ingested data itself. Moreover, also the provenance of the matching can be inspected to get to know which configuration has been used to create the according links. The deployed Silk tool is the latest stable version 2.5.3 (from March 6, 2012)20. Documentation for the tool in general can be found in the Silk wiki at ▇▇▇▇▇://▇▇▇.▇▇▇▇▇▇▇▇.▇▇▇/spaces/silk/wiki/Home. Information about the deployment in DM2E can be found in the developer documentation (see Section 10.2). The software was deployed on a Tomcat 7 Web container configured to run with the options JAVA_OPTS="-Djava.awt.headless=true -Xms2048m -Xmx8192m -XX:PermSize=1024m - XX:MaxPermSize=1024m”, that is, a maximum use of 8GB of RAM. Depending on the use of the machine, the maximum amount of allocated RAM can still be raised later on, seeing the total of 16...

Technical Developments. In recognition of ongoing development in the area of discovery of scholarly resources, the JSTOR, Licensee, and its Members shall cooperate in communicating about possible further uses of Metadata in connection with such developments. Notwithstanding the foregoing, nothing set forth herein shall obligate either party to agree to modify the Scope of Use of the Metadata as described herein.