guerrilla-translation.md (1225B)
1 # [Guerrilla Translation](http://www.guerrillatranslation.org/) 2 3 One feature of this use case is the same resource as both input and output to a series of processes. 4 5 ## Processes 6 7 Input | Process | Output 8 ------------- | ------------- | ----------- 9 Source document | Translate | Translation 10 Translation | Edit | Translation 11 Translation | Proofread | Translation 12 Translation | Publish | Translation 13 14 In this use case, we need to determine at what stage in the process flow the Translation is in. 15 In NRP, we do that by connecting it to the ProcessType of the last Process it came out of. 16 And then, the Input requirement for the next Process is the Translation at the previous stage. 17 18 We use ProcessType instead of Process because then a Translation at the same stage 19 can be used as an input to other Processes of the same next ProcessType. 20 21 We are working on Recipes that combine Processes and Exchanges, 22 or value flows that consist only of a series of Exchanges. 23 In those cases, it would be better to use InteractionType as a superclass of ProcessType and ExchangeType 24 and use the last InteractionType as the stage of the Resource. 25 26 I'll add some screen shots of a Guerrilla Translation Recipe and process flow soon.