RE: [dita] DITA 1.2 suggestion--add format, scope, and type attributes for DITA elements missing them

["Grosso, Paul" <pgrosso@ptc.com>]

I'm not sure exactly what you mean by called but not stored
locally.  I'm thinking maybe you are talking about having
the output refer to the graphics as they sit in your
repository, but that is basically scope="external" (or
maybe "peer"), and usually graphics are treated as "local".

Without a scope attribute I don't know how you could indicate
different processing.  With a scope attribute, you could have 
different behavior for scope="local" and scope="peer". 

Scope="external" may not make sense for print/PDF, but could 
make sense for Web output.  I guess without the scope attribute 
you can look at the href value and make some guesses based on 
the form of the URI, but this seems sort of ad hoc and risky.  

paul

> -----Original Message-----
> From: JoAnn Hackos [mailto:joann.hackos@comtech-serv.com] 
> Sent: Monday, 2007 March 19 14:59
> To: Grosso, Paul; dita@lists.oasis-open.org
> Subject: RE: [dita] DITA 1.2 suggestion--add format, scope, 
> and type attributes for DITA elements missing them
> 
> Paul,
> How would the scope attribute affect a graphic image that is stored in
> another repository (specific to images)? We want to call the 
> images but we don't want them stored in the local directory.
> JoAnn
> 
> 
> -----Original Message-----
> From: Grosso, Paul [mailto:pgrosso@ptc.com] 
> Sent: Monday, March 19, 2007 12:41 PM
> To: dita@lists.oasis-open.org
> Subject: [dita] DITA 1.2 suggestion--add format, scope, and type
> attributes for DITA elements missing them
> 
> Add format, scope, and type attributes for DITA elements 
> that carry an href or other reference attribute, but which 
> do not have these attributes today.
> 
> One question here is whether the image element carry a scope 
> attribute.  The image element carries an href attribute, but 
> does not carry type, format, or scope.  The type and format 
> attributes aren't needed in this case since they are implied 
> by the image element.  Perhaps scope isn't either, but I wonder 
> if there are cases where scope=peer or scope=external would make 
> sense for an image and would determine if the graphic file is 
> copied to the output directory or not.  (Right now we behave as 
> though scope=local for image.)
> 
>