# Presentation: 299808

## A Flexible XML-Based Thesaurus Approach for the Federal Government: Highlights

- by _[Ken Sall ](mailto:xml@kensall.com)_and Judith Newton
- for the DRM Working Group
-        March 17, 2005**	**
- _[http://](http://kensall.com/gov/glossary/)__[kensall.com/gov/glossary](http://kensall.com/gov/glossary/)_

## Agenda

**Candidate Requirements**
**Relevant ISO Specifications**
**ISO 2788:1986 (oldest)**
**ISO 1087:2000**
**ISO 704:2000**
**ISO 15836:2003 - DCMI Metadata Terms**
**SKOS = ISO 2788 + W3C + XML + metadata + RDF + Semantic Web + Web Service + Wiki**
**Recommended Plan of Action**
**Thesaurus Spreadsheet w/SKOS Subset**
**Initial XML Schema**

## Candidate   Requirements (1)

**The glossary / lexicon / **_**thesaurus**_** SHOULD use XML syntax with a schema (DTD, XML Schema, or RDF-S) for validation.**
**It SHOULD be applicable to any government agency.**
**The schema SHOULD be available to any civil servant or citizen. [Should govt be expected to use it?]**
**The schema SHOULD not be overly complex.**
**The schema SHOULD contain few required elements and many optional and/or repeatable elements.**
**It SHOULD be relatively easy to add new terms to the lexicon. Payware SHOULD not be necessary for authoring.**

## Candidate   Requirements (2)

**It SHOULD be relatively easy to combine terms authored by different individuals and different agencies, if desired.**
**The elements in the schema SHOULD be chosen with ISO standards in mind, to the degree that this does not overly complicate the schema.**
**It SHOULD be possible to create an XSLT stylesheet based upon the model to display an XML glossary instance document as HTML in modern browsers (IE, Firefox).**
**It is DESIRABLE that the XSLT generate additional search links not in the source.**
**Multiple definitions of the same term MUST be permitted, with either same or different context.**

## Candidate   Requirements (3)

**The entire approach SHOULD foster a clean separation of collaborative roles:**
**Developer of schema vs. developer of stylesheets**
**Author/collector of terms and definitions**
**Reviewer/approver of definitions**
**Consumer of results (e.g., agency with custom XSLT)**
**It SHOULD support semantic relationships between terms including related-to and synonyms.**
**An approval process SHOULD be defined, but it should *****not***** interfere with contributions. Un-reviewed definitions would still be accessible, but without the “stamp of approval”.**
**It MUST be possible to indicate a term’s**
**Source (agency, author, document, and/or URL)**
**Context**
**Approval status**
**TBD – what else is mandatory?**

## Candidate   Requirements (4)

**Clear authoring conventions SHOULD be established**
**Case convention (UpperCamelCase, Title Case, lowercase, ?)**
**Pluralization (use singular form)**
**Compound terms (e.g., Data Architecture, Data Class)**
**Placement of acronym/abbreviation (separate element)**
**Placement of source/context/concept (separate element)**
**Citation method (URIs, bibliographical, free form?) [Source could contain child elements for each possible format]**
**TBD others?**
**Usage notes and/or examples are DESIRABLE.**

- Vote by requirement # to: _[xml@kensall.com](mailto:xml@kensall.com)__ ; subject “glossary”.  Comments optional._
- +   = in favor (desirable)
- ++ = change SHOULD to MUST (mandatory)
- --   = not a requirement
- 0   = no opinion

## Sall’s XML Glossary Model Strawman

- _[Previous Presentation](http://kensall.com/gov/glossary/XML-Glossary-Strawman.ppt)_

## XML Example of One Term

** ****<****Term**** ****id****="ontology">**
**    ****<****Name****>ontology</Name>**
**    ****<****DefinitionSection****>**
**      ****<****Concept****>semantic web</Concept>**
**      ****<****Concept****>knowledge management</Concept>**
**      ****<****Definition****>Defines the common words and concepts used to describe and represent an area of knowledge, and so standardizes the meanings.**
**      ****An ontology includes classes in the domains of interest, instances, relationships, properties and their values,**
**      ****functions of and processes involving the objects, and relevant constraints and rules.</Definition>**
**      ****<****Source****>Daconta, Obrst, Smith</Source>**
**      ****<****Usage****>An onotology can range from the simple notion of a taxonomy to a thesaurus, to a conceptual model, to a logical theory.  **
**      ****[Daconta, Obrst, Smith]</Usage>**
**      ****<****Synonym****>classification system</Synonym>**
**      ****<****RelatedTerm****>taxonomy</RelatedTerm>**
**      ****<****RelatedTerm****>OWL</RelatedTerm>**
**    ****</DefinitionSection>**
**    ****<****DefinitionSection****>**
**      ****<Concept>philosophy</Concept>**
**      ****<Definition>[sometimes "Ontology"] the metaphysical study of the nature of being and existence</Definition>**
**      ****<Source>WordNet</Source>**
**      ****<Usage>Both the ontology and manner of human existence are of concern to Existentialism.</Usage>**
**      ****<Synonym>metaphysics</Synonym>**
**    ****</DefinitionSection>**
**  ****</Term>**

## Search Links Bootstrap: Based on CDT-FG + CAF Glossary.doc

## ISO 2788:1986   [1]

**“****Documentation – Guidelines for the establishment and development of monolingual thesauri”; replaces ISO 2788:1974**
**From Technical Committee ISO/TC ****46****, ****Documentation**** **
**Guidelines for:**
**Selecting terms for inclusion in *****thesaurus***
**Expressing *****relationships***** between the selected terms**
**Could serve as our guidelines for term selection and definition concepts**
**preferred term – descriptor (main entry point)**
**non-preferred term - synonym**

## ISO 2788:1986  [2]

## ISO 2788:1986  [3]

- Judy Newton has offered to create an “executive summary” of ISO 2788.

## ISO 1087-1:2000   [1]

**1990: “Vocabulary of terminology”**
**2000: “TERMINOLOGY WORK — VOCABULARY — Part 1: Theory and application”**
**Mainly vocabulary (normative)**
**Concept diagrams (informative)**

## ISO 1087-1:2000   [2]

## ISO 1087-1:2000   [3]

***Subject field***** (domain) – field of special knowledge**
***Concept***** – unit of knowledge created by a unique combination of characteristics**
***Characteristic***** – abstraction of a property of an object or of a set of objects**
***Extension***** – set of objects to which concept corresponds**
***Intension***** – set of characteristics which make up the concept**

## ISO 1087-1:2000   [4]

**Hierarchical Relation**
***Generic Relation:*****  vehicle and car**
***Partitive Relation:***** week and day**
***Associative Relation:***** baking and oven**
***Extensional definition***** = enumerating all subordinate concepts under one criterion of subdivision (e.g., noble gases = {helium, neon, argon, crypton, xenon, or radon})**

## ISO 1087-1:2000   [5]

***Terminology work***** has 3 types of *****Designators***** (representation of a concept by a sign that denotes it)**
***Symbol***** **
***Appellation***** – verbal designation of individual concept**
***Term***** - verbal designation of a general concept in a specific subject field; may have variants (i.e., alternate spellings)**

## ISO 1087-1:2000   [6]

**Kinds of Terms (sample)**
***Simple***** – one root**
***Complex***** – two or more roots (e.g., bookmaker, fault tolerance)**
***Clipped term***** – abbreviation formed by truncating part of a simple term (e.g., flu for influenza, vet for veterinarian)**
***Blend***** – formed by clipping and combining two separate terms (e.g., infomercial = information + commercial)**
***Preferred term***** – rated as the primary term for a given concept; usually the *****entry term***

## ISO 1087-1:2000   [7]

***Polysemy***** – one designation represents two or more concepts **_**sharing**_** certain characteristics (e.g., bridge: structure to carry traffic over a gap; dental plate)**
***Homonymy***** - one designation represents two or more **_**unrelated**_** concepts (e.g., bark: sound made by dog; sailing vessel)**
**The more common *****terminological data***** include:**
**	****	**** ****entry term, definition, note, grammatical label, subject label, language identifier, country identifier, and source identifier.**

## ISO 1087-1:2000   [8]

***Terminological dictionary***** - ****collection of terminological entries presenting information related to concepts or designations from one or more specific subject fields**
***Vocabulary***** - terminological dictionary which contains designations and definitions from one or more specific subject fields**
***Glossary***** - terminological dictionary which contains a list of designations from a subject field, together with equivalents in one or more languages [In English common language usage glossary can refer to a unilingual list of designations and definitions in a particular subject field.]**

## ISO 704:2000    [1]

**“****Terminology work — Principles and methods”**
**Replaces ISO 704:1987.**
**Technical Committee ISO/TC ****37****, ****Terminology**
**Establishes basic principles and methods for preparing and compiling terminologies.**
**Describes the links between objects, concepts, and their representations through the use of terminologies.**
**Borrows terms from ISO 1087-1:2000 (i.e., object, concept, characteristic, intension, extension, etc.)**

## ISO 704:2000   [2]

***Essential vs. non-essential characteristics***
**Graphite is encased in wood?**
**One end may be sharpened to a point?**
**Is it indispensable to understanding a concept?**
**Property may be essential characteristic of a concept in one subject field but non-essential in another.**
***Delimiting characteristics***** – essential characteristic that distinguishes one concept from another.**
**“****When modeling a concept system, one shall concentrate on the essential and delimiting characteristics.”**

## ISO 704:2000   [3]

***Hierarchical relations***** – see ISO 1087 slides**
***Associative relations***** – thematic connection between concepts based on experience**
**Pencil case : pencil :: container : contained**
**Writing : pencil :: activity : tool**

## ISO 704:2000   [4]

**Terminology isn’t a random collection of terms. **
**“****The *****terminology***** of a *****subject field***** is the collection of *****designations***** attributed to *****concepts***** making up the knowledge structure of the field.”**
**Concept systems:**
**“****model concept structures based on specialized knowledge of a field;**
**clarify the relations between concepts;**
**form the basis for a uniform and standardized terminology;**
**facilitate the comparative analysis of concepts and designations across languages;**
**facilitate the writing of definitions.”**

## DCMI Metadata  [1]

**Dublin Core Metadata Initiative: **_**[http://dublincore.org/](http://dublincore.org/)**_** **
**Terms:  **_**[http://](http://dublincore.org/documents/dcmi-terms/)**__**[dublincore.org/documents/dcmi](http://dublincore.org/documents/dcmi-terms/)**__**[-terms/](http://dublincore.org/documents/dcmi-terms/)**_** **
**Type vocabulary: **_**[http://dublincore.org/documents/dcmi-type-vocabulary/](http://dublincore.org/documents/dcmi-type-vocabulary/)**_
**Browse **_**[Dublin Core Metadata Registry](http://dublincore.org/dcregistry/navigateServlet?reqType=termsOverviewServlet)**_
_**[ISO 15836:2003(E)](http://www.niso.org/international/SC4/n515.pdf)**_**. Information and documentation — The Dublin Core metadata element set**
_**[Element list ](http://dublincore.org/documents/usageguide/elements.shtml)**_**from Users Guide: 16 (or 18?)**

## DCMI Metadata  [2]

**xmlns:dc="http://purl.org/dc/elements/1.1/" **
**Creator="Internal Revenue Service. Customer Complaints Unit" (a person, an organization, or a service). See also Contributor.**
**Date="1998-02-16" **
**Relation “is Refined by”: **_**[conformsTo](http://dublincore.org/dcregistry/detailServlet?reqType=detail&item=http%3A%2F%2Fpurl.org%2Fdc%2Fterms%2FconformsTo)**_**  **_**[hasFormat](http://dublincore.org/dcregistry/detailServlet?reqType=detail&item=http%3A%2F%2Fpurl.org%2Fdc%2Fterms%2FhasFormat)**_**  **_**[hasPart](http://dublincore.org/dcregistry/detailServlet?reqType=detail&item=http%3A%2F%2Fpurl.org%2Fdc%2Fterms%2FhasPart)**_**  **_**[hasVersion](http://dublincore.org/dcregistry/detailServlet?reqType=detail&item=http%3A%2F%2Fpurl.org%2Fdc%2Fterms%2FhasVersion)**_**  **_**[isFormatOf](http://dublincore.org/dcregistry/detailServlet?reqType=detail&item=http%3A%2F%2Fpurl.org%2Fdc%2Fterms%2FisFormatOf)**_**  **_**[isPartOf](http://dublincore.org/dcregistry/detailServlet?reqType=detail&item=http%3A%2F%2Fpurl.org%2Fdc%2Fterms%2FisPartOf)**_**  **_**[isReferencedBy](http://dublincore.org/dcregistry/detailServlet?reqType=detail&item=http%3A%2F%2Fpurl.org%2Fdc%2Fterms%2FisReferencedBy)**_**  **_**[isReplacedBy](http://dublincore.org/dcregistry/detailServlet?reqType=detail&item=http%3A%2F%2Fpurl.org%2Fdc%2Fterms%2FisReplacedBy)**_**  **_**[isRequiredBy](http://dublincore.org/dcregistry/detailServlet?reqType=detail&item=http%3A%2F%2Fpurl.org%2Fdc%2Fterms%2FisRequiredBy)**_**  **_**[isVersionOf](http://dublincore.org/dcregistry/detailServlet?reqType=detail&item=http%3A%2F%2Fpurl.org%2Fdc%2Fterms%2FisVersionOf)**_**  **_**[references](http://dublincore.org/dcregistry/detailServlet?reqType=detail&item=http%3A%2F%2Fpurl.org%2Fdc%2Fterms%2Freferences)**_**  **_**[replaces](http://dublincore.org/dcregistry/detailServlet?reqType=detail&item=http%3A%2F%2Fpurl.org%2Fdc%2Fterms%2Freplaces)**_**  **_**[requires](http://dublincore.org/dcregistry/detailServlet?reqType=detail&item=http%3A%2F%2Fpurl.org%2Fdc%2Fterms%2Frequires)**_**  **
**Identifier – would be desirable if registry could assign this automatically as a UID**
**Audience**
**Title == Term**
**Subject == Context**

## SKOS  [1]

**Simple Knowledge Organisation System**** **
**“****SKOS is an open collaboration developing specifications and standards to support the use of knowledge organisation systems (KOS) on the semantic web.”**
**SKOS *****Core Vocabulary***** (and *****Core Guide*****) - W3C ****Working Draft: ****3/11****/05; work in progress; subject to backwards incompatible changes!**
**RDF Schema for thesauri and related knowledge organisation systems **
_**[http://www.w3.org/2004/02/skos/](http://www.w3.org/2004/02/skos/)**_
**“****SKOS Core provides a model for expressing the basic structure and content of concept schemes (thesauri, classification schemes, subject heading lists, taxonomies, terminologies, glossaries and other types of controlled vocabulary).”**

**Copyright (c) World Wide Consortium, 2005.**

**Copyright © 2005. World Wide Consortium.**

## SKOS  [2]

_**[Semantic Web Best Practices and Deployment Working Group](http://www.w3.org/2001/sw/BestPractices/)**_
**SKOS *****Core RDF Vocabulary***** - for describing thesauri, glossaries, taxonomies, terminologies. **
**“****The SKOS Core Vocabulary is an application of the Resource Description Framework (RDF), that can be used to express a concept scheme as an RDF graph. Using RDF allows data to be linked to and/or merged with other RDF data by semantic web applications.”**
**SKOS *****Mapping RDF Vocabulary***** - for describing mappings between concept schemes. **
**SKOS *****Web Service API***** – WDSL-based**

**Copyright © 2005. World Wide Consortium.**

## SKOS  [3]

_**[Quick Guide to Publishing a Thesaurus on the Semantic Web](http://www.w3.org/2004/03/thes-tf/primer/)**_
**W3C ****Working Draft in Preparation**** – 2/8/05**

- Term and Alias

- Narrower Terms

- Related Term

- Broader Term

**Copyright © 2005. World Wide Consortium.**

- Scope Note

- Key Slide

**Copyright © 2005. World Wide Consortium.**

## SKOS: RDF Serialization [4]

**Copyright © 2005. World Wide Consortium.**

**Copyright © 2005. World Wide Consortium.**

## SKOS: with Thesaurus Metadata (DCMI) [5]

**Copyright © 2005. World Wide Consortium.**

**Copyright © 2005. World Wide Consortium.**

## SKOS Complements OWL [6]

**“****SKOS-Core is intended as a complement to OWL. It does provide a basic framework for building concept schemes, but it does not carry the strictly defined semantics of OWL. Thus it is ideal for representing those types of KOS, such as thesauri, that cannot be mapped directly to an OWL ontology. SKOS is also easier to use, and harder to misuse than OWL, providing an ideal entry point for those wishing to use the Semantic Web for knowledge organisation. SKOS-Core also provides a framework for linking concepts to the words and phrases that are normally used by people to refer to them. This valuable information, once captured, can be used to support a number of tasks....” – **_**[SKOS Core Guide, 2001](http://www.w3.org/2001/sw/Europe/reports/thes/1.0/guide/)**_** version**
_**[Latest SKOS Core Guide ](http://www.w3.org/2004/02/skos/core/guide/)**_**– 2/15/05 Working Draft**

**Copyright © 2005. World Wide Consortium.**

## SKOS Core Vocabulary  [7]

***  ******Classes***_***[CollectableProperty](http://www.w3.org/2004/02/skos/core/spec/#CollectableProperty)***__***[Collection](http://www.w3.org/2004/02/skos/core/spec/#Collection)***__***[Concept](http://www.w3.org/2004/02/skos/core/spec/#Concept)***__***[ConceptScheme](http://www.w3.org/2004/02/skos/core/spec/#ConceptScheme)***__***[OrderedCollection](http://www.w3.org/2004/02/skos/core/spec/#OrderedCollection)***__*** ***_

***  ******Properties***_***[altLabel](http://www.w3.org/2004/02/skos/core/spec/#altLabel)***__***[altSymbol](http://www.w3.org/2004/02/skos/core/spec/#altSymbol)***__***[broader](http://www.w3.org/2004/02/skos/core/spec/#broader)***__***[changeNote](http://www.w3.org/2004/02/skos/core/spec/#changeNote)***__***[definition](http://www.w3.org/2004/02/skos/core/spec/#definition)***__***[editorialNote](http://www.w3.org/2004/02/skos/core/spec/#editorialNote)***__***[example](http://www.w3.org/2004/02/skos/core/spec/#example)***__***[hasTopConcept](http://www.w3.org/2004/02/skos/core/spec/#hasTopConcept)***__***[hiddenLabel](http://www.w3.org/2004/02/skos/core/spec/#hiddenLabel)***__***[historyNote](http://www.w3.org/2004/02/skos/core/spec/#historyNote)***__***[inScheme](http://www.w3.org/2004/02/skos/core/spec/#inScheme)***__***[isPrimarySubjectOf](http://www.w3.org/2004/02/skos/core/spec/#isPrimarySubjectOf)***__***[isSubjectOf](http://www.w3.org/2004/02/skos/core/spec/#isSubjectOf)***__***[member](http://www.w3.org/2004/02/skos/core/spec/#member)***__***[memberList](http://www.w3.org/2004/02/skos/core/spec/#memberList)***__***[narrower](http://www.w3.org/2004/02/skos/core/spec/#narrower)***__***[prefLabel](http://www.w3.org/2004/02/skos/core/spec/#prefLabel)***__***[prefSymbol](http://www.w3.org/2004/02/skos/core/spec/#prefSymbol)***__***[primarySubject](http://www.w3.org/2004/02/skos/core/spec/#primarySubject)***__***[privateNote](http://www.w3.org/2004/02/skos/core/spec/#privateNote)***__***[publicNote](http://www.w3.org/2004/02/skos/core/spec/#publicNote)***__***[related](http://www.w3.org/2004/02/skos/core/spec/#related)***__***[scopeNote](http://www.w3.org/2004/02/skos/core/spec/#scopeNote)***__***[semanticRelation](http://www.w3.org/2004/02/skos/core/spec/#semanticRelation)***__***[subject](http://www.w3.org/2004/02/skos/core/spec/#subject)***__***[subjectIndicator](http://www.w3.org/2004/02/skos/core/spec/#subjectIndicator)***_

- Key Slide

**Copyright © 2005. World Wide Consortium.**

## Subset of SKOS Core Vocabulary  [8]

**Concept ****- abstract idea or notion; a unit of thought; holds term and related terms**
**ConceptScheme**** – set of concepts; controlled vocabulary (e.g., what we’re developing)**
**prefLabel**** – name of term being defined; must be *****unique***** within a ConceptScheme (e.g., our thesaurus)**
**altLabel**** -  acronyms, abbreviations, spelling variants, and irregular plural/singular forms**
**related**** - concept with which there is an associative semantic relationship**
**broader**** -  more general in meaning; rendered as parent in a concept hierarchy (tree)**
**narrower**** – more specific meaning; child**
**definition****, ****example****, ****changeNote****, ****editorialNote**

**Copyright © 2005. World Wide Consortium.**

## SKOS Example [9]

**<skos:Concept rdf:about="http://my.example.org/GCL/791#concept">**
**	****<skos:prefLabel xml:lang="en">****Civil Service****</skos:prefLabel>**
**	****<skos:related rdf:resource="http://my.example.org/GCL/476#concept"/>**
**</skos:Concept>**
**<****skos:Concept**** rdf:about="http://my.example.org/GCL/476#concept">**
**	****<skos:****prefLabel ****xml:lang="en">****Public administration****</skos:prefLabel>**
**	****<skos:****altLabel**** xml:lang="en">Administration (public)</skos:altLabel>**
**	****<skos:****altLabel**** xml:lang="en">Management (public sector)</skos:altLabel>**
**	****<skos:****related**** rdf:resource="http://my.example.org/GCL/791#concept"/>**
**	****<skos:****related ****rdf:resource="http://my.example.org/GCL/982#concept"/>**
**</skos:Concept>**
**<skos:Concept rdf:about="http://my.example.org/GCL/982#concept">**
**<skos:prefLabel xml:lang="en">****Employment relations****</skos:prefLabel>**
**<skos:altLabel xml:lang="en">Conflict (industrial relations)</skos:altLabel>**
**<skos:altLabel xml:lang="en">Employers' responsibilities</skos:altLabel>**
**<skos:altLabel xml:lang="en">Industrial disputes</skos:altLabel>**
**<skos:altLabel xml:lang="en">Industrial relations</skos:altLabel>**
**<skos:altLabel xml:lang="en">Strikes (labour)</skos:altLabel>**
**<skos:altLabel xml:lang="en">Trades Unions</skos:altLabel>**
**<skos:related rdf:resource="http://my.example.org/GCL/474#concept"/>**
**<skos:related rdf:resource="http://my.example.org/GCL/476#concept"/>**
**</skos:Concept>**
**<skos:Concept rdf:about="http://my.example.org/GCL/474#concept">**
**	****<skos:prefLabel xml:lang="en">****Business management****</skos:prefLabel>**
**	****<skos:altLabel xml:lang="en">Administration (business)</skos:altLabel>**
**	****<skos:altLabel xml:lang="en">Management (business)</skos:altLabel>**
**	****<skos:related rdf:resource="http://my.example.org/GCL/982#concept"/>**
**</skos:Concept>**

**Copyright © 2005. World Wide Consortium.**

## SKOS   [10]

**Semantic Web Advanced Development for Europe: **_**[SWAD-Europe Thesaurus Activity](http://www.w3.org/2001/sw/Europe/reports/thes/)**_** and **_**[SWAD-E home](http://www.w3.org/2001/sw/Europe/)**_
**Standards and Best Practises for USING Knowledge Organisation Systems ON THE Semantic Web [**_**[PPT from Nov. 2004 ](http://www.w3.org/2001/sw/Europe/reports/thes/pres/NKOS2004.ppt)**_**conference]**
_**[RDF Thesaurus Prototype](http://www.w3.org/2001/sw/Europe/reports/thes/8.7/)**_** – “****thesaurus research prototype demonstrating the SKOS schema by means of the SKOS API web service and a demonstrator containing sample data, some simple clients for using the API, documentation and description of related work.” **
**“****Scope of SKOS Core: ‘Language-oriented KOS’**
**Thesauri**
**Glossaries**
**Controlled Vocabularies**
**Terminologies**
**Classification Schemes? **
**Taxonomies?**
**Web directories ... Weblog category schemes ... ?”**
_**[Thesaurus Research Prototype Work Plan](http://www.w3.org/2001/sw/Europe/plan/workpackages/live/esw-wp-8.html)**_**: “****Refining the existing RDF thesaurus schema to make it ****compatible with ISO 2788****: Guidelines for the establishment and development of monolingual thesauri, will ensure the schema is compatible with most existing thesauri, improving the possibilities of migration.” **
_**[SKOS Thesaurus Web Service Demonstrations](http://thes.ilrt.bris.ac.uk/demos/get)**_
_**[public-esw-thes@w3.org Mail Archives](http://lists.w3.org/Archives/Public/public-esw-thes/)**_

- Not in handout

**Copyright © 2005. World Wide Consortium.**

## Next Steps - Revised

**Determine interested agencies and establish funding.**
**Before agencies start authoring, form ad hoc working groups to finalize DTD or XML Schema *****using elements that parallel SKOS and ISO 2788*****. (Agencies can gather their terms and definitions using an interim schema or using spreadsheets.)**
**Determine entry review/approval process and form second team to conduct reviews of submissions.**
**Revise initial XSLT to match final Glossary schema.**
**Determine repository and submission mechanisms.**
**Could be a good use for **_**[CORE.gov](https://www.core.gov/)**_**?**
**Coordinate with **_**[Plans for Derived XML Registry Prototype](http://xml.gov/presentations/starbourne/Plan4DerivedXML-Registry.ppt)**_**?**
**Write additional XSLT stylesheets for:**
**Merging terms and pulling agency-specific terms**
**Special display requirements**
**Filtering only approved terms**
**Filtering only terms that meet agency-specific criteria**

## Candidate Review Elements

**Review – repeatable container element**
**ReviewDate – in a standard format a la GJXDM**
**ReviewerEmail**
**ReviewerName?**
**ReviewStatus = {approved, rejected, pending}**
**ReviewDecision = {primary, secondary, tertiary}**
**(This idea needs more thought and probably can be deferred.)**

## Recommendation: Phased Approach

**Emphasis on ease of implementation and use in the short run, but with expansion path for long run.**
**Phase 1: **
**	****a) **_**Developers**_**: Create schema and distribute/post.**
**    ****b) **_**Expert**_**: Distill ISO 2788 to 3-4 page authoring guide.**
**Phase 2: **_**Authors**_**: Gather terms and definitions.**
**Phase 3: **_**Reviewers**_**: Review definitions and approve, reject, or defer (tentative approve? Pending?).**
**Phase 4: “Publish” Thesaurus version 1.0.**
**Phase 5: Iterate Phases 2, 3, and 4 for next version. On-going access; can access terms not yet reviewed.**
**Phase 6: **_**Developers**_**: Translate schema and Thesaurus to SKOS, after evaluating effort. Can be begun after Phase 1, but need representative set of terms and definitions.  **

- Here comes the new stuff!

## Our Subset: SKOS Core Vocabulary

***  ******Classes***_***[Collection](http://www.w3.org/2004/02/skos/core/spec/#Collection)***__***[Concept](http://www.w3.org/2004/02/skos/core/spec/#Concept)***__*** ***_

***  ******Properties*****altLabel****broader****(changeNote)****definition****(editorialNote)****example****narrower****prefLabel****related****scopeNote****subject****(****semanticRelation)**
**plus 2 more of our own:**
**SOURCE**
**ABBREVIATION_OR_ACRONYM**

**Copyright © 2005. World Wide Consortium.**

## Borrowed SKOS Properties  [1]

## Borrowed SKOS Properties  [2]

## Initial XML Schema - Main

## Initial XML Schema - Ancillary

## GAO Thesaurus Excerpt in Our .xls

- GAO.xml - validated