[
Lists Home |
Date Index |
Thread Index
]
I think I know what you mean, but can you be more specific about the
"feature" you're suggesting? I haven't looked at Mekon's tool yet, but
what you describe sounds like a FM structure application. I can open
DITA files in FM without their tool .. what does it provide, and how can
we add this feature in a way that isn't specific to Mekon's tool?
...scott
JoAnn Hackos wrote:
>I think that will be useful. We've also been using Mekon's DITA to
>FrameMaker conversion for final formatting of the DITA book. It's very
>nice. How about a DITA conversion for output?
>
>JoAnn
>
>-----Original Message-----
>From: Esrig, Bruce (Bruce) [mailto:esrig@lucent.com]
>Sent: Sunday, March 19, 2006 4:25 AM
>To: Scott Prentice
>Cc: dita-fa-edboard@lists.xml.org
>Subject: RE: [dita-fa-edboard] Updated product-filter form
>
>The criteria are coming together really nicely. This will be a great
>asset to the community (as well as a demo of the taxonomy module).
>
>Should we add the following the following feature to products and/or
>services?
>
> [ ] XML transformation Supports conversion/Support for conversion
>between other XML languages and DITA.
>
>The following comments only affect how we describe the criteria.
>
>Best wishes,
>
>Bruce
>
>===========
>
>1. What do you get as a result of selecting a few filter criteria? It
>seems to be an OR logic.
>
>"Select one or more features to get a (reverse!) alphabetical listing of
>products that match ANY of the selected features."
>
>2. Particular items in Products
>
>Delivered with DITA Provides the DITA language and a production engine.
>
>In-place preview of conrefs Displays referenced content at the
>referencing location.
>
>Conditionals and filtering Supports enabling/disabling/flagging through
>conditional parameters.
>
>Workflow management
>Supports ...
>
>Workflow automation
>Supports ...
>
>3. Same items in Services, rearranged and re-glossed
>
>Principles:
> - Getting started should be top left
> - Conceptual services should be above development services
> - Say "Support for" before most services
>
> [ ] Getting started [ ] Training
> [ ] Consulting [ ] Implementation
> [ ] Information architecture Support for structural design for
>collections of topics.
> [ ] DITA specialization Support for customizing DITA information
>types.
> [ ] Domain specialization Support for applying DITA within a domain.
> [ ] Terminology Support for term management, taxonomy, ontology,
>indexing.
> [ ] XSL/XSLT customization [ ] Ant customization
> [ ] Product extensions Development of FrameMaker plugins, XMetaL
>development, etc.
> [ ] Provided by an OASIS member
>
>-----Original Message-----
>From: Scott Prentice [mailto:sp@leximation.com]
>Sent: Friday, March 17, 2006 3:55 PM
>To: dita-fa-edboard@lists.xml.org
>Subject: Re: [dita-fa-edboard] Updated product-filter form
>
>OK .. here's the latest version ..
>
> http://dita.xml.org/products
>
>I've integrated the Products and Services forms onto the same page using
>
>JavaScript to dynamically swap the areas. When I set this up on the
>final page, I'll make it actually two separate pages to avoid using
>JavaScript, but the apparent functionality will be the same. When you go
>
>to the "Products and Services" page, you'd see the description and the
>"Select product features" form will be the default., when you click the
>"Select service offerings" tab, it will actually switch to a different
>page rather than using JS to make the swap.
>
>Let me know if you have any objections or concerns (or if I
>misunderstood anyone's suggestions) .. if I don't hear anything, I'll
>start setting up the vocabularies accordingly.
>
>...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
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>
>
>---------------------------------------------------------------------
>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
>
>
>
>
>
>
>
>
>
|
