head 1.4; access; symbols; locks; strict; comment @# @; 1.4 date 2009.11.25.03.14.31; author GarryJolleyRogers; state Exp; branches; next 1.3; 1.3 date 2009.11.20.02.45.22; author LeeBelbin; state Exp; branches; next 1.2; 1.2 date 2007.03.06.17.30.00; author TWikiGuest; state Exp; branches; next 1.1; 1.1 date 2004.12.31.15.07.29; author ShirleyCohen; state Exp; branches; next ; desc @none @ 1.4 log @none @ text @%META:TOPICINFO{author="GarryJolleyRogers" date="1259118871" format="1.1" version="1.4"}% %META:TOPICPARENT{name="ImplementationsOfBDI.SDD"}% ---+!! %TOPIC% I've been thinking about how SDD will be used in the context of CIPRes. I pressume users will be depositing matrices with up to hundreds of characters and taxa per matrix and sometimes multiple matrices per study. Under these circumstances, there would be a lot of bytes to transfer over the wire and we have to be careful not to send exceeding large SOAP messages. With this in mind, I propose that we decouple the terminology and externalDataInterface sections from the core description section of SDD to make it possible for users to submit multiple matrices belonging to a single study without having to repeat the same vocabulary and media resources assuming those are common between the matrices. This would mean that the first matrix would contain the entire vocabulation section, but subsequent matrices would simply refer to the shared voculabulary using some form of identification scheme that we would agree upon. The identification would refer to the entire vocabulary block defined in the first matrix rather a single taxon. Same goes for the media resource stuff. What do you think of the idea of decoupling these sections in an SDD document and if so how would you recommend that we go about implementing these changes? Thanks, Shirley -- Main.ShirleyCohen - 31 Dec 2004@ 1.3 log @none @ text @d1 1 a1 1 %META:TOPICINFO{author="LeeBelbin" date="1258685122" format="1.1" reprev="1.3" version="1.3"}% d5 1 a5 1 I've been thinking about how BDI.SDD will be used in the context of CIPRes. I pressume users will be depositing matrices with up to hundreds of characters and taxa per matrix and sometimes multiple matrices per study. Under these circumstances, there would be a lot of bytes to transfer over the wire and we have to be careful not to send exceeding large SOAP messages. With this in mind, I propose that we decouple the terminology and externalDataInterface sections from the core description section of BDI.SDD to make it possible for users to submit multiple matrices belonging to a single study without having to repeat the same vocabulary and media resources assuming those are common between the matrices. This would mean that the first matrix would contain the entire vocabulation section, but subsequent matrices would simply refer to the shared voculabulary using some form of identification scheme that we would agree upon. The identification would refer to the entire vocabulary block defined in the first matrix rather a single taxon. Same goes for the media resource stuff. d7 1 a7 1 What do you think of the idea of decoupling these sections in an BDI.SDD document and if so how would you recommend that we go about implementing these changes? d15 1 a15 1 -- Main.ShirleyCohen - 31 Dec 2004 @ 1.2 log @Added topic name via script @ text @d1 2 d5 1 a5 3 %META:TOPICINFO{author="ShirleyCohen" date="1104505649" format="1.0" version="1.1"}% %META:TOPICPARENT{name="ImplementationsOfSDD"}% I've been thinking about how SDD will be used in the context of CIPRes. I pressume users will be depositing matrices with up to hundreds of characters and taxa per matrix and sometimes multiple matrices per study. Under these circumstances, there would be a lot of bytes to transfer over the wire and we have to be careful not to send exceeding large SOAP messages. With this in mind, I propose that we decouple the terminology and externalDataInterface sections from the core description section of SDD to make it possible for users to submit multiple matrices belonging to a single study without having to repeat the same vocabulary and media resources assuming those are common between the matrices. This would mean that the first matrix would contain the entire vocabulation section, but subsequent matrices would simply refer to the shared voculabulary using some form of identification scheme that we would agree upon. The identification would refer to the entire vocabulary block defined in the first matrix rather a single taxon. Same goes for the media resource stuff. d7 1 a7 1 What do you think of the idea of decoupling these sections in an SDD document and if so how would you recommend that we go about implementing these changes? a15 1 @ 1.1 log @none @ text @d1 2 @