Product Marketing would like to rename "SharePoint Imitation".
The detailed naming would be:
module.title=Alfresco Office Services Module
module.description=Allows applications that can talk to a SharePoint server to talk to your Alfresco installation
jar=alfresco-aos-module.jar and alfresco-aos.jar (lives next to aoservices.jar)
This deserves a closer look at the JARs:
- aoservices.jar includes the AOS library and implements the protocol
- alfresco-aos.jar is currently sharepoint-imitation.jar and contains the UI elements
- alfresco-aos-module.jar is currently sharepoint-imitation-module.jar and contains the web fragement to wire in the protocol URLs
- This naming introduces some confusion about the architecture of the product as there are three jars names "aos". But since this is currently a proprietary module, this confusion only matters for our internal team.
- The name does not describe what the module does. But the consumers of this name are generally system administrators, and the name will be displayed in both the installer and documentation next to the descriptive text.
This name has the following benefits:
- It does not use a Microsoft trademark in the name.
- Microsoft specifically allows using their trademarks in the description to indicate interoperability (https://www.microsoft.com/en-us/legal/intellectualproperty/trademarks/usage/general.aspx)
- It leverages a "brand" that we are already using and could be trademarked if needed.