Date: Fri, 29 Mar 2024 02:34:17 +0000 (UTC) Message-ID: <1370205073.7419.1711679657855@ip-10-10-7-29.ec2.internal> Subject: Exported From Confluence MIME-Version: 1.0 Content-Type: multipart/related; boundary="----=_Part_7418_2081852545.1711679657854" ------=_Part_7418_2081852545.1711679657854 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Content-Location: file:///C:/exported.html
Goal: Clarify our own thinking about what SOA is and is not.&nbs= p; One component would be a "literature survey/annotated bibliography."
One problem is that there are so many incommensurable definitions of SOA= that to have a meaningful conversation, one has to define one's terms.
Paul Hill started us off with a good thought provoking piece, "Challenges to adopting SOA within Higher-Ed (and elsewhere).= "
Concrete group question: Does the following article represent an SOA fra= mework in application? "The RepoMMan Project: Automating workf= low and metadata for an institutional repository."