Registry breakout group DC-8, National Library of Canada 5 October 2000

Agenda Purpose of registry Scope of registry Policy and process –Toms strawman proposal –Versioning Relate issues to technical solution WG charter

User requirements Useability impacts architecture Need to produce formal statement of requirements (for registry, for schema expression) Granularity required at element level Require access to additional information related to elements – crosswalks, endorsements, annotations Extensions to RDF Schema language needed

Specific user requirements Query status of qualifiers Mappings, crosswalks Who is using what Machine-readability Ability to submit (publish once!) Editorial review, annotation of content

User requirements contd Look for schemas (elements) by domain Specify authority Collecting information on usage Archiving elements no longer in use or declared obsolete

Scope Pin down requirements (formal statement to circulate to XML Schema, RDF Schema, XML DTD experts) Identify milestones for phased implementation One-place reference for search query formulation Pointers to related services Clarify difference between user guide and registry(no duplication) Specify which sorts of schemas we include and prioiritise (e.g.DC namespaces, application profiles)

Policy and process Strawman: role for usage committee in annotation, role of working groups….. Status of elements depends on agreed criteria Usage committee role limited to valid grammar coniderations WG recommend qualifiers Clarify roles of committees (Registry, Usage, Advisory)

Actions Ensure formal charter Draw up statement of requirements –for registry –for schema language (application profiles) Outline milestones to Phase 1 and 2 implementation