[
Lists Home |
Date Index |
Thread Index
]
OK .. how's this ..
http://dita.xml.org/products
(need to add descriptions for some DITA and CMS items, but I have to run
out now)
...scott
JoAnn Hackos wrote:
>Hi Scott,
>I think Bruce's list on CMSs is workable. Localization/translation
>vendor supports is probably a separate item. You might want to include
>them as a separate category.
>
>JoAnn
>
>-----Original Message-----
>From: Scott Prentice [mailto:sp@leximation.com]
>Sent: Friday, March 17, 2006 11:39 AM
>To: Esrig, Bruce (Bruce)
>Cc: dita-fa-edboard@lists.xml.org
>Subject: Re: [dita-fa-edboard] Updated product-filter form
>
>Good suggestions .. versioning can go, but I do think that workflow is
>important since it's not always part of the system. I guess the question
>
>is, how detailed should we get in this? More details may provide more
>information, but when does it get to be too much? I have no problem
>adding Bruce's suggestions (that built on JoAnn's) .. is this enough of
>a CMS breakdown? What about localization/translation?
>
>I'm not clear what is defined as a feature vs. included .. are they
>equally balanced? It's already a pretty big list and if the features
>column is much longer than the included column, it may not make sense ..
>
>can you provide an example listing?
>
>Services looks good .. I'll get started on that while we refine the
>Products items.
>
>Thanks!
>
>...scott
>
>
>Esrig, Bruce (Bruce) wrote:
>
>
>
>>Comments to build on JoAnn's feedback (below), which she intended for
>>
>>
>this list.
>
>
>>Content management (based on a database, includes map-level and
>>
>>
>topic-level linking and link management)
>
>
>>CMS integration (includes unique IDs, local navigation of remote links)
>>Workflow management (ability to set state within a workflow) <!-- omit?
>>
>>
>-->
>
>
>>Workflow automation (dependencies, triggers, actions)
>>
>>============
>>
>>Could we try the list of checkboxes as a two-column table (Feature /
>>
>>
>Includes) ?
>
>
>>============
>>
>>Services area:
>>
>> OASIS member
>> Training
>> Consulting
>> Implementation
>> Getting started
>> Terminology (term management, taxonomy, ontology, indexing)
>> Information architecture (structural design for collections of
>>
>>
>topics)
>
>
>> DITA specialization (expertise in customizing DITA)
>> Domain specialization (expertise in applying DITA within a domain)
>> XSL/XSLT customization
>> Ant customization
>> Product extensions (FrameMaker plugins, XMetaL development, .. ??)
>>
>>============
>>
>>JoAnn wrote:
>>
>>Content management also has devisions
>>Version control is a standard of CM systems
>>Workflow management is almost a standard
>>
>>But breaking out version control doesn't make sense to me. No CMS lacks
>>version control. It's one of the core functions and we're not learning
>>anything about the product by asking for this. There are other
>>characteristics of a CMSs that are more important. Like unique Ids
>>generated by the system put into every file. Like a database underlying
>>the CMS, not a file server system. Like being able to support DITA maps
>>in the repository. Like link control and reporting.
>>
>>Anyway -- I recommend removing version control at the least.
>>
>>JoAnn
>>
>>-----Original Message-----
>>From: Scott Prentice [mailto:sp@leximation.com]
>>Sent: Thursday, March 16, 2006 10:39 PM
>>To: dita-fa-edboard@lists.xml.org
>>Subject: [dita-fa-edboard] Updated product-filter form
>>
>>
>>Hi...
>>
>>I've moved the filtering forms to the main Products and Services
>>
>>
>(rather
>
>
>>than being on their own pages), something like this ..
>>
>> http://dita.xml.org/products-services
>>
>>I've updated the Product filtering form, see the following URL for an
>>example (I'll move it to the real page once we finalize the terms) ..
>>
>> http://dita.xml.org/products
>>
>>This includes all of the dita-specific fields that we discussed at the
>>meeting this morning. Please look it over and let me know if you want
>>
>>
>to
>
>
>>change anything (no nits too small to pick). Note that this form won't
>>work properly just yet since I haven't set up the corresponding vocab
>>terms yet.
>>
>>For Services, here are the "features" I was thinking of using ..
>>
>> OASIS member
>> XSL development
>> Ant development
>> DITA specializations
>> System setup
>> Training
>> Consulting
>> Development
>> Product augmentation (FrameMaker plugins, XMetaL development, ..
>>
>>
>??)
>
>
>>Please let me know if you have any additions/corrections/objections ..
>>
>>
>?
>
>
>>The Resource Directory is all set up and ready to go. I've migrated all
>>
>>
>
>
>
>>of the items to individual nodes and assigned the terms as it seemed
>>appropriate ..
>>
>> http://dita.xml.org/resource-directory
>>
>>All of the items in the resource directory will have my name on them
>>(scottp), I can reassign them to the appropriate owners as needed. (I
>>assigned the "Introduction to DITA" to Jen). Let me know if you see any
>>
>>
>
>
>
>>problems with this.
>>
>>One issues that I've run into ..
>>
>>- The "URL" fields for the Products, Services, and Resources items all
>>tack on the "http://"; prefix regardless of the actual value of that
>>field. So .. none of the links work since they are all
>>"http://http://www.blahblah.com";. I thought about entering the URLs
>>without the "http://"; .. but I'm assuming this is a bug that can be
>>fixed since most people are going to enter the full URL and won't
>>
>>
>notice
>
>
>>that the link doesn't work.
>>
>>...scott
>>
>>
>>
>>
>>---------------------------------------------------------------------
>>This publicly archived list is provided by OASIS for the use of the
>>Editorial Board of the XML.org DITA Focus Area. Subscription and
>>posting privileges are reserved for members of the Editorial Board;
>>others should contact communications@oasis-open.org for assistance.
>>
>>[Un]Subscribe: dita-fa-edboard-[un]subscribe@lists.xml.org
>>List archives: http://lists.xml.org/archives/dita-fa-edboard
>>Committee homepage: http://www.oasis-open.org/committees/dita
>>
>>---------------------------------------------------------------------
>>This publicly archived list is provided by OASIS for the use of the
>>Editorial Board of the XML.org DITA Focus Area. Subscription and
>>posting privileges are reserved for members of the Editorial Board;
>>others should contact communications@oasis-open.org for assistance.
>>
>>[Un]Subscribe: dita-fa-edboard-[un]subscribe@lists.xml.org
>>List archives: http://lists.xml.org/archives/dita-fa-edboard
>>Committee homepage: http://www.oasis-open.org/committees/dita
>>
>>
>>
>>
>>
>>
>>
>>
>>
>
>
>---------------------------------------------------------------------
>This publicly archived list is provided by OASIS for the use of the
>Editorial Board of the XML.org DITA Focus Area. Subscription and
>posting privileges are reserved for members of the Editorial Board;
>others should contact communications@oasis-open.org for assistance.
>
>[Un]Subscribe: dita-fa-edboard-[un]subscribe@lists.xml.org
>List archives: http://lists.xml.org/archives/dita-fa-edboard
>Committee homepage: http://www.oasis-open.org/committees/dita
>
>
>
>
>
>
>
>
>
|
