Changes between Version 14 and Version 15 of IdsAdiInfrastructureStatus

Show
Ignore:
Timestamp:
10/31/08 04:14:25 (13 years ago)
Author:
mvsen (IP: 193.212.132.34)
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • IdsAdiInfrastructureStatus

    v14 v15  
    11[[TracNav(TracNav/IdsAdi)]] [[Image(wiki:IdsAdiBranding:Logo-128x128.gif)]] 
    22 
    3 = POSC-Caesar FIATECH IDS-ADI Projects = 
     3= POSC Caesar FIATECH IDS-ADI Projects = 
    44== Intelligent Data Sets Accelerating Deployment of ISO15926 == 
    55== ''Realizing Open Information Interoperability'' == 
    66---- 
    77= IDS-ADI Project Infrastructure = 
    8  
    98This page exists to describe the scopes, organization, deliverables and status of the IDS-ADI Projects. 
    109 
     
    1312The [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. 
    1413 
    15  
    1614This 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. 
    1715 
    1816== Cordination Processes == 
    19  
    2017IDS-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 :- 
    2118 
     
    2320 
    2421 * 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) 
    2825 * Other Core IDS-ADI & Matrix Sub-Projects - Ad-Hoc to suit team needs. 
    2926 
     
    4441 
    4542== Work-Breakdown Overview == 
    46  
    4743''(Whole Elephant WBS - In progress)'' 
    4844 
    4945== Project Work Scopes == 
    50  
    5146 * '''IDS-ADI Steering Group''' 
    5247 * '''IDS-ADI General Management Coordination''' 
     
    5853 
    5954== IDS-ADI Steering Group == 
    60  
    6155The IDS-ADI Steering group currently consists of :- Robin Benjamins (Chair), Magne Valen-Sendstad, Onno Paap, Adrian Laud, Manoj Dharwadkar, Julian Bourne and Ian Glendinning. 
    6256 
    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. 
     57Periodically co-opted into the steering group for liaison purposes are representatives of POSC Caesar, FIATECH or other industry intiatives :- eg Mark Palmer, Ric Jackson. 
    6458 
    6559The 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. 
    6660 
    6761== IDS-ADI General Management Coordination == 
    68  
    6962''(Coordination of all IDS-ADI Projects, ISO Standard publication process, Liaison with and representation at industry conferences and other industry standardization initiatives.)'' 
    7063 
    7164== IDS-ADI Core Deliverables == 
    72  
    7365''(Modelers & Impelementors per below - plus ISO Standard Parts, Compliance Spec, Public Communications / Web-pages / Presentations ....)'' 
    7466 
    7567== IDS-ADI Modeling, Methods & Content Team == 
    76  
    7768Also known simply as the "Modelers". Team Lead is Ian Glendinning. 
    7869 
     
    8071 
    8172== IDS-ADI Implementation & Technology Team == 
    82  
    8373Also known simply as the "Implementors". Team Lead is Julian Bourne. 
    8474 
     
    8676 
    8777== IDS-ADI Matrix Sub-Projects == 
    88  
    8978''itemize all identified sub-projects, identify and link to active sub-projects.'' 
    9079 
    9180== SIG's (Special Interest Groups) == 
    92  
    9381SIG'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. 
    9482 
    95 For POSC-Caesar SIG's refer to [wiki/Sig PCA SIG's Page]. 
     83For POSC Caesar SIG's refer to [wiki/Sig PCA SIG's Page]. 
    9684 
    9785SIG's which overlap significantly with IDS-ADI and ISO15926 are :- 
     
    10492 
    10593---- 
     94== All below holding extract from previous pages - subject to further editing and/or moving to other subsidiary pages == 
     95These are  Standing web conference meetings: 
    10696 
    107 == All below holding extract from previous pages - subject to further editing and/or moving to other subsidiary pages == 
     978: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 
    10898 
     99All core project and subproject documentation is kept in the "Subversion" Document Repository. 
    109100 
    110 These are  
    111 Standing web conference meetings:  
     101Folders 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.) 
    112102 
    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  
     103The projects include 
    117104 
    118 All core project and subproject documentation is kept in the "Subversion" Document Repository.  
     105Core 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. 
    119106 
    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.)  
     107Uploading 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) 
    121108 
    122 The projects include  
     109Status of Deliverables 
    123110 
    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  
     111The status of some of the infrastructure-related deliverables undertaken by this umbrella group are detailed on the IDS-ADI Infrastructure Status Page. 
    134112 
    135113COMPLIANCE 
     
    173151Technical 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. 
    174152 
    175  
    176153RDS/WIP 
    177154 
     
    186163Overview 
    187164 
    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. 
     165The [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. 
    189166 
    190167Report 
     
    192169The 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. 
    193170 
    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. 
     171The [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. 
    195172 
    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. 
     173The [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. 
    197174 
    198175The 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. 
Home
About PCA
Reference Data Services (RDS)
RDS Operations Support
Meetings and Conferences
ISO 15926
Special Interest Groups
Technical Advisory Board
Norwegian Continental Shelf Std
Projects
Search