Carol, Where is the spreadsheet? I don't see
it.
I really like all these suggestions for seeding the focus
discussions. I think the spec and the language ref would be great starter
content. We could definitely ask people to submit example code blocks.
Adding comments would be fine for the KB pages. I'd like to see what someone
might suggest for the list of topic-based authoring books that I just
added.
Carol, Can you get my blog renamed? How about TopicsRUs
by JoAnn Hackos or is that too silly?
JoAnn
WRT Bruce's message, I did turn Drupal's comment feature
back on, so at the bottom of every page, there's an "add comment" link.
Editorial Board members could periodically review any comments posted and make
decisions about incorporating them into the main text of the
page.
Note also that I've edited the footer for the site. Now
we have links to the KB, Today, and Wiki overview pages with instructions for
adding content to each. Please let me know if you think this
works.
WRT Michael's message, I'll have to check with Mary
McRae.
--carol
Along these lines, I was thinking of defining shadow
pages for some of the architecture pages, so that people could comment, and
then the comments could be edited into the architecture
pages.
This
would help a lot with keeping up with abstracts of articles, for
example.
Bruce
It just occurred
to me that one way to kickstart/focus discussion in the community area would
be to provide the existing DITA 1.0 spec as a set of starter topics, which
people can then comment on, respond to, etc. - effectively letting the
community annotate the spec.
How
hard would this be, and would it be ok/appropriate from an OASIS point of
view? I'm not suggesting this as a prereq for launch, but thinking it could
be a useful follow-on activity.
Michael Priestley
IBM DITA Architect
Classification Schema PDT
Lead
mpriestl@ca.ibm.com
