Hi folks,
This is probably the sort of discussion that needs to be on the whole list.
cheers,
Ray
I believe we agreed in Moscow on the first day to have the Resource element to "not" have a namespace for the Query Interface. I am realizing now I am having a difficult time making this happen. Any help you can give would be great.
Though I am now wondering something else in our OAI currently we come back with nonamespace Resources can these individual Resources be validated? Because I would like to validate individual Resources and chunk them away if they don't validate. I thought this was working, but I believe because of our nonamespace they are just passing through. I will see if I can verify that.
Another option might be is we simply make a separate schema (or a global element in the VOResource-1.0.xsd) that is simply an element of type vr:Resource where by the Query Interface can reference it and the OAI can use it as well. This would of course mean that our Resource elements would have some kind of namespace both for Query and OAI interfaces.
Or if you say the OAI individual Resource elements (with nonamespace) can be validated with not much problem and you know of a way to represent a nonamespace Resource element in the wsdl like we said we would do in Moscow. Then I am quite happy for that.
Many Thanks for any help and answers.
cheers,
Kevin
Received on 2006-09-27Z18:27:03