Search: concept
Last modified by Vincent Massol on 2014/10/21
- Sort by:
- Relevance
Results 1 - 4 of 4
Page
1
Diagram
Located in
- Rendered document content
<mxGraphModel dx="1291" dy="497" grid="1" gridSize="10" guides="1" tooltips="1" connect="1" arrows="1" fold="1" page="1" pageScale="1" pageWidth="827" pageHeight="1169" math="0" shadow="0"> <root> <mxCell id="SIQsT-9ZqWYkEbxsVq23-0" /> <mxCell id="SIQsT-9ZqWYkEbxsVq23-1" parent="SIQsT-9ZqWYkEbxsVq23-0" /> <mxCell id="Hl1Mmd2WGRjVptXKN7IO-2" value="" style="edgeStyle=orthogonalEdgeStyle;rounded=0;orthogonalLoop=1;jettySize=auto;html=1;startArrow=classic;startFill=1;" edge="1" parent="SIQsT-9ZqWYkEbxsVq23-1" source="Hl1Mmd2WGRjVptXKN7IO-4" target="Hl1Mmd2WGRjVptXKN7IO-26"> <mxGeometry relative="1" as="geometry" /> </mxCell> <mxCell id="Hl1Mmd2WGRjVptXKN7IO-3" value="<div>The JS backend exposes endpoints similar to</div><div>the XWiki script services to the frontend</div>" style="edgeLabel;html=1;align=center;verticalAlign=middle;resizable=0;points=[];" vertex="1" connectable="0" parent="Hl1Mmd2WGRjVptXKN7IO-2"> <mxGeometry x="-0.3379" y="-2" relative="1" as="geometry"> <mxPoint x="2" y="13.71" as="offset" /> </mxGeometry> </mxCell> <mxCell id="Hl1Mmd2WGRjVptXKN7IO-4" value="<div>JS Backend - Native Javascirpt<br></div><div>Provides the same concepts as in XWiki in terms of component-based architecture and separation between API and implementation.
- Attachment content
The JS backend exposes endpoints similar to the XWiki script services to the frontend The JS backend exposes endpoints similar to the XWiki script services to the frontend JS Backend - Native Javascirpt Provides the same concepts as in XWiki in terms of component-based architecture and separation between API and implementation. JS Backend - Native Javascirpt Provides the same concepts as in XWiki in terms of component-based architecture and separation between API and implementation.
- Raw document content
<mxGraphModel dx="1291" dy="497" grid="1" gridSize="10" guides="1" tooltips="1" connect="1" arrows="1" fold="1" page="1" pageScale="1" pageWidth="827" pageHeight="1169" math="0" shadow="0"> <root> <mxCell id="SIQsT-9ZqWYkEbxsVq23-0" /> <mxCell id="SIQsT-9ZqWYkEbxsVq23-1" parent="SIQsT-9ZqWYkEbxsVq23-0" /> <mxCell id="Hl1Mmd2WGRjVptXKN7IO-2" value="" style="edgeStyle=orthogonalEdgeStyle;rounded=0;orthogonalLoop=1;jettySize=auto;html=1;startArrow=classic;startFill=1;" edge="1" parent="SIQsT-9ZqWYkEbxsVq23-1" source="Hl1Mmd2WGRjVptXKN7IO-4" target="Hl1Mmd2WGRjVptXKN7IO-26"> <mxGeometry relative="1" as="geometry" /> </mxCell> <mxCell id="Hl1Mmd2WGRjVptXKN7IO-3" value="<div>The JS backend exposes endpoints similar to</div><div>the XWiki script services to the frontend</div>" style="edgeLabel;html=1;align=center;verticalAlign=middle;resizable=0;points=[];" vertex="1" connectable="0" parent="Hl1Mmd2WGRjVptXKN7IO-2"> <mxGeometry x="-0.3379" y="-2" relative="1" as="geometry"> <mxPoint x="2" y="13.71" as="offset" /> </mxGeometry> </mxCell> <mxCell id="Hl1Mmd2WGRjVptXKN7IO-4" value="<div>JS Backend - Native Javascirpt<br></div><div>Provides the same concepts as in XWiki in terms of component-based architecture and separation between API and implementation.
Diagram
Located in
- Rendered document content
<mxGraphModel dx="2118" dy="497" grid="1" gridSize="10" guides="1" tooltips="1" connect="1" arrows="1" fold="1" page="1" pageScale="1" pageWidth="827" pageHeight="1169" math="0" shadow="0"> <root> <mxCell id="SIQsT-9ZqWYkEbxsVq23-0" /> <mxCell id="SIQsT-9ZqWYkEbxsVq23-1" parent="SIQsT-9ZqWYkEbxsVq23-0" /> <mxCell id="Tw77TpUCIYBJzCZJhseV-0" value="<div>Cristal Wiki UI / Client<br></div><div><br></div><div><br></div><div><br></div><div><br></div><div><br></div><div><br></div><div><br></div><div><br></div><div><br></div><div><br></div><div><br></div><div><br></div><div><br></div><div><br></div><div><br></div><div><br></div><div><br></div><div><br></div><div><br></div><div><br></div><div><br></div><div><br></div><div><br></div><div><br></div><div><br></div><div><br></div><div><br></div><div><br></div><div><br></div><div><br></div><div><br></div><div><br></div><div><br></div><div><br></div><div><br></div><div><br></div><div><br></div><div><br></div><div><br></div><div><br></div><div><br></div><div><br></div><div><br></div><div><br></div><div><br></div><div><br></div><div><br></div><div><br></div><div><br></div><div><br></div><div><br></div>" style="rounded=0;whiteSpace=wrap;html=1;dashed=1;fillColor=none;verticalAlign=middle;" parent="SIQsT-9ZqWYkEbxsVq23-1" vertex="1"> <mxGeometry x="-200" y="10" width="790" height="770" as="geometry" /> </mxCell> <mxCell id="Hl1Mmd2WGRjVptXKN7IO-2" value="" style="edgeStyle=orthogonalEdgeStyle;rounded=0;orthogonalLoop=1;jettySize=auto;html=1;startArrow=classic;startFill=1;" parent="SIQsT-9ZqWYkEbxsVq23-1" source="Hl1Mmd2WGRjVptXKN7IO-4" target="Hl1Mmd2WGRjVptXKN7IO-26" edge="1"> <mxGeometry relative="1" as="geometry" /> </mxCell> <mxCell id="Hl1Mmd2WGRjVptXKN7IO-3" value="<div>The JS backend exposes endpoints similar to</div><div>the XWiki script services to the frontend</div>" style="edgeLabel;html=1;align=center;verticalAlign=middle;resizable=0;points=[];" parent="Hl1Mmd2WGRjVptXKN7IO-2" vertex="1" connectable="0"> <mxGeometry x="-0.3379" y="-2" relative="1" as="geometry"> <mxPoint x="2" y="13.71" as="offset" /> </mxGeometry> </mxCell> <mxCell id="Hl1Mmd2WGRjVptXKN7IO-4" value="<div>JS Backend - Native Javascript or compilable JS / WebAssembly<br></div><div>Provides the same concepts as in XWiki in terms of component-based architecture and separation between API and implementation.
- Attachment content
Cristal Wiki UI / Client Cristal Wiki UI / Client The JS backend exposes endpoints similar to the XWiki script services to the frontend The JS backend exposes endpoints similar to the XWiki script services to the frontend JS Backend - Native Javascript or compilable JS / WebAssembly Provides the same concepts as in XWiki in terms of component-based architecture and separation between API and implementation. JS Backend - Native Javascript or compilable JS / WebAssembly Provides the same concepts as in XWiki in terms of component-based architecture and separation between API and implementation.
- Raw document content
<mxGraphModel dx="2118" dy="497" grid="1" gridSize="10" guides="1" tooltips="1" connect="1" arrows="1" fold="1" page="1" pageScale="1" pageWidth="827" pageHeight="1169" math="0" shadow="0"> <root> <mxCell id="SIQsT-9ZqWYkEbxsVq23-0" /> <mxCell id="SIQsT-9ZqWYkEbxsVq23-1" parent="SIQsT-9ZqWYkEbxsVq23-0" /> <mxCell id="Tw77TpUCIYBJzCZJhseV-0" value="<div>Cristal Wiki UI / Client<br></div><div><br></div><div><br></div><div><br></div><div><br></div><div><br></div><div><br></div><div><br></div><div><br></div><div><br></div><div><br></div><div><br></div><div><br></div><div><br></div><div><br></div><div><br></div><div><br></div><div><br></div><div><br></div><div><br></div><div><br></div><div><br></div><div><br></div><div><br></div><div><br></div><div><br></div><div><br></div><div><br></div><div><br></div><div><br></div><div><br></div><div><br></div><div><br></div><div><br></div><div><br></div><div><br></div><div><br></div><div><br></div><div><br></div><div><br></div><div><br></div><div><br></div><div><br></div><div><br></div><div><br></div><div><br></div><div><br></div><div><br></div><div><br></div><div><br></div><div><br></div><div><br></div>" style="rounded=0;whiteSpace=wrap;html=1;dashed=1;fillColor=none;verticalAlign=middle;" parent="SIQsT-9ZqWYkEbxsVq23-1" vertex="1"> <mxGeometry x="-200" y="10" width="790" height="770" as="geometry" /> </mxCell> <mxCell id="Hl1Mmd2WGRjVptXKN7IO-2" value="" style="edgeStyle=orthogonalEdgeStyle;rounded=0;orthogonalLoop=1;jettySize=auto;html=1;startArrow=classic;startFill=1;" parent="SIQsT-9ZqWYkEbxsVq23-1" source="Hl1Mmd2WGRjVptXKN7IO-4" target="Hl1Mmd2WGRjVptXKN7IO-26" edge="1"> <mxGeometry relative="1" as="geometry" /> </mxCell> <mxCell id="Hl1Mmd2WGRjVptXKN7IO-3" value="<div>The JS backend exposes endpoints similar to</div><div>the XWiki script services to the frontend</div>" style="edgeLabel;html=1;align=center;verticalAlign=middle;resizable=0;points=[];" parent="Hl1Mmd2WGRjVptXKN7IO-2" vertex="1" connectable="0"> <mxGeometry x="-0.3379" y="-2" relative="1" as="geometry"> <mxPoint x="2" y="13.71" as="offset" /> </mxGeometry> </mxCell> <mxCell id="Hl1Mmd2WGRjVptXKN7IO-4" value="<div>JS Backend - Native Javascript or compilable JS / WebAssembly<br></div><div>Provides the same concepts as in XWiki in terms of component-based architecture and separation between API and implementation.
Selecting a tool for managing Localization
Located in
- Rendered document content
The initial prototype is promising but wil need work to allow concurrent access and faster handling of big volumes of data. Currently the concept is ongoing translation. Reimport of the main language (english) file can be done regularly.
…Once it is loaded on launchpad.net there is a quite extensively developed translation application. The concept seems to work by application version. We need to verity if this is the way we want it to work.
- Raw document content
The initial prototype is promising but wil need work to allow concurrent access and faster handling of big volumes of data. Currently the concept is ongoing translation. Reimport of the main language (english) file can be done regularly.
…Once it is loaded on launchpad.net there is a quite extensively developed translation application. The concept seems to work by application version. We need to verity if this is the way we want it to work.
GPT Based Technologies
Located in
- Rendered document content
Annoucement here: https://stability.ai/blog/stability-ai-launches-the-first-of-its-stablelm-suite-of-language-models https://github.com/stability-AI/stableLM/ As a proof-of-concept, we also fine-tuned the model with Stanford Alpaca's procedure using a combination of five recent datasets for conversational agents: Stanford's Alpaca, Nomic-AI's gpt4all, RyokoAI's ShareGPT52K datasets, Databricks labs' Dolly, and Anthropic's HH.
…In order to solve these risks, Open access will be key. This concept is very interesting and it would make a lot of sense to join them and do something similar and ideally the same.
- Raw document content
Annoucement here: [[https:~~/~~/stability.ai/blog/stability-ai-launches-the-first-of-its-stablelm-suite-of-language-models>>https://stability.ai/blog/stability-ai-launches-the-first-of-its-stablelm-suite-of-language-models]] [[https:~~/~~/github.com/stability-AI/stableLM/>>https://github.com/stability-AI/stableLM/]] As a proof-of-concept, we also fine-tuned the model with [[Stanford Alpaca>>url:https://github.com/tatsu-lab/stanford_alpaca]]'s procedure using a combination of five recent datasets for conversational agents: Stanford's [[Alpaca>>url:https://github.com/tatsu-lab/stanford_alpaca]], Nomic-AI's [[gpt4all>>url:https://github.com/nomic-ai/gpt4all]], RyokoAI's [[ShareGPT52K>>url:https://huggingface.co/datasets/RyokoAI/ShareGPT52K]] datasets, Databricks labs' [[Dolly>>url:https://github.com/databrickslabs/dolly]], and Anthropic's [[HH>>url:https://github.com/anthropics/hh-rlhf]].
…In order to solve these risks, Open access will be key. This concept is very interesting and it would make a lot of sense to join them and do something similar and ideally the same.
Page
1
RSS feed for search on [concept]