<snip>If all we need to design future DITA wikis is a DITA wiki, what are we waiting for???</snip> If there is a suitable DITA wiki we can use then let's get...
Maybe it is a bit premature to move on to using a dwiki to design dwikis. A bit more planning and considering the possibilities seems in order. Doug Morrison...
... We'll get there! I like the discussions we've had, and I see some great potential for new tools here. The big picture I see is that the traditional wiki...
... potential for new tools here. If it helps move the DITA (wiki) community forward, I can provide a free license for our xml editor for this particular use...
Wow, I appreciate that offer, Laurens. I was just working on getting a design forum in place for the proposed project. We need a conventional type of forum...
This topic is intended to be a "sticky" resource on the whereabouts of currently available DITA collaboration tools and discussions. Tools: The ongoing IBM...
In my current investigation of the regulations surrounding Pharma, it appears that the FDA and the EU have come up with an XML structure that defines how to...
The OASIS Pharma Subcommittee (not a TC, but an SC of the DITA TC) is looking at appropriate semantic specialization to support the nomenclature and required...
I've mentioned that from a purely visual aspect, there is very little difference between a wiki and a blog. However, people who care deeply about blogging also...
66
dita-wikis@yahoogroup...
May 6, 2010 6:09 pm
Enter your vote today! A new poll has been created for the dita-wikis group: On a separate project forum, Lisa Dyer brought up the issue of devices on which...
I had to modify the poll to move this message to a post, as it looked funny on the poll page itself. On a separate project forum, Lisa Dyer brought up the...
Hi Don, WebDav with desktop editors may be a way to go, but I'm not so sure that solution precludes a browser-based solution. In fact, I think that there's...
... solution precludes a browser-based solution. WebDav is HTTP based, so it should be easy to add to any browser-based tool that doesn't already support it. ...
Julio, the efforts of vendors like Quark and SimplyXML to put DITA authoring on top of Word does play to the critical business value of getting new uses out of...
Gabor Fari of Microsoft has done a lot of work with pharma and life sciences companies. He presented on this at Rockley's IC 2010 in February. The problem he...
... their concerns about costs, schedules, training, and ... THEIR budgets and concerns. FYI: There is an article on precisely this topic in the February 2010...
Hi all, Great discussion. Thanks for the pointer Laurens. I do agree that there is a large amount of Office/Word inertia in this space but that doesn't mean we...
"Word / Office inertia" is part of the use case. Part of the point behind Quark/ IBM and Microsoft / Content Technologies is to lower the barriers to content...
I agree that we should be removing the barriers to adoption, which is the intent of DITA wiki. The complexity of the pharma content requirements practically...
... the guidance of a wizard for each data model. I agree. That is what I would define a DITA wiki. And I would expect any good DITA editor for non-technical...
To be truly collaborative, I think a DITA WIKI would need tiers of compliance. An idea or discussion needs to come into the system as freeform text, and...
Hi Chris, Very interesting thoughts. That could be a valid workflow model and I'm not sure how easy it would be to implement, but that's not what we're talking...
Before I enter the poll, I wanted to say that the future involves more smartphones, not less. So any future technologies will need to support the particular...
I'm totally in agreement. What I'm seeing in terms of interest has me already looking into emulators to test functionality against. Lisa Dyer and I have had a...
Hi Don, Regarding smartphone screen resolution, HVGA (320x480) is also very common, and WVGA (480x800) is becoming more so. There are also a number of other ...
Although a primary goal of identifying defects in current collaboration tools is to find ways in which DITA could help, it could restrict the free flow of...
To me, the three biggest flaws of wikis are: 1. They require contributors to learn a markup mechanism to input information instead of being able to add...
The only thing that has stopped me from using WIKIs for real and collaborative documentation is the lack of structure. I assume a DITA layer on a WIKI would...
The converse to this is that too much structure applied too early in the process can hinder output. This is why I enjoy working with Wiki, because then I can...
I'm in 100% agreement. I want to see a layering of structure over the collaborative material. I don't want to see a structure imposed on the collaborative...
