1 / 13

JISC Technical Standards

JISC Technical Standards. Jon Duke Andy Jordan. Purpose. Pull together the JISC’s guidance Identify a way forward Tie in with allied bodies Propose maintenance arrangements. Scope. All services and projects Existing guidance documents

cutler
Download Presentation

JISC Technical Standards

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. JISC Technical Standards Jon Duke Andy Jordan

  2. Purpose • Pull together the JISC’s guidance • Identify a way forward • Tie in with allied bodies • Propose maintenance arrangements

  3. Scope • All services and projects • Existing guidance documents • Appraisal of other work such as Becta, NOF-digitise, the NLN and e-GIF

  4. Our approach • Initially consult with key stakeholders • Then consultation process • email list of ~ 70 volunteers from the JISC, its community and other organisations • area on JISC web site to post documents for list members

  5. Key foci of standards activity • UKOLN, CETIS, TechDis • e-Government Unit • e-GIF and Technical Standards Catalogue • Parliamentary mandate for public sector use

  6. Conclusions - 1 • Favour open standards but • recognise sometimes only proprietary ones available • Link JISC maintenance process to e-GIF • Use checklist based approach for appraising standards • Minimise risk

  7. Conclusions - 2 • Tools should be used to verify compliance of developed applications to standards • Metadata of JISC projects to include statement of compliance/non-compliance • Use SOA approach to organise presentation of standards guidance

  8. SOA approach Presentation functionality (delivery channels etc.) eLearning application functionality eResearch application functionality Common functionality (e.g. authentication/authorisation, resource discovery, metadata, content management, digital library) Infrastructure (e.g. JANET)

  9. Key audiences are Manager Developer JISC development projects Third party vendors Institutions and organisations in community JISC funded service providers

  10. Guidance publication • Initially on the web • Intention of moving to an XML based approach • to harmonise with any similar moves made by e-GIF

  11. Maintenance • Policy should rest with the JISC • Annual Review • UKOLN should manage the process • 6 monthly Review • Subcontracting parts out

  12. UKOLN pulls drafts together Sub-contractors work on draft Publish Consult community Write guidance Publish draft Amend Consult publicly Publish draft Amend Publish Prepare next version

  13. Key Issues • Open Standards • Maintenance • Presentation • Tying to eGIF Comments please

More Related