ePractice.eu provides its members with a blog in which all registered users can post opinions, questions and links to news related to eGovernment, eInclusion and eHealth. Your point of view is what makes ePractice.eu relevant to other public administrators all over Europe, so feel free to post and...
I won't unfortunately be able to join you on 17 Feb (I am with a Flemish government delegation to Silicon Valley) but would like to make a couple of observations.
Up front, I should declare that I was an editor of the "Reference Model for SOA", published as an OASIS Standard in 2006, and that I am currently President and Chairman of the Board of OASIS.
We developed the Reference Model in an attempt to dispel a lot of myths about SOA - the most common of which is that "SOA = Web Services", to the exclusion of other architectures and methodologies (such as RESTful architecture or messaging suchas ebXML). We believe very strongly that SOA is essentially a paradigm for a particular approach to architecting systems. SOA in itself does not, and should not, prescribe a particular architecture, methodology or technology stack.
The reference Model stuck a stake in the ground, laying down a clear set of concepts, definitions and seeking to explain the paradigm.
More recently, that initial work has been followed up by the "Reference Architecture Foundation for SOA" - I would urge you allto take a good look at this: you may find that much of the ground work, necessary for planning any specific implementation of SOA, and identifying the main issues, are covered in this document.
I would particularly comment the diagrams on pages 12, 19, 77-78, to grasp a "high level" view of what SOA - understood in its entirety - implies.
The strength of the work, in my opinion, is in its approach to SOA as a "service eco-system" and its emphasis not only on modelling and architecture, but equally on critical issues that many approaches to SOA either overlook or - equally dangerously - simply imply or take for granted - such as: governance, security, management, and testing.
I hope these comments help and I hope that you have a great workshop!
I am happy to follow up with anyone who requires further assistance.
ePractice.eu provides its members with a blog in which all registered users can post opinions, questions and links to news related to eGovernment, eInclusion and eHealth. Your point of view is what makes ePractice.eu relevant to other public administrators all over Europe, so feel free to post and...
I won't unfortunately be able to join you on 17 Feb (I am with a Flemish government delegation to Silicon Valley) but would like to make a couple of observations.
Up front, I should declare that I was an editor of the "Reference Model for SOA", published as an OASIS Standard in 2006, and that I am currently President and Chairman of the Board of OASIS.
We developed the Reference Model in an attempt to dispel a lot of myths about SOA - the most common of which is that "SOA = Web Services", to the exclusion of other architectures and methodologies (such as RESTful architecture or messaging suchas ebXML). We believe very strongly that SOA is essentially a paradigm for a particular approach to architecting systems. SOA in itself does not, and should not, prescribe a particular architecture, methodology or technology stack.
The reference Model stuck a stake in the ground, laying down a clear set of concepts, definitions and seeking to explain the paradigm.
More recently, that initial work has been followed up by the "Reference Architecture Foundation for SOA" - I would urge you allto take a good look at this: you may find that much of the ground work, necessary for planning any specific implementation of SOA, and identifying the main issues, are covered in this document.
I would particularly comment the diagrams on pages 12, 19, 77-78, to grasp a "high level" view of what SOA - understood in its entirety - implies.
The strength of the work, in my opinion, is in its approach to SOA as a "service eco-system" and its emphasis not only on modelling and architecture, but equally on critical issues that many approaches to SOA either overlook or - equally dangerously - simply imply or take for granted - such as: governance, security, management, and testing.
I hope these comments help and I hope that you have a great workshop!
I am happy to follow up with anyone who requires further assistance.
ePractice.eu provides its members with a blog in which all registered users can post opinions, questions and links to news related to eGovernment, eInclusion and eHealth. Your point of view is what makes ePractice.eu relevant to other public administrators all over Europe, so feel free to post and...
I won't unfortunately be able to join you on 17 Feb (I am with a Flemish government delegation to Silicon Valley) but would like to make a couple of observations.
Up front, I should declare that I was an editor of the "Reference Model for SOA", published as an OASIS Standard in 2006, and that I am currently President and Chairman of the Board of OASIS.
We developed the Reference Model in an attempt to dispel a lot of myths about SOA - the most common of which is that "SOA = Web Services", to the exclusion of other architectures and methodologies (such as RESTful architecture or messaging suchas ebXML). We believe very strongly that SOA is essentially a paradigm for a particular approach to architecting systems. SOA in itself does not, and should not, prescribe a particular architecture, methodology or technology stack.
The reference Model stuck a stake in the ground, laying down a clear set of concepts, definitions and seeking to explain the paradigm.
More recently, that initial work has been followed up by the "Reference Architecture Foundation for SOA" - I would urge you allto take a good look at this: you may find that much of the ground work, necessary for planning any specific implementation of SOA, and identifying the main issues, are covered in this document.
I would particularly comment the diagrams on pages 12, 19, 77-78, to grasp a "high level" view of what SOA - understood in its entirety - implies.
The strength of the work, in my opinion, is in its approach to SOA as a "service eco-system" and its emphasis not only on modelling and architecture, but equally on critical issues that many approaches to SOA either overlook or - equally dangerously - simply imply or take for granted - such as: governance, security, management, and testing.
I hope these comments help and I hope that you have a great workshop!
I am happy to follow up with anyone who requires further assistance.
ePractice.eu provides its members with a blog in which all registered users can post opinions, questions and links to news related to eGovernment, eInclusion and eHealth. Your point of view is what makes ePractice.eu relevant to other public administrators all over Europe, so feel free to post and...
I won't unfortunately be able to join you on 17 Feb (I am with a Flemish government delegation to Silicon Valley) but would like to make a couple of observations.
Up front, I should declare that I was an editor of the "Reference Model for SOA", published as an OASIS Standard in 2006, and that I am currently President and Chairman of the Board of OASIS.
We developed the Reference Model in an attempt to dispel a lot of myths about SOA - the most common of which is that "SOA = Web Services", to the exclusion of other architectures and methodologies (such as RESTful architecture or messaging suchas ebXML). We believe very strongly that SOA is essentially a paradigm for a particular approach to architecting systems. SOA in itself does not, and should not, prescribe a particular architecture, methodology or technology stack.
The reference Model stuck a stake in the ground, laying down a clear set of concepts, definitions and seeking to explain the paradigm.
More recently, that initial work has been followed up by the "Reference Architecture Foundation for SOA" - I would urge you allto take a good look at this: you may find that much of the ground work, necessary for planning any specific implementation of SOA, and identifying the main issues, are covered in this document.
I would particularly comment the diagrams on pages 12, 19, 77-78, to grasp a "high level" view of what SOA - understood in its entirety - implies.
The strength of the work, in my opinion, is in its approach to SOA as a "service eco-system" and its emphasis not only on modelling and architecture, but equally on critical issues that many approaches to SOA either overlook or - equally dangerously - simply imply or take for granted - such as: governance, security, management, and testing.
I hope these comments help and I hope that you have a great workshop!
I am happy to follow up with anyone who requires further assistance.
ePractice.eu provides its members with a blog in which all registered users can post opinions, questions and links to news related to eGovernment, eInclusion and eHealth. Your point of view is what makes ePractice.eu relevant to other public administrators all over Europe, so feel free to post and...
I won't unfortunately be able to join you on 17 Feb (I am with a Flemish government delegation to Silicon Valley) but would like to make a couple of observations.
Up front, I should declare that I was an editor of the "Reference Model for SOA", published as an OASIS Standard in 2006, and that I am currently President and Chairman of the Board of OASIS.
We developed the Reference Model in an attempt to dispel a lot of myths about SOA - the most common of which is that "SOA = Web Services", to the exclusion of other architectures and methodologies (such as RESTful architecture or messaging suchas ebXML). We believe very strongly that SOA is essentially a paradigm for a particular approach to architecting systems. SOA in itself does not, and should not, prescribe a particular architecture, methodology or technology stack.
The reference Model stuck a stake in the ground, laying down a clear set of concepts, definitions and seeking to explain the paradigm.
More recently, that initial work has been followed up by the "Reference Architecture Foundation for SOA" - I would urge you allto take a good look at this: you may find that much of the ground work, necessary for planning any specific implementation of SOA, and identifying the main issues, are covered in this document.
I would particularly comment the diagrams on pages 12, 19, 77-78, to grasp a "high level" view of what SOA - understood in its entirety - implies.
The strength of the work, in my opinion, is in its approach to SOA as a "service eco-system" and its emphasis not only on modelling and architecture, but equally on critical issues that many approaches to SOA either overlook or - equally dangerously - simply imply or take for granted - such as: governance, security, management, and testing.
I hope these comments help and I hope that you have a great workshop!
I am happy to follow up with anyone who requires further assistance.
ePractice.eu provides its members with a blog in which all registered users can post opinions, questions and links to news related to eGovernment, eInclusion and eHealth. Your point of view is what makes ePractice.eu relevant to other public administrators all over Europe, so feel free to post and...
I won't unfortunately be able to join you on 17 Feb (I am with a Flemish government delegation to Silicon Valley) but would like to make a couple of observations.
Up front, I should declare that I was an editor of the "Reference Model for SOA", published as an OASIS Standard in 2006, and that I am currently President and Chairman of the Board of OASIS.
We developed the Reference Model in an attempt to dispel a lot of myths about SOA - the most common of which is that "SOA = Web Services", to the exclusion of other architectures and methodologies (such as RESTful architecture or messaging suchas ebXML). We believe very strongly that SOA is essentially a paradigm for a particular approach to architecting systems. SOA in itself does not, and should not, prescribe a particular architecture, methodology or technology stack.
The reference Model stuck a stake in the ground, laying down a clear set of concepts, definitions and seeking to explain the paradigm.
More recently, that initial work has been followed up by the "Reference Architecture Foundation for SOA" - I would urge you allto take a good look at this: you may find that much of the ground work, necessary for planning any specific implementation of SOA, and identifying the main issues, are covered in this document.
I would particularly comment the diagrams on pages 12, 19, 77-78, to grasp a "high level" view of what SOA - understood in its entirety - implies.
The strength of the work, in my opinion, is in its approach to SOA as a "service eco-system" and its emphasis not only on modelling and architecture, but equally on critical issues that many approaches to SOA either overlook or - equally dangerously - simply imply or take for granted - such as: governance, security, management, and testing.
I hope these comments help and I hope that you have a great workshop!
I am happy to follow up with anyone who requires further assistance.
ePractice.eu provides its members with a blog in which all registered users can post opinions, questions and links to news related to eGovernment, eInclusion and eHealth. Your point of view is what makes ePractice.eu relevant to other public administrators all over Europe, so feel free to post and...
I won't unfortunately be able to join you on 17 Feb (I am with a Flemish government delegation to Silicon Valley) but would like to make a couple of observations.
Up front, I should declare that I was an editor of the "Reference Model for SOA", published as an OASIS Standard in 2006, and that I am currently President and Chairman of the Board of OASIS.
We developed the Reference Model in an attempt to dispel a lot of myths about SOA - the most common of which is that "SOA = Web Services", to the exclusion of other architectures and methodologies (such as RESTful architecture or messaging suchas ebXML). We believe very strongly that SOA is essentially a paradigm for a particular approach to architecting systems. SOA in itself does not, and should not, prescribe a particular architecture, methodology or technology stack.
The reference Model stuck a stake in the ground, laying down a clear set of concepts, definitions and seeking to explain the paradigm.
More recently, that initial work has been followed up by the "Reference Architecture Foundation for SOA" - I would urge you allto take a good look at this: you may find that much of the ground work, necessary for planning any specific implementation of SOA, and identifying the main issues, are covered in this document.
I would particularly comment the diagrams on pages 12, 19, 77-78, to grasp a "high level" view of what SOA - understood in its entirety - implies.
The strength of the work, in my opinion, is in its approach to SOA as a "service eco-system" and its emphasis not only on modelling and architecture, but equally on critical issues that many approaches to SOA either overlook or - equally dangerously - simply imply or take for granted - such as: governance, security, management, and testing.
I hope these comments help and I hope that you have a great workshop!
I am happy to follow up with anyone who requires further assistance.
ePractice.eu provides its members with a blog in which all registered users can post opinions, questions and links to news related to eGovernment, eInclusion and eHealth. Your point of view is what makes ePractice.eu relevant to other public administrators all over Europe, so feel free to post and...
I won't unfortunately be able to join you on 17 Feb (I am with a Flemish government delegation to Silicon Valley) but would like to make a couple of observations.
Up front, I should declare that I was an editor of the "Reference Model for SOA", published as an OASIS Standard in 2006, and that I am currently President and Chairman of the Board of OASIS.
We developed the Reference Model in an attempt to dispel a lot of myths about SOA - the most common of which is that "SOA = Web Services", to the exclusion of other architectures and methodologies (such as RESTful architecture or messaging suchas ebXML). We believe very strongly that SOA is essentially a paradigm for a particular approach to architecting systems. SOA in itself does not, and should not, prescribe a particular architecture, methodology or technology stack.
The reference Model stuck a stake in the ground, laying down a clear set of concepts, definitions and seeking to explain the paradigm.
More recently, that initial work has been followed up by the "Reference Architecture Foundation for SOA" - I would urge you allto take a good look at this: you may find that much of the ground work, necessary for planning any specific implementation of SOA, and identifying the main issues, are covered in this document.
I would particularly comment the diagrams on pages 12, 19, 77-78, to grasp a "high level" view of what SOA - understood in its entirety - implies.
The strength of the work, in my opinion, is in its approach to SOA as a "service eco-system" and its emphasis not only on modelling and architecture, but equally on critical issues that many approaches to SOA either overlook or - equally dangerously - simply imply or take for granted - such as: governance, security, management, and testing.
I hope these comments help and I hope that you have a great workshop!
I am happy to follow up with anyone who requires further assistance.
ePractice.eu provides its members with a blog in which all registered users can post opinions, questions and links to news related to eGovernment, eInclusion and eHealth. Your point of view is what makes ePractice.eu relevant to other public administrators all over Europe, so feel free to post and...
I won't unfortunately be able to join you on 17 Feb (I am with a Flemish government delegation to Silicon Valley) but would like to make a couple of observations.
Up front, I should declare that I was an editor of the "Reference Model for SOA", published as an OASIS Standard in 2006, and that I am currently President and Chairman of the Board of OASIS.
We developed the Reference Model in an attempt to dispel a lot of myths about SOA - the most common of which is that "SOA = Web Services", to the exclusion of other architectures and methodologies (such as RESTful architecture or messaging suchas ebXML). We believe very strongly that SOA is essentially a paradigm for a particular approach to architecting systems. SOA in itself does not, and should not, prescribe a particular architecture, methodology or technology stack.
The reference Model stuck a stake in the ground, laying down a clear set of concepts, definitions and seeking to explain the paradigm.
More recently, that initial work has been followed up by the "Reference Architecture Foundation for SOA" - I would urge you allto take a good look at this: you may find that much of the ground work, necessary for planning any specific implementation of SOA, and identifying the main issues, are covered in this document.
I would particularly comment the diagrams on pages 12, 19, 77-78, to grasp a "high level" view of what SOA - understood in its entirety - implies.
The strength of the work, in my opinion, is in its approach to SOA as a "service eco-system" and its emphasis not only on modelling and architecture, but equally on critical issues that many approaches to SOA either overlook or - equally dangerously - simply imply or take for granted - such as: governance, security, management, and testing.
I hope these comments help and I hope that you have a great workshop!
I am happy to follow up with anyone who requires further assistance.
ePractice.eu provides its members with a blog in which all registered users can post opinions, questions and links to news related to eGovernment, eInclusion and eHealth. Your point of view is what makes ePractice.eu relevant to other public administrators all over Europe, so feel free to post and...
I won't unfortunately be able to join you on 17 Feb (I am with a Flemish government delegation to Silicon Valley) but would like to make a couple of observations.
Up front, I should declare that I was an editor of the "Reference Model for SOA", published as an OASIS Standard in 2006, and that I am currently President and Chairman of the Board of OASIS.
We developed the Reference Model in an attempt to dispel a lot of myths about SOA - the most common of which is that "SOA = Web Services", to the exclusion of other architectures and methodologies (such as RESTful architecture or messaging suchas ebXML). We believe very strongly that SOA is essentially a paradigm for a particular approach to architecting systems. SOA in itself does not, and should not, prescribe a particular architecture, methodology or technology stack.
The reference Model stuck a stake in the ground, laying down a clear set of concepts, definitions and seeking to explain the paradigm.
More recently, that initial work has been followed up by the "Reference Architecture Foundation for SOA" - I would urge you allto take a good look at this: you may find that much of the ground work, necessary for planning any specific implementation of SOA, and identifying the main issues, are covered in this document.
I would particularly comment the diagrams on pages 12, 19, 77-78, to grasp a "high level" view of what SOA - understood in its entirety - implies.
The strength of the work, in my opinion, is in its approach to SOA as a "service eco-system" and its emphasis not only on modelling and architecture, but equally on critical issues that many approaches to SOA either overlook or - equally dangerously - simply imply or take for granted - such as: governance, security, management, and testing.
I hope these comments help and I hope that you have a great workshop!
I am happy to follow up with anyone who requires further assistance.
The ePractice blog: discuss, praise, disagree.
ePractice.eu provides its members with a blog in which all registered users can post opinions, questions and links to news related to eGovernment, eInclusion and eHealth. Your point of view is what makes ePractice.eu relevant to other public administrators all over Europe, so feel free to post and...
Build on existing standards and frameworks
I won't unfortunately be able to join you on 17 Feb (I am with a Flemish government delegation to Silicon Valley) but would like to make a couple of observations.
Up front, I should declare that I was an editor of the "Reference Model for SOA", published as an OASIS Standard in 2006, and that I am currently President and Chairman of the Board of OASIS.
We developed the Reference Model in an attempt to dispel a lot of myths about SOA - the most common of which is that "SOA = Web Services", to the exclusion of other architectures and methodologies (such as RESTful architecture or messaging suchas ebXML). We believe very strongly that SOA is essentially a paradigm for a particular approach to architecting systems. SOA in itself does not, and should not, prescribe a particular architecture, methodology or technology stack.
The reference Model stuck a stake in the ground, laying down a clear set of concepts, definitions and seeking to explain the paradigm.
More recently, that initial work has been followed up by the "Reference Architecture Foundation for SOA" - I would urge you allto take a good look at this: you may find that much of the ground work, necessary for planning any specific implementation of SOA, and identifying the main issues, are covered in this document.
I would particularly comment the diagrams on pages 12, 19, 77-78, to grasp a "high level" view of what SOA - understood in its entirety - implies.
The strength of the work, in my opinion, is in its approach to SOA as a "service eco-system" and its emphasis not only on modelling and architecture, but equally on critical issues that many approaches to SOA either overlook or - equally dangerously - simply imply or take for granted - such as: governance, security, management, and testing.
I hope these comments help and I hope that you have a great workshop!
I am happy to follow up with anyone who requires further assistance.
The ePractice blog: discuss, praise, disagree.
ePractice.eu provides its members with a blog in which all registered users can post opinions, questions and links to news related to eGovernment, eInclusion and eHealth. Your point of view is what makes ePractice.eu relevant to other public administrators all over Europe, so feel free to post and...
Build on existing standards and frameworks
I won't unfortunately be able to join you on 17 Feb (I am with a Flemish government delegation to Silicon Valley) but would like to make a couple of observations.
Up front, I should declare that I was an editor of the "Reference Model for SOA", published as an OASIS Standard in 2006, and that I am currently President and Chairman of the Board of OASIS.
We developed the Reference Model in an attempt to dispel a lot of myths about SOA - the most common of which is that "SOA = Web Services", to the exclusion of other architectures and methodologies (such as RESTful architecture or messaging suchas ebXML). We believe very strongly that SOA is essentially a paradigm for a particular approach to architecting systems. SOA in itself does not, and should not, prescribe a particular architecture, methodology or technology stack.
The reference Model stuck a stake in the ground, laying down a clear set of concepts, definitions and seeking to explain the paradigm.
More recently, that initial work has been followed up by the "Reference Architecture Foundation for SOA" - I would urge you allto take a good look at this: you may find that much of the ground work, necessary for planning any specific implementation of SOA, and identifying the main issues, are covered in this document.
I would particularly comment the diagrams on pages 12, 19, 77-78, to grasp a "high level" view of what SOA - understood in its entirety - implies.
The strength of the work, in my opinion, is in its approach to SOA as a "service eco-system" and its emphasis not only on modelling and architecture, but equally on critical issues that many approaches to SOA either overlook or - equally dangerously - simply imply or take for granted - such as: governance, security, management, and testing.
I hope these comments help and I hope that you have a great workshop!
I am happy to follow up with anyone who requires further assistance.
The ePractice blog: discuss, praise, disagree.
ePractice.eu provides its members with a blog in which all registered users can post opinions, questions and links to news related to eGovernment, eInclusion and eHealth. Your point of view is what makes ePractice.eu relevant to other public administrators all over Europe, so feel free to post and...
Build on existing standards and frameworks
I won't unfortunately be able to join you on 17 Feb (I am with a Flemish government delegation to Silicon Valley) but would like to make a couple of observations.
Up front, I should declare that I was an editor of the "Reference Model for SOA", published as an OASIS Standard in 2006, and that I am currently President and Chairman of the Board of OASIS.
We developed the Reference Model in an attempt to dispel a lot of myths about SOA - the most common of which is that "SOA = Web Services", to the exclusion of other architectures and methodologies (such as RESTful architecture or messaging suchas ebXML). We believe very strongly that SOA is essentially a paradigm for a particular approach to architecting systems. SOA in itself does not, and should not, prescribe a particular architecture, methodology or technology stack.
The reference Model stuck a stake in the ground, laying down a clear set of concepts, definitions and seeking to explain the paradigm.
More recently, that initial work has been followed up by the "Reference Architecture Foundation for SOA" - I would urge you allto take a good look at this: you may find that much of the ground work, necessary for planning any specific implementation of SOA, and identifying the main issues, are covered in this document.
I would particularly comment the diagrams on pages 12, 19, 77-78, to grasp a "high level" view of what SOA - understood in its entirety - implies.
The strength of the work, in my opinion, is in its approach to SOA as a "service eco-system" and its emphasis not only on modelling and architecture, but equally on critical issues that many approaches to SOA either overlook or - equally dangerously - simply imply or take for granted - such as: governance, security, management, and testing.
I hope these comments help and I hope that you have a great workshop!
I am happy to follow up with anyone who requires further assistance.
The ePractice blog: discuss, praise, disagree.
ePractice.eu provides its members with a blog in which all registered users can post opinions, questions and links to news related to eGovernment, eInclusion and eHealth. Your point of view is what makes ePractice.eu relevant to other public administrators all over Europe, so feel free to post and...
Build on existing standards and frameworks
I won't unfortunately be able to join you on 17 Feb (I am with a Flemish government delegation to Silicon Valley) but would like to make a couple of observations.
Up front, I should declare that I was an editor of the "Reference Model for SOA", published as an OASIS Standard in 2006, and that I am currently President and Chairman of the Board of OASIS.
We developed the Reference Model in an attempt to dispel a lot of myths about SOA - the most common of which is that "SOA = Web Services", to the exclusion of other architectures and methodologies (such as RESTful architecture or messaging suchas ebXML). We believe very strongly that SOA is essentially a paradigm for a particular approach to architecting systems. SOA in itself does not, and should not, prescribe a particular architecture, methodology or technology stack.
The reference Model stuck a stake in the ground, laying down a clear set of concepts, definitions and seeking to explain the paradigm.
More recently, that initial work has been followed up by the "Reference Architecture Foundation for SOA" - I would urge you allto take a good look at this: you may find that much of the ground work, necessary for planning any specific implementation of SOA, and identifying the main issues, are covered in this document.
I would particularly comment the diagrams on pages 12, 19, 77-78, to grasp a "high level" view of what SOA - understood in its entirety - implies.
The strength of the work, in my opinion, is in its approach to SOA as a "service eco-system" and its emphasis not only on modelling and architecture, but equally on critical issues that many approaches to SOA either overlook or - equally dangerously - simply imply or take for granted - such as: governance, security, management, and testing.
I hope these comments help and I hope that you have a great workshop!
I am happy to follow up with anyone who requires further assistance.
The ePractice blog: discuss, praise, disagree.
ePractice.eu provides its members with a blog in which all registered users can post opinions, questions and links to news related to eGovernment, eInclusion and eHealth. Your point of view is what makes ePractice.eu relevant to other public administrators all over Europe, so feel free to post and...
Build on existing standards and frameworks
I won't unfortunately be able to join you on 17 Feb (I am with a Flemish government delegation to Silicon Valley) but would like to make a couple of observations.
Up front, I should declare that I was an editor of the "Reference Model for SOA", published as an OASIS Standard in 2006, and that I am currently President and Chairman of the Board of OASIS.
We developed the Reference Model in an attempt to dispel a lot of myths about SOA - the most common of which is that "SOA = Web Services", to the exclusion of other architectures and methodologies (such as RESTful architecture or messaging suchas ebXML). We believe very strongly that SOA is essentially a paradigm for a particular approach to architecting systems. SOA in itself does not, and should not, prescribe a particular architecture, methodology or technology stack.
The reference Model stuck a stake in the ground, laying down a clear set of concepts, definitions and seeking to explain the paradigm.
More recently, that initial work has been followed up by the "Reference Architecture Foundation for SOA" - I would urge you allto take a good look at this: you may find that much of the ground work, necessary for planning any specific implementation of SOA, and identifying the main issues, are covered in this document.
I would particularly comment the diagrams on pages 12, 19, 77-78, to grasp a "high level" view of what SOA - understood in its entirety - implies.
The strength of the work, in my opinion, is in its approach to SOA as a "service eco-system" and its emphasis not only on modelling and architecture, but equally on critical issues that many approaches to SOA either overlook or - equally dangerously - simply imply or take for granted - such as: governance, security, management, and testing.
I hope these comments help and I hope that you have a great workshop!
I am happy to follow up with anyone who requires further assistance.
The ePractice blog: discuss, praise, disagree.
ePractice.eu provides its members with a blog in which all registered users can post opinions, questions and links to news related to eGovernment, eInclusion and eHealth. Your point of view is what makes ePractice.eu relevant to other public administrators all over Europe, so feel free to post and...
Build on existing standards and frameworks
I won't unfortunately be able to join you on 17 Feb (I am with a Flemish government delegation to Silicon Valley) but would like to make a couple of observations.
Up front, I should declare that I was an editor of the "Reference Model for SOA", published as an OASIS Standard in 2006, and that I am currently President and Chairman of the Board of OASIS.
We developed the Reference Model in an attempt to dispel a lot of myths about SOA - the most common of which is that "SOA = Web Services", to the exclusion of other architectures and methodologies (such as RESTful architecture or messaging suchas ebXML). We believe very strongly that SOA is essentially a paradigm for a particular approach to architecting systems. SOA in itself does not, and should not, prescribe a particular architecture, methodology or technology stack.
The reference Model stuck a stake in the ground, laying down a clear set of concepts, definitions and seeking to explain the paradigm.
More recently, that initial work has been followed up by the "Reference Architecture Foundation for SOA" - I would urge you allto take a good look at this: you may find that much of the ground work, necessary for planning any specific implementation of SOA, and identifying the main issues, are covered in this document.
I would particularly comment the diagrams on pages 12, 19, 77-78, to grasp a "high level" view of what SOA - understood in its entirety - implies.
The strength of the work, in my opinion, is in its approach to SOA as a "service eco-system" and its emphasis not only on modelling and architecture, but equally on critical issues that many approaches to SOA either overlook or - equally dangerously - simply imply or take for granted - such as: governance, security, management, and testing.
I hope these comments help and I hope that you have a great workshop!
I am happy to follow up with anyone who requires further assistance.
The ePractice blog: discuss, praise, disagree.
ePractice.eu provides its members with a blog in which all registered users can post opinions, questions and links to news related to eGovernment, eInclusion and eHealth. Your point of view is what makes ePractice.eu relevant to other public administrators all over Europe, so feel free to post and...
Build on existing standards and frameworks
I won't unfortunately be able to join you on 17 Feb (I am with a Flemish government delegation to Silicon Valley) but would like to make a couple of observations.
Up front, I should declare that I was an editor of the "Reference Model for SOA", published as an OASIS Standard in 2006, and that I am currently President and Chairman of the Board of OASIS.
We developed the Reference Model in an attempt to dispel a lot of myths about SOA - the most common of which is that "SOA = Web Services", to the exclusion of other architectures and methodologies (such as RESTful architecture or messaging suchas ebXML). We believe very strongly that SOA is essentially a paradigm for a particular approach to architecting systems. SOA in itself does not, and should not, prescribe a particular architecture, methodology or technology stack.
The reference Model stuck a stake in the ground, laying down a clear set of concepts, definitions and seeking to explain the paradigm.
More recently, that initial work has been followed up by the "Reference Architecture Foundation for SOA" - I would urge you allto take a good look at this: you may find that much of the ground work, necessary for planning any specific implementation of SOA, and identifying the main issues, are covered in this document.
I would particularly comment the diagrams on pages 12, 19, 77-78, to grasp a "high level" view of what SOA - understood in its entirety - implies.
The strength of the work, in my opinion, is in its approach to SOA as a "service eco-system" and its emphasis not only on modelling and architecture, but equally on critical issues that many approaches to SOA either overlook or - equally dangerously - simply imply or take for granted - such as: governance, security, management, and testing.
I hope these comments help and I hope that you have a great workshop!
I am happy to follow up with anyone who requires further assistance.
The ePractice blog: discuss, praise, disagree.
ePractice.eu provides its members with a blog in which all registered users can post opinions, questions and links to news related to eGovernment, eInclusion and eHealth. Your point of view is what makes ePractice.eu relevant to other public administrators all over Europe, so feel free to post and...
Build on existing standards and frameworks
I won't unfortunately be able to join you on 17 Feb (I am with a Flemish government delegation to Silicon Valley) but would like to make a couple of observations.
Up front, I should declare that I was an editor of the "Reference Model for SOA", published as an OASIS Standard in 2006, and that I am currently President and Chairman of the Board of OASIS.
We developed the Reference Model in an attempt to dispel a lot of myths about SOA - the most common of which is that "SOA = Web Services", to the exclusion of other architectures and methodologies (such as RESTful architecture or messaging suchas ebXML). We believe very strongly that SOA is essentially a paradigm for a particular approach to architecting systems. SOA in itself does not, and should not, prescribe a particular architecture, methodology or technology stack.
The reference Model stuck a stake in the ground, laying down a clear set of concepts, definitions and seeking to explain the paradigm.
More recently, that initial work has been followed up by the "Reference Architecture Foundation for SOA" - I would urge you allto take a good look at this: you may find that much of the ground work, necessary for planning any specific implementation of SOA, and identifying the main issues, are covered in this document.
I would particularly comment the diagrams on pages 12, 19, 77-78, to grasp a "high level" view of what SOA - understood in its entirety - implies.
The strength of the work, in my opinion, is in its approach to SOA as a "service eco-system" and its emphasis not only on modelling and architecture, but equally on critical issues that many approaches to SOA either overlook or - equally dangerously - simply imply or take for granted - such as: governance, security, management, and testing.
I hope these comments help and I hope that you have a great workshop!
I am happy to follow up with anyone who requires further assistance.
The ePractice blog: discuss, praise, disagree.
ePractice.eu provides its members with a blog in which all registered users can post opinions, questions and links to news related to eGovernment, eInclusion and eHealth. Your point of view is what makes ePractice.eu relevant to other public administrators all over Europe, so feel free to post and...
Build on existing standards and frameworks
I won't unfortunately be able to join you on 17 Feb (I am with a Flemish government delegation to Silicon Valley) but would like to make a couple of observations.
Up front, I should declare that I was an editor of the "Reference Model for SOA", published as an OASIS Standard in 2006, and that I am currently President and Chairman of the Board of OASIS.
We developed the Reference Model in an attempt to dispel a lot of myths about SOA - the most common of which is that "SOA = Web Services", to the exclusion of other architectures and methodologies (such as RESTful architecture or messaging suchas ebXML). We believe very strongly that SOA is essentially a paradigm for a particular approach to architecting systems. SOA in itself does not, and should not, prescribe a particular architecture, methodology or technology stack.
The reference Model stuck a stake in the ground, laying down a clear set of concepts, definitions and seeking to explain the paradigm.
More recently, that initial work has been followed up by the "Reference Architecture Foundation for SOA" - I would urge you allto take a good look at this: you may find that much of the ground work, necessary for planning any specific implementation of SOA, and identifying the main issues, are covered in this document.
I would particularly comment the diagrams on pages 12, 19, 77-78, to grasp a "high level" view of what SOA - understood in its entirety - implies.
The strength of the work, in my opinion, is in its approach to SOA as a "service eco-system" and its emphasis not only on modelling and architecture, but equally on critical issues that many approaches to SOA either overlook or - equally dangerously - simply imply or take for granted - such as: governance, security, management, and testing.
I hope these comments help and I hope that you have a great workshop!
I am happy to follow up with anyone who requires further assistance.
The ePractice blog: discuss, praise, disagree.
ePractice.eu provides its members with a blog in which all registered users can post opinions, questions and links to news related to eGovernment, eInclusion and eHealth. Your point of view is what makes ePractice.eu relevant to other public administrators all over Europe, so feel free to post and...
Build on existing standards and frameworks
I won't unfortunately be able to join you on 17 Feb (I am with a Flemish government delegation to Silicon Valley) but would like to make a couple of observations.
Up front, I should declare that I was an editor of the "Reference Model for SOA", published as an OASIS Standard in 2006, and that I am currently President and Chairman of the Board of OASIS.
We developed the Reference Model in an attempt to dispel a lot of myths about SOA - the most common of which is that "SOA = Web Services", to the exclusion of other architectures and methodologies (such as RESTful architecture or messaging suchas ebXML). We believe very strongly that SOA is essentially a paradigm for a particular approach to architecting systems. SOA in itself does not, and should not, prescribe a particular architecture, methodology or technology stack.
The reference Model stuck a stake in the ground, laying down a clear set of concepts, definitions and seeking to explain the paradigm.
More recently, that initial work has been followed up by the "Reference Architecture Foundation for SOA" - I would urge you allto take a good look at this: you may find that much of the ground work, necessary for planning any specific implementation of SOA, and identifying the main issues, are covered in this document.
I would particularly comment the diagrams on pages 12, 19, 77-78, to grasp a "high level" view of what SOA - understood in its entirety - implies.
The strength of the work, in my opinion, is in its approach to SOA as a "service eco-system" and its emphasis not only on modelling and architecture, but equally on critical issues that many approaches to SOA either overlook or - equally dangerously - simply imply or take for granted - such as: governance, security, management, and testing.
I hope these comments help and I hope that you have a great workshop!
I am happy to follow up with anyone who requires further assistance.