Open PermID Release Notes R1.9

Transcription

1 Preface Permid.org is the public-facing portal for Thomson Reuters core entities and metadata, providing the tools that enable you to work with PermIDs unique identifiers for objects in the Thomson Reuters Information Model (TRiM). Each PermID is associated with a web address, which serves as the permanent identity for that entity. Permid.org provides three tools for returning PermIDs: Entity Search: Search for an entity by name, identifier, or PermID to retrieve entity information. Record Matching: Upload up to 1,000 of your own records to return PermIDs for each one. Open Calais Tagging: Use Open Calais to automatically extract PermIDs for the organizations, instruments, and quotes hidden within your unstructured text. Each of these tools also has an API associated with it, with API keys available to registered users. This document is intended for existing users of Open PermID, and describes the changes in the current version relative to the previous release. Note: User Guides for the three APIs are available on: Please note that Open Calais is a stand-alone product, with distinct releases and release notes. See

2 New and Enhanced Features This release includes the following new features and enhancements: 1. LEI - new field in Organization entity 2. Add prefixes in API response of the following entities o Industry o Asset class 3. Geoname URL instead of Geoname code in currency API response

3 1. LEI - NEW FIELD IN ORGANIZATION ENTITY The Legal Entity Identifier (LEI) is a unique 20-character alphanumeric code based on the ISO standard developed by the International Organization of Standardization, which is assigned to legal entities that are counterparties to financial transactions. The LEI code itself is neutral, with no embedded intelligence or country codes which would create unnecessary complexity for users. You can get the LEI code of an organization on the organization page or in the lookup API response. LEI on Organization page Note: The LEI field is available to all users.

4 Examples- LEI in Lookup API response Organization: Thomson Reuters Corp PermId URI: LEI in Organization API response (Turtle format) Request: tr-common: tr-fin: mdaas: tr-org: xsd: fibo-be-le-cb: vcard: < < a tr-org:organization ; mdaas:headquartersaddress "3 Times Sq\nNEW YORK\nNEW YORK\n \nUnited States\n"^^xsd:string ; mdaas:registeredaddress "Suite 400\n333 Bay Street\nTORONTO\nONTARIO\nM5H 2R2\nCanada\n"^^xsd:string ; tr-common:haspermid " "^^xsd:string ; tr-fin:hasorganizationprimaryquote < ; tr-fin:hasprimaryinstrument < ; tr-org:hasactivitystatus tr-org:statusactive ; tr-org:hasheadquartersphonenumber " "^^xsd:string ; tr-org:hasholdingclassification tr-org:publiclyheld ; tr-org:hasipodate " T04:00:00Z"^^xsd:dateTime ; tr-org:haslei " UZND4C7B569"^^xsd:string ; tr-org:haslatestorganizationfoundeddate " T00:00:00Z"^^xsd:dateTime ; tr-org:hasprimarybusinesssector < ; tr-org:hasprimaryeconomicsector < ; tr-org:hasprimaryindustrygroup < ; tr-org:hasregisteredphonenumber " "^^xsd:string ; tr-org:isincorporatedin < ; fibo-be-le-cb:isdomiciledin < ; vcard:hasurl < ; vcard:organization-name "Thomson Reuters Corp"^^xsd:string.

5 LEI in Organization API response (Json-ld format) Request: "organization-name" : { "@id" : " "hasactivitystatus" : { "@id" : " "isdomiciledin" : { "@id" : " "haslei" : { "@id" : " "hasheadquartersphonenumber" : { "@id" : " "haspermid" : { "@id" : " "hasorganizationprimaryquote" : { "@id" : "

6 2. CHANGES IN API RESPONSES We ve made changes to the API responses of the following entities: 1. Industry 2. Asset class The changes includes adding prefixes to the following fields: Field Business classification code Comment Label broader Prefix trbc rdfs rdfs skos Examples - Industry lookup API Response Industry: Applied Resources PermId URI: Previous Industry Json-ld API response (was changed in this version) { "@id" : " "@type" : "trbc:businesssector", "tr-common:haspermid" : " ", "BusinessClassificationCode" : "5130", "comment" : "Producers of wood-based products and providers of related services, as well as manufacturers of paper and non-paper products, containers and packaging.", "label" : "Applied Resources", "broader" : " "@context" : { "broader" : { "@id" : " "label" : " "comment" : " "BusinessClassificationCode" : " "haspermid" : {

7 } } "@id" : " "tr-common" : " "rdfs" : " "xsd" : " "skos" : " "trbc" : " Industry Json-ld response (with the new prefixes) Request: { "@id" : " "@type" : "trbc:businesssector", "tr-common:haspermid" : " ", "trbc:businessclassificationcode" : "5130", "rdfs:comment" : "Producers of wood-based products and providers of related services, as well as manufacturers of paper and non-paper products, containers and packaging.", "rdfs:label" : "Applied Resources", "broader" : " "@context" : { "label" : { "@id" : " "comment" : { "@id" : " "broader" : { "@id" : " "BusinessClassificationCode" : { "@id" : " "haspermid" : { "@id" : " "tr-common" : " "rdfs" : " "xsd" : " "skos" : " "trbc" : } }

8 Example: Industry Turtle response (with the new prefixes) Request: tr-common: rdfs: xsd: skos: trbc: < < a trbc:businesssector ; rdfs:comment "Producers of wood-based products and providers of related services, as well as manufacturers of paper and non-paper products, containers and packaging."^^xsd:string ; rdfs:label "Applied Resources"^^xsd:string ; tr-common:haspermid " "^^xsd:string ; trbc:businessclassificationcode "5130"^^xsd:string ; skos:broader <

9 Examples Asset class lookup API Response Asset class: FX Butterflies PermId URI: Asset class Json-ld API response (was changed in this version) { } "@id" : " "@type" : "tr-fin:assetclass", "tr-common:haspermid" : " ", "comment" : "A butterfly is a combination of strangle and an ATM straddle (long strangle, short straddle or vice versa). The butterfly is typically quoted as a 25 or 10 delta, and the strangle has the appropriate delta.", "label" : "FX Butterflies", "broader" : " "@context" : { "broader" : { "@id" : " "label" : " "comment" : " "haspermid" : { "@id" : " "tr-common" : " "rdfs" : " "tr-fin" : " "xsd" : " "skos" : " }

10 Asset class Json-ld response (with the new prefixes) Request: { } "@id" : " "@type" : "tr-fin:assetclass", "tr-common:haspermid" : " ", "rdfs:comment" : "A butterfly is a combination of strangle and an ATM straddle (long strangle, short straddle or vice versa). The butterfly is typically quoted as a 25 or 10 delta, and the strangle has the appropriate delta.", "rdfs:label" : "FX Butterflies", "broader" : " "@context" : { "label" : { "@id" : " "comment" : { "@id" : " "broader" : { "@id" : " "haspermid" : { "@id" : " "tr-common" : " "rdfs" : " "tr-fin" : " "xsd" : " "skos" : " }

11 Asset class Turtle response (with the new prefixes) Request: tr-common: rdfs: tr-fin: xsd: skos: < < a tr-fin:assetclass ; rdfs:comment "A butterfly is a combination of strangle and an ATM straddle (long strangle, short straddle or vice versa). The butterfly is typically quoted as a 25 or 10 delta, and the strangle has the appropriate delta."^^xsd:string ; rdfs:label "FX Butterflies"^^xsd:string ; tr-common:haspermid " "^^xsd:string ; skos:broader <

12 3. GEONAME URL INSTEAD OF GEONAME CODE IN CURRENCY API RESPONSE You can now get the geoname URL instead of the geoname code of the countries in Is currency of and Is primary currency of fields. Example Geoname field in Currency lookup API Response Currency: Euro Currency PermID URI: Currency API with Geoname code (was changed in this version) { "@id" : " "@type" : "tr-currency:currency", "tr-common:haspermid" : "500111", "decimalplaces" : "2", "iscurrencyof" : [ "geonames: ", "geonames:597427", "geonames: ", "geonames: ", "geonames: ", "geonames:660013", "geonames:453733", "geonames: ", "geonames: ", "geonames: ", "geonames: ", "geonames:146669", "geonames: ", "geonames: ", "geona Currency API response (with Geoname URL) Request: { "@id" : " "@type" : "tr-currency:currency", "tr-common:haspermid" : "500111", "decimalplaces" : "2", "iscurrencyof" : [ " " " " " " " " " " " " "