« WorkshopDocumentation/FabmlOntologies » : différence entre les versions
De fablabo
m →FabML : mise en page |
m →FabML : mise en page |
||
| Ligne 18 : | Ligne 18 : | ||
«''Developing open & distributed tools for Fablab project documentation''» (2010) | « '''''Developing open & distributed tools for Fablab project documentation''''' » (2010) | ||
Analyse à partir de 3 lieux : Protospace (Utrecht), Swiss Fablab (Lucerne), fabfolk.com (n'existe plus en 2014 ?) | Analyse à partir de 3 lieux : Protospace (Utrecht), Swiss Fablab (Lucerne), fabfolk.com (n'existe plus en 2014 ?) | ||
| Ligne 31 : | Ligne 31 : | ||
« ''Fab Labs often choose their own website as the primary repository for their project documentation, also known as FabMoments. FabML has been proposed as a meta language to describe FabMoments across repositories. This proposal has been validated at the FabFuse2 conference in Amersfoort in 2013, and a narrative of a possible use scenario has been developed to further detail the initial FabML proposal.'' » | « ''Fab Labs often choose their own website as the primary repository for their project documentation, also known as FabMoments. FabML has been proposed as a meta language to describe FabMoments across repositories. This proposal has been validated at the FabFuse2 conference in Amersfoort in 2013, and a narrative of a possible use scenario has been developed to further detail the initial FabML proposal.'' » | ||
« ''This article presents the initial FabML use context, as proposed earlier, which consists of a sharing part, a retrieval part, and some initial | « ''This article presents the initial FabML use context, as proposed earlier, which consists of a sharing part, a retrieval part, and some initial enhancements to the repository and retrieval system. The article then describes the FabMoment use scenario as developed at FabFuse2 and applies | ||
enhancements to the repository and retrieval system. The article then describes the FabMoment use scenario as developed at FabFuse2 and applies | |||
it to the initial FabML proposal. This results in four extensions to the initial description of the FabML use context. The article concludes with a summary of the requirements for the semantic design of a FabMoment, and it outlines the next steps for the development of the semantics of FabML. It also sketches the steps needed for the development of the technical and practical implementation of FabML.'' » | it to the initial FabML proposal. This results in four extensions to the initial description of the FabML use context. The article concludes with a summary of the requirements for the semantic design of a FabMoment, and it outlines the next steps for the development of the semantics of FabML. It also sketches the steps needed for the development of the technical and practical implementation of FabML.'' » | ||
