{'fraction_non_alphanumeric': 0.025813692480359147, 'fraction_numerical': 0.008978675645342313, 'mean_word_length': 5.28169014084507, 'pattern_counts': {'":': 0, '<': 0, '<?xml version=': 0, '>': 0, 'https://': 0, 'lorem ipsum': 0, 'www.': 0, 'xml': 0}, 'pii_count': 0, 'substrings_counts': 0, 'word_list_counts': {'cursed_substrings.json': 0, 'profanity_word_list.json': 0, 'sexual_word_list.json': 0, 'zh_pornsignals.json': 0}}
Supporting the evolution of workflow patterns for virtual communities

Virtual communities that make use of network information systems (NIS) have a need for specification support that agrees with their communal character. System specification changes must be acceptable to all members for a community to thrive. We concentrate on the specification of workflow-enabling communication tools rather than information tools that support a single user. Previously, we defined various levels of workflow specification, from speech acts to scenarios (H. Weigand et al., 1997; 1998). Once patterns for these levels have been identified, they can be stored in a component library and be (re)-used effectively by communities to speed up their NIS development. To ensure the acceptability of changes in workflow patterns, we propose to apply an existing method for legitimate user-driven specification.