OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.

 


Help: OASIS Mailing Lists Help | MarkMail Help

dita-adoption-help message

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]


Subject: RE: [dita-adoption-help] Criteria for determining which tools to include in the DHTG...


One key characteristic is that you access Help when you have a problem,
and you locate one or more topics that are relevant to the problem. Help
delivery, then, is mostly about relevance. Another is that Help delivery
is carried out by an application. It is possible to search out a CHM and
launch it as one would launch a PDF book, but then there's a strong
argument that you are using it as a standalone publication and not as
online help.

If we can assume that users expect context sensitive help integrated
with the application, then PDF becomes harder and harder to justify.

We could just list typical Help formats and rule out PDF by fiat.

	/B

> -----Original Message-----
> From: Scott Prentice [mailto:sp10@leximation.com] 
> Sent: Monday, September 27, 2010 3:32 PM
> To: dita-adoption-help@lists.oasis-open.org
> Subject: [dita-adoption-help] Criteria for determining which 
> tools to include in the DHTG...
> 
> Hi...
> 
> This action item of mine is a bit overdue. Here's what I'm 
> thinking should be the criteria ..
> 
> - A tool can be included in the DHTG if that tool can consume 
> or create DITA, and can export out-of-the-box, through the 
> tool's UI, at least one "Help" format.
> 
> Even if that tool is just using the OT to generate this Help 
> format, as long as it installs the OT to do that, it can be 
> in the DHTG. This probably opens the door to many DITA 
> authoring tools, but excludes tools that do not themselves 
> consume DITA in some way. It would not include a tool that 
> just converts from one format to another, since this would 
> have nothing to do with DITA.
> 
> Then there is the issue of defining what constitutes a "Help" 
> format. I think that for the purposes of the DHTG, a Help 
> format is one that's described in the "Help Delivery 
> Technologies" section of the DHTG. How we decide what to put 
> in that section .. well, I suppose that's up for discussion. 
> There are two formats that I can see might be considered "on 
> the fence" of being a Help format or not .. PDF and ePub. 
> There are people who use PDF as the "online Help system," and 
> therefore this would be considered a Help format (I'd think) 
> .. even though I personally think this is a bad use of PDF. 
> But what about ePub? What exactly does make something a Help format?
> 
> Something for further discussion, I'd think.
> 
> Cheers,
> 
> ...scott
> 
> 
> ---------------------------------------------------------------------
> 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_workgr
> oups.php 
> 
> 


[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
https://lists.oasis-open.org/archives/dita-adoption-help/201009/msg00018.html
lists.oasis-open.org
crawl=CC-MAIN-2020-05
8267
application/http; msgtype=response
sha1:XME5UEGNJ2URT6DXUG4E4I3UPI2X734L
<urn:uuid:c4944dfe-0b44-4e16-ac72-45b47824b7cc>
2020-01-25T07:36:11Z
34.233.166.49
text/html
sha1:EVBUZU4R6ISLRLU5WQ7OIQCWGD4SYEBT
<urn:uuid:f2a01219-f183-4d3a-b371-e91628a2dce0>
https://lists.oasis-open.org/archives/dita-adoption-help/201009/msg00018.html
response
<urn:uuid:546caf22-1600-4711-9ee7-128df0fb9eb5>
isPartOf: CC-MAIN-2020-05
publisher: Common Crawl
description: Wide crawl of the web for January 2020
operator: Common Crawl Admin (info@commoncrawl.org)
hostname: ip-10-67-67-43.ec2.internal
software: Apache Nutch 1.16 (modified, https://github.com/commoncrawl/nutch/)
robots: checked via crawler-commons 1.1-SNAPSHOT (https://github.com/crawler-commons/crawler-commons)
format: WARC File Format 1.1
conformsTo: http://iipc.github.io/warc-specifications/specifications/warc-format/warc-1.1/