To make the attachments more direct I am resending the attachments
directly with this message.
I am forwarding this message to the whole list after seeing a message
from DW looking for browse and drill down query examples. This message
has all the 6 messages (3 request / 3 responses) for the same
classification tree that we have in the demo scenario. DW please let me
know if you have any questions regarding browse and drill down queries.
These are the only RR interactions we have for POC, and I will be glad
to help ensure that your implementation questions are answered.
In summary there should be no doubt that browse and drill down queries
are supported adequately by the RR specs. There is at least one
implementation that showed this in a Registry Browser demo at the POC
f2f. RR implementors please focus on this functionality since that is
what we will show in the demo scenario.
Finally, I will be leaving for Tokyo this Saturday. I will not check
email between Friday nite and Monday afternoon. Please get your RR
issues to me by COB Friday if possible and I will do what I can to help.
------------Text of msg to Mark Hale ---------------
The following are noteworthy of your attention
and would require you or Krishna to send out a policy statement on these
conventions. Note these cause major problems at SJ due to lack of
agreement.
TPAID
-------
Note that in SJ we used a TPAID with "/" characters which caused
problems to several people. I am proposing that '_' be used as
separators:
<TPAId context="tpadb">
SunRegistryClient_SunRegistryService_ebXML_Registry_1.0
</TPAId>
Note in my own implemetation I add a suffix of .tpa.xml to the file.
This is not publicaly visible. I have attached my sample RR client to
service tpa file as well which was used to generate this output.
Let us know if this is acceptable.
DUNS ID
----------
In SJ demo we used 9 digit numbers which made it really hard to remember
who was who. I suggest we use names like SunRegistryClient and
SunRegistryService. Note that RoleName should match Partyname attribute
in PartyName and OrgName elements according to bottom of pp 10 of
tpaspec.pdf for 1.0.6.
Let us know if this is acceptable.
DocType
----------
I recommend we use the single DTD file RegRep0.8.dtd for RR to reduce
chances of errors. I have attached the file in case you have lost it. So
the RR payloads have a doctype as foollows:
<!DOCTYPE ebXMLRegistry SYSTEM "RegRep0.8.dtd" >
Let us know if this is acceptable.
--
Regards,
Farrukh
--
Regards,
Farrukh