Comments:

Flat Nested Threaded Embedded

Oldest First Newest First

Author	Thread:
Bob DeHoff	More Extensive Attribute Data Form Model Posted: Wednesday, March 16, 2005 8:23 PM (EST) Jeff, thank you for your feedback. The next revision of the UML models will include a textual description for each attribute in each class. Is this what you were referring to by "much more attribute data is needed" or is there additional information that should be shown? The values for the code lists and enumerations such as ContractEventType are shown in the Stereotypes UML class diagram for each schema. In UML, the way the code list or enumeration that applies to an attribute is indicated is by using the code list or enumeration stereotype class name as the data type for the attribute. So for example, the event attribute of the ContractEvent class has a data type of ContractEventType, indicating that the ContractEventType enumeration stereotype class applies to that attribute. For more information on the UML modeling conventions that the TransXML team is using, please see the "Understanding UML Class Diagrams" presentation posted in the TransXML Project Documents area. The textual descriptions for the ContractMilestone class and other classes are shown in the document. Is there additional information at the class level that should be shown? The approach we are taking to developing the schema is to develop the UML models first and get consensus from the community on those, then develop the XML schema (XSD) for the model and get consensus from the community on those. So at this stage the XML Schema Definition Language (XSD) files have not been developed for these schemas. What additional aspects of the UML model are needed to enable you to confirm the attributes associated with the various classes? The scope of the BidPackage schema is publication of the bid package by the agency to the public. Specifically excluded from the scope is XML schema for document artifacts such as plans, special provisions, and other specifications. Based on that scope, what spacial referencing information about where the work is to be performed should be included in the bid package XML documents that are published by the agency? What additional information about prequalification should be published in the bid package XML documents?
Jeff Thorn	More Extensive Attribute Data Form Model Posted: Monday, April 04, 2005 10:08 AM (EST) I did not notice a “work type”  such as “highway design or other design” in the pdf document titled “XML Schemas for Exchange of Transportation Data“. Are design services  within the scope of bid system development and if so are design services already addressed ?  It would probably be good to include reference to bidding services such as communications, utility, traffic data, weather, etc. I did not notice reference to bidding those services in the documentation noted above.
Bob DeHoff	More Extensive Attribute Data Form Model Posted: Monday, April 04, 2005 11:40 AM (EST) The first draft of the Proposal class has two work type classification attributes: constructionType and workPrequalificationClass.  Both attributes have code list data types that provide for expansion of the codes that are available.  These attributes could be used to indicate at a high level that the Proposal scope includes specific service types. Bidding of services is not explicitly modeled in the current model.  To represent services to be bid in the current model, an agency would define a ReferencePayItem for each service and have a ContractPayItem for each service to be bid on the proposal.  Jeff - How does your agency handle bidding of services now?  Do you use a pay item for each service to be bid or do you handle it separately from pay items?  Other schema reviewers and participants - What has your experience been with how bidding of services is handled?