RE: [dita] Question about syntax for the @anchorref attribute

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

Hi Eliot,

Our emails just crossed.

So do you agree that anchorref's datatype is, like conref and href,
a URI reference?

paul

> -----Original Message-----
> From: Eliot Kimber [mailto:ekimber@reallysi.com]
> Sent: Tuesday, 2010 November 30 9:02
> To: Kristen Eberlein; dita
> Subject: Re: [dita] Question about syntax for the @anchorref attribute
> 
> This syntax for a reference to an element iwthin the map cannot be
> correct:
> 
> <map id="B" anchorref="map1.ditamap/a1²>
> 
> Because the fragment identifier part (the "a1" in this case) is here
> encoded
> as a part of the main URL, which is not sensical unless "map1.ditamap"
> happens to be a directory and "a1" is the filename of a map, which we
> can
> assume was not the intent.
> 
> The correct syntax must then be that as defined in the general rules
> for
> URIs, name "map1.ditamap#a1".
> 
> Cheers,
> 
> Eliot
> 
> On 11/30/10 7:06 AM, "Kristen Eberlein" <keberlein@sdl.com> wrote:
> 
> > Hi, TC members.
> >
> > Iıve been asked about the correct syntax for the @anchorref attribute
> on the
> > <map> element. As Iıve read through various spec topics, Iıve gotten
> confused.
> > I think this might be an area that that we need to consider for
> future
> > clarification.
> >
> > Question
> > In map1.ditamap, an anchor is defined with an @id attribute set to
> ³a1².
> >  <map id="A">
> >    <title>MyComponent tasks</title>
> >    <topicref navtitle="Start here" href="start.dita" toc="yes">
> >      <navref mapref="othermap2.ditamap"/>
> >      <navref mapref="othermap3.ditamap"/>
> >      <anchor id="a1"/>
> >    </topicref>
> >  </map>
> > In map2.ditamap, which contains the content to be pulled into
> map1.ditamap at
> > the anchor point, what syntax should be used for the @anchorref
> attribute?
> >  <map id="B" anchorref="?">
> >    <title>This map is pulled into the MyComponent task map</title>
> >    ...
> >  </map>
> > And I assume that map2.ditamap must be referenced somewhere in
> map1.ditamap in
> > order for the <anchor> element to be resolved?
> > Topics in the DITA 1.2 spec
> >
> > The topics in the DITA 1.2 spec suggest several distinct
> possibilities; which
> > is correct?
> >
> > 2.1.2.2.3 DITA map elements
> > http://docs.oasis-open.org/dita/v1.2/cs01/spec/archSpec/ditamap-
> elements.html#
> > ditamap-elements
> > Read down to the ³Example of maps that use the <anchor> element and
> the
> > @anchorref attribute² section; it suggests that the syntax should be
> as
> > follows:
> >
> > <map anchorref="a1">
> > ...
> > </map>
> >
> > 3.1.2.1.1 map
> > http://docs.oasis-open.org/dita/v1.2/cs01/spec/langref/map.html#map
> > The explanation for the @anchorref attribute suggests that the syntax
> should
> > be the following:
> >
> > <map id="B" anchorref="map1.ditamap/a1²>
> > ...
> > </map>
> >
> >
> > 2.1.3.4.2 URI-based (direct) addressing
> > http://docs.oasis-open.org/dita/v1.2/cs01/spec/archSpec/uri-based-
> addressing.h
> > tml#uri-based-addressing
> > The section titled ³URI reference syntax examples² lists the
> following syntax
> > for targeting an element within a map:
> >
> > "http://example.com/map.ditamap#elementID"; (and a value of "ditamap"
> for the
> > format attribute)
> > Best regards,
> > Kris
> > Kristen James Eberlein l DITA Architect and Technical Specialist l
> SDL
> > Structured Content Technologies Division l (t) + 1 (919) 682-2290 l
> > keberlein@sdl.com <mailto:keberlein@sdl.com>
> >   <http://www.sdl.com/>
> > Please consider the environment before printing this e-mail
> >
> 
> --
> Eliot Kimber
> Senior Solutions Architect
> "Bringing Strategy, Content, and Technology Together"
> Main: 512.554.9368
> www.reallysi.com
> www.rsuitecms.com
> 
> 
> ---------------------------------------------------------------------
> 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