Changes between Version 14 and Version 15 of IdsAdiInfrastructureStatus
- Timestamp:
- 10/31/08 04:14:25 (15 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
IdsAdiInfrastructureStatus
v14 v15 1 1 [[TracNav(TracNav/IdsAdi)]] [[Image(wiki:IdsAdiBranding:Logo-128x128.gif)]] 2 2 3 = POSC -Caesar FIATECH IDS-ADI Projects =3 = POSC Caesar FIATECH IDS-ADI Projects = 4 4 == Intelligent Data Sets Accelerating Deployment of ISO15926 == 5 5 == ''Realizing Open Information Interoperability'' == 6 6 ---- 7 7 = IDS-ADI Project Infrastructure = 8 9 8 This page exists to describe the scopes, organization, deliverables and status of the IDS-ADI Projects. 10 9 … … 13 12 The [wiki:IdsAdiProject IDS-ADI Projects], like the [wiki:IdsAdiStandardStructure ISO15926 standard] itself, are in several inter-related parts. These workscopes range from creation of the standard docouments for ISO publication, data modelling, reference data creation, implementation software and services, training, and support for special interest groups around business areas & engineering disciplines and around extending modelling approaches and technologies. 14 13 15 16 14 This page therefore itemizes all the workscopes and deliverables as undertaken by [wiki:IdsAdiProject IDS-ADI Projects] and provides each with a current status, a responsible party and links to further on-line information about each project / task / sub-project. 17 15 18 16 == Cordination Processes == 19 20 17 IDS-ADI relies on cooperation between member organizations and individuals. Individual groups teams and tasks are largely autonomous subject only to steering inputs and compliance with core deliverables. The coordination is achieved through the following :- 21 18 … … 23 20 24 21 * Steering Group - Meets Ad-Hoc, quarterly or to address specific issues. 25 * General Management Coordination - Meets 8:30am-10:00am EST Thursdays (15-20 regular attendees) 26 * Modeling, Methodologies & Content - Meets 8:30am-10:00am EST Mondays (6-10 regular attendees) 27 * Implementation & technology - Meets 8:30am-10:00am EST Wednesdays (4-8 regular attendees) 22 * General Management Coordination - Meets 8:30am-10:00am EST Thursdays (15-20 regular attendees) 23 * Modeling, Methodologies & Content - Meets 8:30am-10:00am EST Mondays (6-10 regular attendees) 24 * Implementation & technology - Meets 8:30am-10:00am EST Wednesdays (4-8 regular attendees) 28 25 * Other Core IDS-ADI & Matrix Sub-Projects - Ad-Hoc to suit team needs. 29 26 … … 44 41 45 42 == Work-Breakdown Overview == 46 47 43 ''(Whole Elephant WBS - In progress)'' 48 44 49 45 == Project Work Scopes == 50 51 46 * '''IDS-ADI Steering Group''' 52 47 * '''IDS-ADI General Management Coordination''' … … 58 53 59 54 == IDS-ADI Steering Group == 60 61 55 The IDS-ADI Steering group currently consists of :- Robin Benjamins (Chair), Magne Valen-Sendstad, Onno Paap, Adrian Laud, Manoj Dharwadkar, Julian Bourne and Ian Glendinning. 62 56 63 Periodically co-opted into the steering group for liaison purposes are representatives of POSC -Caesar, FIATECH or other industry intiatives :- eg Mark Palmer, Ric Jackson.57 Periodically co-opted into the steering group for liaison purposes are representatives of POSC Caesar, FIATECH or other industry intiatives :- eg Mark Palmer, Ric Jackson. 64 58 65 59 The scope of the steering group is to set policies and priorities for IDS-ADI projects, to resolve any conflicts or issues arising between IDS-ADI Projects, or with external initiatives, that cannot be solved by ongoing management coordination. A further role of the steering group is management reporting (eg of deliverable progress and budgets) to the sponsoring consortia and their member organisations. 66 60 67 61 == IDS-ADI General Management Coordination == 68 69 62 ''(Coordination of all IDS-ADI Projects, ISO Standard publication process, Liaison with and representation at industry conferences and other industry standardization initiatives.)'' 70 63 71 64 == IDS-ADI Core Deliverables == 72 73 65 ''(Modelers & Impelementors per below - plus ISO Standard Parts, Compliance Spec, Public Communications / Web-pages / Presentations ....)'' 74 66 75 67 == IDS-ADI Modeling, Methods & Content Team == 76 77 68 Also known simply as the "Modelers". Team Lead is Ian Glendinning. 78 69 … … 80 71 81 72 == IDS-ADI Implementation & Technology Team == 82 83 73 Also known simply as the "Implementors". Team Lead is Julian Bourne. 84 74 … … 86 76 87 77 == IDS-ADI Matrix Sub-Projects == 88 89 78 ''itemize all identified sub-projects, identify and link to active sub-projects.'' 90 79 91 80 == SIG's (Special Interest Groups) == 92 93 81 SIG's by definition have special interests that are not limited to the current scope of IDS-ADI and ISO15926. SIG's have scopes that are above and beyond IDS-ADI and ISO15926, but which may overlap significantly with IDS-ADI and ISO15926. 94 82 95 For POSC -Caesar SIG's refer to [wiki/Sig PCA SIG's Page].83 For POSC Caesar SIG's refer to [wiki/Sig PCA SIG's Page]. 96 84 97 85 SIG's which overlap significantly with IDS-ADI and ISO15926 are :- … … 104 92 105 93 ---- 94 == All below holding extract from previous pages - subject to further editing and/or moving to other subsidiary pages == 95 These are Standing web conference meetings: 106 96 107 == All below holding extract from previous pages - subject to further editing and/or moving to other subsidiary pages == 97 8:30am-10:00am EST Thursdays - general meeting (15-20 regular attendees) 8:30am-10:00am EST Mondays - modeling, methodologies & content meeting (6-10 regular attendees) 8:30am-10:00am EST Wednesdays - implementation and technology meeting (4-8 regular attendees) Core ADI-IDS & Matrix Projects 108 98 99 All core project and subproject documentation is kept in the "Subversion" Document Repository. 109 100 110 These are 111 Standing web conference meetings: 101 Folders are organised according to project / content / subject types. These include scopes / specifications / methodologies / notes-of-meetings / action-lists etc. (ie folders are NOT organised according to file types.) 112 102 113 8:30am-10:00am EST Thursdays - general meeting (15-20 regular attendees) 114 8:30am-10:00am EST Mondays - modeling, methodologies & content meeting (6-10 regular attendees) 115 8:30am-10:00am EST Wednesdays - implementation and technology meeting (4-8 regular attendees) 116 Core ADI-IDS & Matrix Projects 103 The projects include 117 104 118 All core project and subproject documentation is kept in the "Subversion" Document Repository. 105 Core IDS-ADI Projects ... documentation common across all sub-projects (organised primarily by core project area - management / modelling / content / implementation, etc) Matrix-Sub-Projects ... documentation specific to each sub-project. Wiki pages should link to individual documents or folders directly wherever relevant. Browsing and accessing any and all documents is via your browser links to documents and via the repository link above. 119 106 120 Folders are organised according to project / content / subject types. These include scopes / specifications / methodologies / notes-of-meetings / action-lists etc. (ie folders are NOT organised according to file types.) 107 Uploading new and revised folders and documents should be done using the Tortoise SVN Client (See XXXX for SVN set-up and use). Notification of updates is recommended by RSS subscription to the Timeline page. (Ref XXXX) 121 108 122 The projects include 109 Status of Deliverables 123 110 124 Core IDS-ADI Projects ... documentation common across all sub-projects (organised primarily by core project area - management / modelling / content / implementation, etc) 125 Matrix-Sub-Projects ... documentation specific to each sub-project. 126 Wiki pages should link to individual documents or folders directly wherever relevant. Browsing and accessing any and all documents is via your browser links to documents and via the repository link above. 127 128 Uploading new and revised folders and documents should be done using the Tortoise SVN Client (See XXXX for SVN set-up and use). Notification of updates is recommended by RSS subscription to the Timeline page. (Ref XXXX) 129 130 Status of Deliverables 131 132 The status of some of the infrastructure-related deliverables undertaken by this umbrella group are detailed on the IDS-ADI Infrastructure Status Page. 133 111 The status of some of the infrastructure-related deliverables undertaken by this umbrella group are detailed on the IDS-ADI Infrastructure Status Page. 134 112 135 113 COMPLIANCE … … 173 151 Technical introductory collateral targeted at implementation is thoroughly scant at this stage: there is a need to provide almost a "path" or "plan" to integrated ISO 15926 into vendor tools in a meaningful way. Julian Bourne had volunteered to lead that initiative. 174 152 175 176 153 RDS/WIP 177 154 … … 186 163 Overview 187 164 188 The [ RdsWipProject RDS/WIP project] provides the software and Internet-accessible services for publishing both the standard and contributions to its associated reference data library. There are two exposed forms of this data: one is intended for machines, expressed in OWL/RDF and delivered via SPARQL; the other is intended for humans and is presented using HTML in a web browser.165 The [wiki:RdsWipProject RDS/WIP project] provides the software and Internet-accessible services for publishing both the standard and contributions to its associated reference data library. There are two exposed forms of this data: one is intended for machines, expressed in OWL/RDF and delivered via SPARQL; the other is intended for humans and is presented using HTML in a web browser. 189 166 190 167 Report … … 192 169 The existing deployment is only partially operational: it does not reach the necessary mark in aspects such as performance and standards conformance and is missing machine-driven mechanisms for submitting new contributions. Also, its internal structure is far too rigid and requires a great deal of coordination between different parties to effect change. 193 170 194 The [ RdsWipOnePlan next stage (RDS/WIP 1.0)] will be to move that solution to a more robust and faster technical framework, dropping the support for direct editing in the interim, but adding much more flexible support for incorporating bulk contributions, with some administrator intervention.171 The [wiki:RdsWipOnePlan next stage (RDS/WIP 1.0)] will be to move that solution to a more robust and faster technical framework, dropping the support for direct editing in the interim, but adding much more flexible support for incorporating bulk contributions, with some administrator intervention. 195 172 196 The [ RdsWipTwoPlan following stage (RDS/WIP 2.0)] will be to provide a completely automated path to incorporate bulk contributions and the administration features needed to manage that; along with recreating a direct editing feature for ISO 15926 data only.173 The [wiki:RdsWipTwoPlan following stage (RDS/WIP 2.0)] will be to provide a completely automated path to incorporate bulk contributions and the administration features needed to manage that; along with recreating a direct editing feature for ISO 15926 data only. 197 174 198 175 The main advantage of the revised platform, apart from performance and conformance, is that it will allow any RDF to be published, which leaves a great deal of flexibility in structure and representation - allowing the structures and representation to change quickly and without much need for coordination. It also provides a lower barrier to entry when starting a collaborative project to harmonize standards against one another. These features are inherent in the architecture and to the technology choices and will be available from the outset of RDS WIP 1.0.
