Re: [dita-busdocs] Groups - Designing DITA Abstract Topic Types.ppt uploaded

["Rob Hanna" <rob@ascan.ca>]

However, title is certainly straddling both metadata and content. I suggest shortdesc is the same if we agree that shortdesc is rendered as content.


Ask me about the Society for Technical Communication (STC) to learn more on how the STC serves your business and professional needs. Visit http://www.stc.org/story.

-----Original Message-----
From: "Ann Rockley" <rockley@rockley.com>
Date: Wed, 16 Jun 2010 14:06:20 
To: <rob@ascan.ca>; 'Tim Grantham'<tgrantham@timgrantham.com>; <dita-busdocs@lists.oasis-open.org>
Subject: RE: [dita-busdocs] Groups - Designing DITA Abstract Topic Types.ppt uploaded

I would argue that what makes good metadata (e.g., link teaser) is not the
same as content. Rendering metadata in content makes one or the other less
effective.

-----Original Message-----
From: Rob Hanna [mailto:rob@ascan.ca] 
Sent: Wednesday, June 16, 2010 1:59 PM
To: Tim Grantham; dita-busdocs@lists.oasis-open.org
Subject: Re: [dita-busdocs] Groups - Designing DITA Abstract Topic Types.ppt
uploaded

I have to disagree with Steve and try to hold you to your original design.
"Link Teaser" is an online publishing implementation of the short
description - however the implementation of publishing shouldn't overrule
good semantic design of the content. Particularly when the implementation is
media dependant.

We were at one time agreed that the short description played a dual role of
content and metadata. In other words, while the short description served as
metadata on a topic it still has to be rendered inline as content. How can
we create a short description of a rule that isn't the rule and have them
both rendered in the content? Remember that short description is a child of
abstract.

I believe strongly in what you'd stated in our last meeting that other
abstract types may specialize the content from either short description or
abstract depending upon the requirements for the information type. In the
case of the advisory type, I believe that this must be specialized from
short description unless you can think of an element more granular than rule
that can be used in the information type.

BTW I must extend my regrets for missing today's meeting. I am under the gun
to get a report out.

Cheers,

Rob Hanna


Ask me about the Society for Technical Communication (STC) to learn more on
how the STC serves your business and professional needs. Visit
http://www.stc.org/story.

-----Original Message-----
From: "Tim Grantham" <tgrantham@timgrantham.com>
Date: Wed, 16 Jun 2010 13:43:59 
To: <dita-busdocs@lists.oasis-open.org>
Subject: FW: [dita-busdocs] Groups - Designing DITA Abstract Topic Types.ppt
uploaded


-----Original Message-----
From: Tim Grantham [mailto:tgrantham@timgrantham.com] 
Sent: Friday, June 11, 2010 9:55 AM
To: 'Steve Manning'
Subject: RE: [dita-busdocs] Groups - Designing DITA Abstract Topic Types.ppt
uploaded

I agree, Steve.

If no-one else objects, I will modify my presentation and <advisory> schema
to specialize <rule> from <abstract>. In fact, it looks more and more to me
that an abstract topic types will probably always specialize from the
<abstract> element, for the reasons you cite.

There is also, as theoretical physicists would say, a nice symmetry about
specializing the key distinguishing element of an abstract topic type from
the <abstract> element. :-)

Regards,
Tim.

-----Original Message-----
From: Steve Manning [mailto:steven.manning@sympatico.ca]
Sent: Friday, June 11, 2010 9:14 AM
To: dita-busdocs@lists.oasis-open.org
Subject: Re: [dita-busdocs] Groups - Designing DITA Abstract Topic Types.ppt
uploaded

Tim,

I have a concern with specializing shortdesc for rule/etc.  While I fully
support the idea of capturing the key information about the topic in a
shortdesc-like element, I am uneasy with using shortdesc as it has 
a dual purpose.    In addition to being the "initial paragraph-like 
content of a topic," it is also "intended to be used as the link preview 
for searching.   The content you might capture as a rule, might not 
actually be effective as a link-teaser.  As an alternative, could the
initial paragraph (like rule) element be specialized off abstract instead?
That way, you could have both rule and shortdesc in a topic and ensure they
are appropriate to their individual uses.

/steve





07/06/2010 11:18 AM, tgrantham@timgrantham.com wrote:
> Here it is, with corrections for typos.
>
>   -- Tim Grantham
>
> The document named Designing DITA Abstract Topic Types.ppt has been 
> submitted by Tim Grantham to the DITA Enterprise Business Documents SC 
> document repository.
>
> Document Description:
> Proposes a set of practices for designing abstract topic types
>
> View Document Details:
> http://www.oasis-open.org/committees/document.php?document_id=38147
>
> Download Document:
> http://www.oasis-open.org/committees/download.php/38147/Designing%20DI
> TA%20Abstract%20Topic%20Types.ppt
>
>
> PLEASE NOTE:  If the above links do not work for you, your email 
> application may be breaking the link into two pieces.  You may be able 
> to copy and paste the entire link address into the address field of your
web browser.
>
> -OASIS Open Administration
>    


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



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