[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: RE: [dita] DITA goes Nuclear?
Sounds like this might be something that should be forwarded to the DITA Adoption TC - they can work on setup issues, etc. Regards, Mary > -----Original Message----- > From: Larsen, Seraphim L [mailto:seraphim.l.larsen@intel.com] > Sent: Thursday, November 13, 2008 12:54 PM > To: Don Day; dita > Subject: RE: [dita] DITA goes Nuclear? > > Hi Don, > > The main difference is that the CPAN site is already organized to > support this usage model. The very first thing listed on the CPAN page > is "Perl Modules", and it takes you to a page with links for search or > for browsing a categorized list of modules. > > But specializations aren't even listed on the Resources page, and there > isn't any consistency in the descriptions of the few specializations > that are mentioned on the site. > > So, here would be my suggestions: > > (1) Create a place to put the specializations. Set up some kind of > base hierarchy / taxonomy scheme. Make it searchable. Post guidelines > on how it is intended to be organized. > (2) Create a standard for how they should be posted: which files to > include, what kind of documentation and samples to include. Document > this standard clearly. > (3) Post a few examples to get it started -- e.g., the already existing > specializations for Learning and Training, Troubleshooting, and Music, > which are listed in the Wiki Knowledgebase article, "Introduction to > Specializations" (but links either don't work, or point to > Sourceforge). > > Maybe Sourceforge is a better place, if that's where people are already > posting these? > > > Thanks, > > Seraphim Larsen > Intel Corporation * ECG TechComm > Chandler, AZ * (480) 552-6504 > My opinions only; I don't speak for Intel. > > > > -----Original Message----- > From: Don Day [mailto:dond@us.ibm.com] > Sent: Monday, November 10, 2008 8:33 AM > To: dita > Subject: RE: [dita] DITA goes Nuclear? > > Your suggestion has a lot of value, Seraphim. How would you see CPAN as > being like or different than the DITA Focus Area, http://dita.xml.org? > For > example, what kind of file hosting service and interface might be > needed by > that Drupal site to make it more equivalent? > > Regards, > -- > Don Day > Chair, OASIS DITA Technical Committee > Architect, Lightweight DITA Publishing Solutions > Email: dond@us.ibm.com > 11501 Burnet Rd. MS9033E015, Austin TX 78758 > Phone: +1 512-244-2868 (home office) > > "Where is the wisdom we have lost in knowledge? > Where is the knowledge we have lost in information?" > --T.S. Eliot > > > > From: "Larsen, Seraphim L" <seraphim.l.larsen@intel.com> > > To: dita <dita@lists.oasis-open.org> > > Cc: "Ogden, Jeff" <jogden@ptc.com>, Eliot Kimber > <ekimber@reallysi.com> > > Date: 11/06/2008 12:01 PM > > Subject: RE: [dita] DITA goes Nuclear? > > > > > > > I've always envisioned a DITA archive like the CPAN archive for Perl ( > http://cpan.org/). > > Could OASIS set up a site like that? > > If not, could something like that be hosted on sourceforge? > > > Seraphim Larsen > Intel Corporation * ECG TechComm > Chandler, AZ * (480) 552-6504 > My opinions only; I don't speak for Intel. > > > > > -----Original Message----- > From: Ogden, Jeff [mailto:jogden@ptc.com] > Sent: Thursday, November 06, 2008 10:18 AM > To: Eliot Kimber; dita > Subject: RE: [dita] DITA goes Nuclear? > > Eliot, I agree with the comments from both of your e-mails on this > topic. > > Is there a good place for people and organizations to informally share > new specializations? Part of the DITA area on xml.org? That might be > a > way to encourage sharing of DITA specializations that are not formally > standardized. It might be a good way to share early versions of new > specializations before they become standardized as well. > > If the specializations don't need to be formally standardized, would > the > DITA Adoption TC be a better forum for encouraging this sort of thing > than the DITA TC with its focus on standards development? > > -Jeff > > > -----Original Message----- > > From: Eliot Kimber [mailto:ekimber@reallysi.com] > > Sent: Thursday, November 06, 2008 12:05 PM > > To: dita > > Subject: Re: [dita] DITA goes Nuclear? > > > > On 11/4/08 5:01 PM, "Eliot Kimber" <ekimber@reallysi.com> wrote: > > > > > On 11/4/08 3:10 PM, "Robert D Anderson" <robander@us.ibm.com> > wrote: > > > > > >> So - is there anybody on the TC interested in working on a > > specialization > > >> for the nuclear industry? If so, we can set up a subcommittee to > start > > work > > >> based on what has already been done. If so, please send a note > briefly > > >> describing your interest level (observer vs active participant). > If > > you'd > > >> rather not send directly to the list at this point, you can send > to > me > > and > > >> I'll collect responses; if you do that, please also copy Don Day, > as > > I'll > > >> be offline some of the next week and want to be sure I don't miss > any > > >> notes. > > > > > > While I'm sure such a specialization is quite valuable and it's > exciting > > to > > > see this type of activity happening, I worry that we are starting > to > set > > a > > > precedent by which every community of interest that might find DITA > > useful > > > wants to be a subcommittee. > > > > > > I don't think that's either necessary or productive in the long > run. > > DITA is > > > expressly designed to enable unilateral extension that does not > need > to > > be > > > coordinated with the base standard in order to be both reliably > > > interchangeable and potentially useful as a standard in its own > right. > > > > > > There's absolutely no reason that something like a nuclear industry > > > specialization couldn't be developed as a completely separate > effort > > within > > > whatever standards community serves the nuclear power industry. > > > > Michael Priestly pointed out privately that there might be > communities > of > > interest that do not have an existing standards-making body that > could > > host > > a DITA specialization standard, in which case the DITA TC would be a > > natural > > home. I agree completely. > > > > My main intent is that it's clear to the DITA community at large that > > standardization within the DITA TC is not a *requirement* for > standardized > > DITA specialization, nor is standardization within OASIS a > requirement. > > > > For example, if the Air Transport Association wanted to define an > > aircraft-industry-specific set of specializations, it would make > sense > for > > the ATA to host that activity--no need for it to be done under the TC > just > > because it happens to be a DITA-based XML application. > > > > Cheers, > > > > Eliot > > > > ---- > > Eliot Kimber | Senior Solutions Architect | Really Strategies, Inc. > > email: ekimber@reallysi.com <mailto:ekimber@reallysi.com> > > office: 610.631.6770 | cell: 512.554.9368 > > 2570 Boulevard of the Generals | Suite 213 | Audubon, PA 19403 > > www.reallysi.com <http://www.reallysi.com> | > http://blog.reallysi.com > > <http://blog.reallysi.com> | www.rsuitecms.com > <http://www.rsuitecms.com> > > > > > > --------------------------------------------------------------------- > > 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 > > > --------------------------------------------------------------------- > 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 > > > --------------------------------------------------------------------- > 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 > > > > > > --------------------------------------------------------------------- > 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 > > > --------------------------------------------------------------------- > 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
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]