User Tools
Add this page to your book 
Remove this page from your book 
Manage book (
Help This is an old revision of the document!
Table of Contents
Detailed Rolling Notes Thursday 01 Sept
Back to start
The main aim of this and the next coule of sessions is to identify what metadata we need, define a structure of metaterms, and define exactly how to render these as OWL Annotation Properties, in the UML version of the FIBO model, using the agreed base class within ODM. Today we look at some of the metadata itself.
We started with a presentation and discussion led by Elisa Kendall, based on some sample metadata that was developed for this week's Proof of Concept presentation.
Metadata
Elisa went through some of the draft metadata in the attached email. These mainly (but not only) relate to provenance and labels. There are also metadata terms for change management concepts, which will be needed for the new content process changes (see later notes).
This is clearly not definitive, but here is a notional set of metadata for the LegalEntityIdentifier class:
NOTE: THIS DID NOT FORMAT WELL! Bear with me…
| skos:prefLabel | “legal entity identifier” |
| skos:altLabel | <optional – placeholder for an alternate label> |
| iso1087:hasDesignation | LEI |
| rdf:type | http://www.omg.org/spec/VTW/20111114/iso1087#Symbol |
| skos:definition | “A legal entity identifier (LEI) is a unique ID associated with a single corporate entity.” |
| dc:source | “SIFMA (Securities Industry and Financial Markets Association) overview discussion of Legal Entity Identifier, http://www.sifma.org/issues/operations-and-technology/legal-entity-identifier/overview/ |
| dct:issued | “2011-11-14” |
| dct:modified | <optional – placeholder for modification date> |
| dct:hasVersion | http://www.omg.org/spec/FIBO/1.0/usage/history/BusinessEntity/LEI#LegalEntityIdentifier-001 |
| dct:replaces | <optional – placeholder for link to prior version> |
| iso1087:hasAcceptabilityRating | preferred |
| rdfs:isDefinedBy | http://www.omg.org/spec/FIBO/20111114/BusinessEntity/LEI#LegalEntityIdentifier |
| rdfs:seeAlso | “Office of Financial Research; Statement on Legal Entity Identification for Financial Contracts, http://www.federalregister.gov/articles/2010/11/30/2010-30018/office-of-financial-research-statement-on-legal-entity-identification-for-financial-contracts |
| skos:note | “Additional background information can be found at http://en.wikipedia.org/wiki/Legal_Entity_Identifier“ |
Namespace Legend dc Dublin Core Metadata Elements – http://purl.org/dc/elements/1.1/ dct Dublin Core (DCMI) Terms – http://purl.org/dc/terms/ skos Simple Knowledge Organization System (SKOS) – http://www.w3.org/2004/02/skos/core iso1087 ISO 1087: Vocabulary for Terminology Work (VTW) – http://www.omg.org/spec/VTW/20111114/iso1087 (notional, based on submission by RFC for the December OMG meeting in Santa Clara)
Additional notes and conversation:
EK: Also SKOS ScopeNote will be of relevance.
For the metadata we will need a Laundry list of: - Mandatory - Mandatory if Available - Recommended - Optional
Action: EK can put these in a spreadsheet.
Discussion
Labels – always use. A label is mandatory whether it’s RDF or SKOS. In SKOS, if Pref label, 1 or 1 per language. So have language label pair. Can have mulptiple of those preferred. Only one preferred oer language,. Aoways see a text definition. SKOS Definition, Note, SKOW Example. 5 or 4 or those describe the textual information we should include in formal definitions. Useful to differentiate. Otherwise in OWL you can’t distinguish what is a definition and what is a note.
ISO - note, example, definition. Pick the ones from SKOS. Source critical. Source for definition important. Not easy / SKOS / DC in any obvious way: further definitions, extended definitions, more notes. Not a nice way of comparing those with additional
Further Discussion
Is on another machine so if you're reading this I'm halfway through putting these notes up.
