Please note: This blog is no longer updated and has moved to a new location: Scott Mark.
Thursday, April 06, 2006
Scott Mark's original blog on Application Architecture for the Enterprise - loose coupling, Agile methods, open source, Java development, thought leadership, managing people, social networking and building relationships through technology. Come visit the new blog!
About
Scott Mark
I am an Enterprise Application Architect for a Fortune 250 medical technology company. This is my personal blog of thoughts on work and life in general. This blog does not in any way represent the opinions or views of my employer or any other organization with which I am affiliated.
Contact me at scottemark at yahoo dot com
Subscribe
Recent Posts
- Yet More Architecture Podcasts
- WCM: Bone In The Throat of ECM
- More on Architecture Podcasts
- Cumulative Thoughts on the Blogosphere, Blog Tools...
- Thoughts from Dave Nicolette on Enterprise Agile
- Agility in Large Enterprises
- What's On My Reading List
- Resume Points To Consider If You Want A Job At A L...
- Architecture, Leadership, and Coaching
- More of the Same: You Still Need -ility Managemen...
Blogroll
Analysts
Architects
Development
Information Architects
Interesting
Podcasts
Security
Vendors
Powered by BloglinesMy flickr photos
www.flickr.com |
Copyright © 2005-2006 Scott Mark
This work is licensed under a Creative Commons Attribution-NonCommercial 2.5 License.
2 Comments:
Uh oh. A good idea, but this becomes problematic in a number of contexts, much like the various data and identity protection laws state are implementing to combat identity theft.
The two key problems are: ambiguity, although the proposed MN law looks to be quite specific on first reading; and what specific standard is to be adopted? And would all states utilize identical standards?
States trade data between themselves (tax, motor vehicle, etc.) and the federal government all the time? Which standard(s) would apply and what to do if State A uses a different standard than State B?
Governmental mandates like this are proposed for good reasons. However, implementing them successfully is another matter entirely. Thanks for the heads up on this.
Bob
Bob -
You're definitely right that it's easy to sit on high and propose something like this, yet another to implement it. I haven't worked in govt, but I imagine the interop issue is way more headache that in the business world due to funding, slower pace, etc. This does have a little ivory tower smell to it.
But I do like the fact that they did not mention specific formats, but rather values such as publicly available and human readable specs, royalty free implementation and extension in perpetuity, and no restrictions on creation of software to read and create the format. They have at least proposed some built-in litmus tests. And I certainly appreciate the values they are expressing in those statements.
Will be interesting to see where this goes - thanks for your thoughts!
Scott
Post a Comment
Trackbacks
<< Home