[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: Re: [dita] Meaningful Values for type= on xref and topicref
On 5/22/09 9:26 AM, "Michael Priestley" <mpriestl@ca.ibm.com> wrote: >> It would probably make >> sense that unqualified type names can only refer to standard-defined > types >> since that's the only context in which they are unambiguous. > > That makes sense for xref, but I don't think it's necessary for topicref. > On an xref, type="newpara" might be a link to mytopic/newpara or > yourtopic/newpara. But on topicref, it shouldn't be ambiguous. When a > topicref points to a DITA resource, it's a topic - and the topic's class > attribute is always somewhat redundant, since the name of the element and > the name of the specialization package are the same. I know it's established convention that the topic module name and the topic type name are the same, but is that actually required by the spec? 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]