[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: Re: [dita] Inheritance of attributes through mapref
On 4/14/09 10:51 AM, "Michael Priestley" <mpriestl@ca.ibm.com> wrote: > > Fair enough. Navref is delayed transclusion, which may or may not be local > (one reason to delay transclusion is because the resources aren't local). > > It remains logical for someone to want a cross-plugin navigation > reference/transclusion that cannot be resolved at build time but will be > resolved at runtime (ie format=ditamap scope=peer). > > The rationale for scope=peer applies as well to map resources as it does to > topic resources. Fair enough. That suggests that there needs to be a way to explicitly single author intent of navigation or transclusion. Clearly the navref element type means transclusion but I don't think we have anything that means navigation in the 1.2 spec, do we? Cheers, E. ---- 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]