[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: My TC Action Items - DITA Help Technologies Guide and Referencing Proprietary Technologies
Hi --
Follow-up in two action items from the DITA TC call earlier today:
1. DITA Help SC Draft Publication
> Scott Prentice - draft reorganized document (June 2010)
- https://www.oasis-open.org/apps/org/workgroup/dita-help/download.php/38357/DHTG-reorg-0.1.pdf
> Stan Doherty - SC-approved final draft (April 2009)
- https://www.oasis-open.org/apps/org/workgroup/dita-help/download.php/32126/DHTG_v1_03232009.pdf
2. Working policy on referencing proprietary technologies in OASIS publications.
Here's the exchange between Chet, JoAnn, and myself on the topic of how we
reference proprietary technologies in Adoption publications. We can, but very
carefully.
See below.
Stan
-------- Forwarded Message --------
Subject: Re: Chet -- Need some OASIS guidance of referencing vendor products in OASIS whitepapers
Date: Fri, 5 Dec 2014 20:11:14 +0000
From: Hackos, Joann <joann.hackos@comtech-serv.com>
To: Chet Ensign <chet.ensign@oasis-open.org>
CC: Stan Doherty <stan@modularwriting.com>
Exactly. I thin we will be fine but we have to be inclusive about vendors.
JoAnn
Sent from my iPad
JoAnn Hackos
President
Comtech Services Inc
710 Kipling Street Suite 400
Lakewood CO 80215
303-232-7586
CIDM will be hosting the Content Management Strategies/DITA Europe 2014 conference in Munich, Germany November 18-19. More information at:
http://www.infomanagementcenter.com/DITAeurope/2014/index.htm
On Dec 5, 2014, at 12:00 PM, Chet Ensign <chet.ensign@oasis-open.org> wrote:
> Hi JoAnn -
>
> Good point. Coming from the DITA Adoption TC helps set the context. There should be no problem publishing something as a Committee Note or white paper from there. The context will communicate "To help you ramp up on DITA ...
>
> /chet
>
> On Fri, Dec 5, 2014 at 7:25 AM, Hackos, Joann <joann.hackos@comtech-serv.com> wrote:
>
> Hi Chet,
> Remember that we are publishing this information as a feature article from the DITA Adoption TC. It will not be part of a spec. Seems like this issue would then fall under committee notes.
> JoAnn
>
> Sent from my iPad
> JoAnn Hackos
> President
> Comtech Services Inc
> 710 Kipling Street Suite 400
> Lakewood CO 80215
> 303-232-7586
>
>
>
> CIDM will be hosting the Content Management Strategies/DITA Europe 2014 conference in Munich, Germany November 18-19. More information at:
>
> http://www.infomanagementcenter.com/DITAeurope/2014/index.htm
>
>
>
> On Dec 4, 2014, at 7:45 PM, Chet Ensign <chet.ensign@oasis-open.org> wrote:
>
>> Hi Stan, hi JoAnn,
>>
>> There are a couple of rules that govern aspects of this and I'll share my thoughts as well.
>>
>> The TC Process Commercial Terms and Conditions section (https://www.oasis-open.org/policies-guidelines/tc-process#commterms) specifically precludes doing anything that appears to endorse one product or another in a spec. ("Therefore, it generally is not acceptable to include manufacturer lists, service provider lists, or similar material in the text of a standard or in an annex (or the equivalent).") In addition, trademarked names, logos, etc. not owned by OASIS cannot be used in the name of a TC or in the title of a work product.
>>
>> There are a couple of ways, given the above, to do what you want. The TGF TC uses its wiki to maintain a listing of what it calls "Policy Products" - essentially examples of products or implementations that achieve specific elements of their specs. (See https://wiki.oasis-open.org/tgf/Policy%20Products). I believe the OBix TC is considering something similar. So you could use your wiki as a place to list informational information on products and services.
>>
>> The other way would be to publish a Committee Note on the subject, e.g. something like "Implementing DITA 1.2 in Commercial Products" or something like that.
>>
>> Either approach can work and I'm happy to give you more feedback on whatever approach you'd like to pursue.
>>
>> /chet
>>
>>
>> On Wed, Nov 26, 2014 at 3:50 PM, Stan Doherty <stan@modularwriting.com> wrote:
>>
>> Hi Chet --
>>
>> Two of the DITA TC subcommittees on which I work (Help and Technical Communications) have been developing whitepapers that capture the benefits of organizations moving to OASIS DITA 1.2 and DITA 1.3 (coming soon). Our target practitioners tend to be quite involved in making DITA work with various industry-standard, but proprietary tools and technologies, e.g. MadCap Flare, Syncrosoft WebHelp, or Design Science MathFlow. Whenever possible, we advocate open-source, vendor-neutral solutions for our readers. That said, in some areas our readers really need to understand how to integrate OASIS standards with their popular proprietary infrastructure. We're feeling kinda silly NOT referencing one or more of the target integration tools and technologies.
>>
>> Does OASIS have some guidelines that would help us figure this out?
>>
>> To your knowledge, are there other TCs that have figured this out and could serve as advisors?
>>
>> What do you think? Can you help us here?
>>
>> Many thanks in advance . . .
>>
>> Stan Doherty
>> DITA TechComm Subcommittee Co-chair
>> DITA Help Subcommittee Secretary
>>
>>
>> Stanley Doherty, Ph.D.
>> Member - OASIS DITA Technical Committee
>> ModularWriting.com
>>
>>
>>
>>
>> --
>>
>> /chet [§]
>> ----------------
>> Chet Ensign
>> Director of Standards Development and TC Administration
>> OASIS: Advancing open standards for the information society
>> http://www.oasis-open.org
>>
>> Primary: +1 973-996-2298
>> Mobile: +1 201-341-1393
>>
>> Check your work using the Support Request Submission Checklist at http://www.oasis-open.org/committees/download.php/47248/tc-admin-submission-checklist.html
>>
>> TC Administration information and support is available at http://www.oasis-open.org/resources/tcadmin
>>
>> Follow OASIS on:
>> LinkedIn: http://linkd.in/OASISopen
>> Twitter: http://twitter.com/OASISopen
>> Facebook: http://facebook.com/oasis.open
>
>
>
>
> --
>
> /chet [§]
> ----------------
> Chet Ensign
> Director of Standards Development and TC Administration
> OASIS: Advancing open standards for the information society
> http://www.oasis-open.org
>
> Primary: +1 973-996-2298
> Mobile: +1 201-341-1393
>
> Check your work using the Support Request Submission Checklist at http://www.oasis-open.org/committees/download.php/47248/tc-admin-submission-checklist.html
>
> TC Administration information and support is available at http://www.oasis-open.org/resources/tcadmin
>
> Follow OASIS on:
> LinkedIn: http://linkd.in/OASISopen
> Twitter: http://twitter.com/OASISopen
> Facebook: http://facebook.com/oasis.open
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]