the Oxygen WebHelp in-browser editor->the Oxygen
WebAuthor in-browser editor
We have an Oxygen WebHelp server->We have an Oxygen
WebAuthor server
Hi Scott,
We are willing to donate to the DITA TC any Oxygen
product commercial license which would be useful to
you.
Do you plan to allow anyone, even without an account
to review the specs? Or the reviewers are a selected
few who need to authenticate in some way?
Are the reviewers allowed to modify content (using
change tracking) or only to add comments to certain
paragraphs?
Let's say you would create a review branch for the
DITA 2.0 GitHub project:
https://github.com/oasis-tcs/dita
You could create some custom build process which
publishes it for example to Oxygen Webhelp output.
For example for the Oxygen XML Blog:
https://github.com/oxygenxml/blog
we have a Gradle script which publishes it to
WebHelp:
https://github.com/oxygenxml/blog/blob/master/build/build.gradle
And a web site which presents the WebHelp content:
https://blog.oxygenxml.com/topics/welcome.html
In the HTML page above there is an "Edit Online"
button which starts the Oxygen WebHelp in-browser
editor and allows people to edit the topic on GitHub
and then start a pull request. Users could edit using
change tracking, add comments and then their pull
requests could be merged in the branch and
re-published.
The Oxygen WebHelp output has a parameter which
allows it to show change tracking and comments
directly in the HTML content.
We have an Oxygen WebHelp server publicly available
but if you want to install one on premise we could
give you a license for it.
These suggestions made by users would remain on
GitHub in that separate branch if you want to archive
that branch later on.
As another possibility to allow for reviews, in the
same HTML page (https://blog.oxygenxml.com/topics/welcome.html)
you can add comments at the end using the Oxygen
Feedback form. Using Oxygen Feedback you can also add
comments on any HTML paragraph or block which had an
ID defined on it in the DITA content. Again we could
give you a license for Oxygen Feedback and host the
comments on our Feedback server. We do not have an
feature to export for comments out of Feeback but
maybe we could manually export them for you out of the
database when necessary.
About using Content Fusion, you could use our public
demo server, upload from Oxygen to it the entire DITA
contents as a fusion task, but all people willing to
read the specs and review it would need to create some
kind of free account (using their GitHub account for
example):
https://fusion.oxygenxml.com/evaluate
Or if you want to host Content Fusion on premise on
your own server we can give you a license for that.
If you use Oxygen change tracking or comments to
review topics, they will be part of the topic XML
content so if you want to preserve these in an archive
you could archive the entire set of topics.
So I'm not sure what you consider would be the best
solution for you.
Regards,
Radu
Radu Coravu
Oxygen XML Editor
On 11/2/21 16:09, Scott
Hudson wrote:
George, Radu,
Would this be something that could highlight
Content Fusion? Would Syncro be interested in
donating a Content Fusion instance to the DITA TC
that meets the requirements below?
--Scott
Sent from my iPhone
Begin forwarded message:
ï Can we ask oXygen to donate an
instance of Content Fusion that meets these
requirements?
--Scott
Sent from my iPhone
ï
I'm going to see if we can get DITAWeb
up and running this week. However, I
know that Mekon:
- No longer sells the product as a
review tool
- No longer is an OASIS member
So, I really don't know how responsive
they will be if we need assistance.
We probably should brainstorm as to
whether we have any alternatives.
We DO have requirements from OASIS that
pertain to our use of non-OASIS tooling:
- Our reviews must be viewable by the
public.
- We must be able to archive (in the
OASIS document repository) the work of
the review, that is, the comments made
by all participants.
Our requirements on the TC side have
been the following:
- Reviewers must be able to see all
the comments made by other reviewers.
- The tool must support discussion
between reviewers.
- Editors must be able respond to
comments, and indicate what work they
have done in response.
- It must be something that the
reviewers can tolerate, that is, NOT
Adobe PDF.
--
Best,
Kris
Kristen James Eberlein
Chair, OASIS DITA Technical Committee
OASIS Distinguished Contributor
Principal consultant, Eberlein
Consulting LLC
www.eberleinconsulting.com
+1 919 622-1501; kriseberlein (skype)
--------------------------------------------------------------------- To
unsubscribe from this mail list, you must
leave the OASIS TC that generates this
mail. Follow this link to all your TCs in
OASIS at:
https://www.oasis-open.org/apps/org/workgroup/portal/my_workgroups.php