- Posts: 264
- Joined: Thu Nov 28, 2013 9:32 am
- Location: Hamburg/Germany
we have a central XML file for which we need a comfortable way to edit it - preferably from anywhere within our intranet.
If I would edit the file locally with oXygen XML editor I would create a custom framework including
- identification of file type by file name or content
- XSD file
- schematron file (possibly included inthe xsd)
- custom css file(s)
- possibly XSLT-based author operations referenced by the css
But since the file should be editable from a larger range of computers within our company a browser-based editor would be nice. Thus, I had the idea of using Web Author. However, I have almost no knowledge about it, yet...
Now my questions:
- Is it possible to create a framework with these features with Web Author as well?
- It is a configuration file for a real server application. So we have quite high security requirements. A 1-level authentification (username+password) would probably not be sufficient. What options does Web Author provide? Or is it possible to host it locally?
- What are the ways to access the file? I guess this is what the connectors are for!? Since we need a versioning anyway we might put it into a local git-repository anyway. Are there any other recommendations?
Thanks and regards,
- Posts: 311
- Joined: Thu Sep 04, 2014 4:22 pm
To answer your questions:
1. Yes. Frameworks developed for Oxygen XML Editor have a high degree of compatibility with Web Author. Specifically, the points that you mentioned are supported. The only thing I wanted to mention is that XSLT operations will be executed using Saxon HE.
2. Web Author does not need an authentication itself. You just need to authorize it edit files on your behalf. For example, for files stored on GitLab, you will log in to GitLab using whatever authentication mechanism you have configured there and then "authorize" Web Author to access files on your behalf (using an OAuth flow).
Web Author needs to be installed locally - the online demo is provided only for evaluation purposes.
3. Connectors fail in two categories: Enterprise Content Management and Versioning Control Systems. People choose the first one when they already have an ECM deployed in their company and they are constraint to choose it also for XML files.
Among VCS-es Git is a popular option. For an on-premise distribution we recommend GitLab and GitHub Enterprise.