[Home] [By Thread] [By Date] [Recent Entries]
On Wed, Aug 12, 2009 at 4:20 AM, Michael Kay <mike@s...> wrote:
Michael, Whilst I agree with your assertion above I still don't think this necessitates namespaced data content. I if have understood your eample you could either have: <hr:employees xmlns:hr="http://mycompany.com/human-resources/scheme-a"> Â Â Â Â <hr:employee type="hourly">fred</hr:employee> Â Â Â Â <hr:employee type="contractor">joe</hr:employee> Â Â Â Â <hr:employee type="salaried">jane</hr:employee> </hr:employees> Or <hr:employees xmlns:hr="http://mycompany.com/human-resources/scheme-b"> Â Â Â Â <hr:hourly>fred</hr:hourly> Â Â Â Â <hr:contractor>joe</hr:contractor> Â Â Â Â <hr:salaried>jane</hr:salaried> </hr:employees> Clearly mapping between these two simple representations is trivial. I think this is preferable to: <hr:employees xmlns:hr="http://mycompany.com/human-resources/scheme-c" Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â xmlns:cont="http://mycompany.com/human-resources/contractor" Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â xmlns:hour="http://mycompany.com/human-resources/hourly" Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â xmlns:sal="http://mycompany.com/human-resources/salaried"> Â Â Â Â <hr:employee>hour:fred</hr:employee> Â Â Â Â <hr:employee>cont:joe</hr:employee> Â Â Â Â <hr:employee>sal:jane</hr:employee> </hr:employees> Which is I think what is being suggested on this thread. Regards, Michael Odling-Smee
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] |

Cart



