[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: Re: FW: [emergency-adopt-docs] EDXL Product Directory Data Fields
Thanks Patrick, I just forwarded the message. I uploaded the draft minutes earlier. Cheers, Rex Patrick Gannon wrote: > Rex, > > Please forward the email below to Carol, with attachment, which was approved by the C&D SC on 23 Feb to be added to the EM Product Director Requirements. The C&D SC also requested that the assigned OASIS IT person join the next SC call at 10am ET on 9 Mar to discuss these requirements with the SC including the questions posed in my email of 18 Jan. > > Patrick > > -----Original Message----- > From: Patrick Gannon [mailto:pgannon@warningsystems.com] > Sent: Monday, January 18, 2010 1:03 PM > To: emergency-adopt-docs@lists.oasis-open.org > Subject: [emergency-adopt-docs] EDXL Product Directory Data Fields > > Rex, > > After struggling to answer the questions today about what the search should look like, I stepped back to consider what data a vendor would have available to enter into the product directory. Attached is DRAFT of some thoughts on those data fields. Doing this helped me to see that we need to engage with the OASIS IT staff person on questions about whether the available Drupal software models can support relational data fields with one-to-many relationships. This will determine whether a vendor needs to make one entry for each of their products and then be able to select multiple specs/version from a drop-down list, or whether they are limited to selecting only one spec-version per product entry. See example I included in the attached spreadsheet. > > Are there other data fields needed? > > Patrick Gannon > -- Rex Brooks President, CEO Starbourne Communications Design GeoAddress: 1361-A Addison Berkeley, CA 94702 Tel: 510-898-0670
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]