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

 


Help: OASIS Mailing Lists Help | MarkMail Help

dita message

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


Subject: Re: [dita] Why There are Constraints on Conref


On 9/25/09 5:31 PM, "JoAnn Hackos" <joann.hackos@comtech-serv.com> wrote:

> Are we clear in saying that one cannot conref between Task and General
> Task at all? or only from Task to General Task? Is it possible to conref
> from General Task to Task?
> 
> From loose to more constrained, will the conref work?
> So can I conref a prereq from General Task to a prereq to Task but not
> vice versa? 
> 
> But, I cannot conref a <step> from Task to General Task even though they
> are in both models?
> 
> Would someone please state all the use cases simply? I'm trying to be
> clear in writing the arch spec and the feature description and I'm still
> confused by all the rhetoric being flung around.

Give a strict task and a general task:

1. Can conref elements from strict task into general task
2. Cannot conref elements from general task into strict task

That is, you can *always* conref more-constrained elements into
less-constrained elements. You can *never* conref less-constrained elements
into more-constrained elements.

Cheers,

Eliot
----
Eliot Kimber | Senior Solutions Architect | Really Strategies, Inc.
email:  ekimber@reallysi.com <mailto:ekimber@reallysi.com>
office: 610.631.6770 | cell: 512.554.9368
2570 Boulevard of the Generals | Suite 213 | Audubon, PA 19403
www.reallysi.com <http://www.reallysi.com>  | http://blog.reallysi.com
<http://blog.reallysi.com> | www.rsuitecms.com <http://www.rsuitecms.com> 



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