references to ditabases without an explicit topicid

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

Our developers are trying to understand what it means 
to have a reference to a ditabase from a topicref in
a map where the href value does not include a fragment 
identifier (e.g., "path" rather than "path#topicid").
Specifically, is just the first topic picked up or
all the topics?

The DITA 1.0 Architectural Spec doesn't seem to 
address this.

In the DITA 1.0 Language Specification, there are 
a few references that seem to address this issue:

In the Language Spec. in the descriptions for the 
conref attribute on topic, concept, reference, and 
task elements it says in part:

 During output processing, a lookup process will pull the
 contents of the first topic into the calling topic markup
 that has the conref attribute.

And a bit later in the same description it says:

    Target elsewhere in the same file:
        conref="#topicid"

    First topic in a different file:
        conref="filename.xml"

    Specific topic in different file:
        conref="filename.xml#topicid"

And in the href description for the link element in a 
topic, it says:

   Target elsewhere in the same file:
        conref="#topicid"

    First topic in a different file:
        conref="filename.dita"

    Specific topic in different file:
        conref="filename.dita#topicid"

There is nothing specific about this one way or another in the 
other href descriptions for the elements topicref and xref.

Using the DITA Open Toolkit, for html output, only one link 
appears in the index.html file, but all of the topics from 
the ditabase were included in the other .html file.

Can someone confirm what is the expectation when one encounters
an href to a ditabase without a fragment identifier on a topicref.
Should just the first topic from the ditabase be included or 
should all of the topics from the ditabase be included?

paul