During the last meeting we agreed to review the way that the documentation about CRM base and its extensions is managed. This is probably as part of issue 358, but there have been messages in the list about this issue (e.g. by Rob, but I can't find the reference)
Francesco, George and I discussed this and produced the following text, which is a first attempt to specify what it is we need: --- # Specification of CRM-SIG work ## Functions ### Versioning: * manage CRM core and extensions document versions, i.e. specifying the classes and properties (and their versions) which exist in each document, to ensure coherence among versions of extensions and CRM core versions, * manage content changes in the class and property declarations in current document version (including scope notes), * document arguments for each committed change and dismissed proposal ### Visualization: * visualize class and property hierarchies * visualize combinations of extensions with CRM core * visualize evolution in time of CRM core and extensions ### Serialization: * produce a formatted encoding (e.g. PDF file) for each document version * produce an RDFS encoding for each document version ### Interpretation and best practice: * capture discussions about classes, properties and their meaning * recommend best practice at implementation level ## Roles * SIG members: participate in meetings to make decisions on version and scope note changes * version maintainers (SIG): collect contributions, editorial work, animate and moderate the discussion in the community, ensure completeness * version contributors (SIG) : produce and discuss the content (including serializations) and propose changes * public (non-SIG) : discuss the content, raise questions on interpretation ### Access level * Public, contributors and SIG members raise questions, discuss proposals, comment, answer questions * Contributors can create issues and recommend changes at any level * Maintainers summarize/introduce issues for discussion in the SIG * SIG members 'vote' on issues, classes definitions, ... ## Existing platforms: * Drupal in FORTH (existing but not accessible for contributors and maintainers) * dataforhistory.org application (open, but still under development) + an internal forum / API * GitHub (versioning, discussions, API) --- It would be useful to receive feedback on whether this captures the SIG's activities and whether there are any other platforms we should be considering. We can then assign people to evaluate the different platforms, so volunteers with expertise on a platform are welcome. All the best, Thanasis This email and any attachments are intended solely for the addressee and may contain confidential information. If you are not the intended recipient of this email and/or its attachments you must not take any action based upon them and you must not copy or show them to anyone. Please send the email back to us and immediately and permanently delete it and its attachments. Where this email is unrelated to the business of University of the Arts London or of any of its group companies the opinions expressed in it are the opinions of the sender and do not necessarily constitute those of University of the Arts London (or the relevant group company). Where the sender's signature indicates that the email is sent on behalf of UAL Short Courses Limited the following also applies: UAL Short Courses Limited is a company registered in England and Wales under company number 02361261. Registered Office: University of the Arts London, 272 High Holborn, London WC1V 7EY
