If I was designing it, I would use yyyy/mm/dd instead. Sébastien
On 1/11/08, Ron Young <[EMAIL PROTECTED]> wrote: > > Hi all, > > Using WCF to define service/data contracts: > > [ServiceContract(Namespace = " > http://company.com/contracts/services/enrollment-core/01/11/2008";)] > interface IEnrollmentCore > { > [OperationContract] > GetSomeDataResponse GetSomeData(GetSomeDataRequest request); > } > > [DataContract(Namespace = " > http://company.com/contracts/data/enrollment-core/01/11/2008";)] > class GetSomeDataResponse > { > [DataMember] > public SomeData[] SomeData; > } > > [DataContract(Namespace = " > http://company.com/contracts/data/enrollment-core/01/11/2008";)] > class GetSomeDataRequest > { > [DataMember] > public string SomeDataCategory; > } > > > Any objections to that namespace convention? I know the issues with > versioning and don't see versioning as a priority requirement right now. I'm > just trying to establish some best practices and reasons why when using XML > namespaces within my organization. > > =================================== > This list is hosted by DevelopMentor(R) http://www.develop.com > > View archives and manage your subscription(s) at > http://discuss.develop.com > -- Sébastien www.sebastienlorion.com =================================== This list is hosted by DevelopMentor® http://www.develop.com View archives and manage your subscription(s) at http://discuss.develop.com
