I am following up on my predecessor's question and the thoughtful
I understand the two methods discussed for defining extensions,
independent schemas and inheritance. The issue I am confronting
now is making a DiGIR portal work with either extension method.
On the DiGIR provider side, when defining a resource that is 'pulling'
from 2 independent schemas you have to define 2 <conceptualSchema>
data elements. Examination of the resource_name.xml file shows
2 <conceptualSchema> elements with 2 schemaLocation attributes.
On the DiGIR portal side, or more accurately in the presentation servlet,
the Information Domains are defined in presentation.xml. The issue as I
see it is that the Information Domain structure only allows for 1
<conceptualSchema> to be defined. I tried tests with adding a
<conceptualSchemas> wrapper around 2 <conceptualSchema> elements, and
tests with 2 stand-alone <conceptualSchema> elements both generating errors.
What/which schemaLocation namespace should be used in the Information Domain
document when trying to list provider resources that are defined with 2
<conceptualSchema>s? Or am I barking ( DiGIR-ing ) up the wrong tree?
I tried tests using inheritance and received prefix label errors. These errors
were more due to my lack of grace in this realm than anything else, but my gut
feel was that the errors were due to a relationship between the <handle> value
defined in the Information Domain document and the tags used in the
definition, etc. If I recall correctly the software was complaining about
like "prefix bmde:darwin: needs to be defined."
Any suggestions to get extended-schema provider resources working through a
portal for either extension technique would be greatly appreciated.