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

 


Help: OASIS Mailing Lists Help | MarkMail Help

dita-help message

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


Subject: RE: [dita-help] Current best practices for context hooks


Hi, Chris.

So you are adding the <resourceid> element to the <prolog> element within the DITA topic?

Best regards,

Kris
Kristen James Eberlein l DITA Architect and Technical Specialist l SDL Structured Content Technologies Division l (t) + 1 (919) 682-2290 l keberlein@sdl.com
 
Please consider the environment before printing this e-mail




-----Original Message-----
From: Goolsby, Chris [mailto:cgoolsby@ptc.com] 
Sent: Thursday, January 06, 2011 9:36 AM
To: Kristen Eberlein; dita-help@lists.oasis-open.org
Cc: Ymte Westra
Subject: RE: [dita-help] Current best practices for context hooks

At PTC Arbortext, we use the resourceid in topics to hold our context hooks. The stylesheet passes the value in the resourceid to the published HTML, and the product grabs the right topic based on that value.

Regards.

Chris Goolsby
PTC

-----Original Message-----
From: Kristen Eberlein [mailto:keberlein@sdl.com] 
Sent: Thursday, January 06, 2011 9:29 AM
To: dita-help@lists.oasis-open.org
Cc: Ymte Westra
Subject: [dita-help] Current best practices for context hooks

What are people currently doing for context hooks? SDL has some clients who cannot wait for DITA 1.3; any current best practices that we should practice?

Best regards,
Kris

Kristen James Eberlein l DITA Architect and Technical Specialist l SDL Structured Content Technologies Division l (t) + 1 (919) 682-2290 l keberlein@sdl.com
 
Please consider the environment before printing this e-mail


-----Original Message-----
From: Tony Self [mailto:tself@hyperwrite.com] 
Sent: Monday, December 06, 2010 1:33 AM
To: dita-help@lists.oasis-open.org
Subject: [dita-help] Help Features in DITA 1.3

Greetings colleagues

Now that 1.2 has been released, we have to start thinking about 1.3. You
will probably recall that the Help Subcommittee was established to make
recommendations for 1.3; it wasn't anticipated that 1.3 would be so far
away.

So far, we have proposals for spec changes to better handle context hooks,
and window definitions. 

We have discussed in the past the possibility of a specialisation for
integrated or embedded user assistance content.

There has been some negative feedback from the community about the perceived
complexity of 1.2, with new information types, constrained versions of some
types, and a (perceived) mushrooming in the number of elements. 

My feeling is that the context hook and window definitions should be built
into the base content model. My feeling is that we should not have a
specialised information type for UA, mainly because I don't think the
community is demanding such a thing.

What do you all think? 

Tony Self



---------------------------------------------------------------------
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]