Mapping between core datamodels (ISA vs. IMI)	

Hideaki Takeda
National Institute of Informatics
takeda@nii.ac.jp	

Core vocabulary v2.2	
• Published on Feb.3 2015
• 48 core class terms– person, address, facility, location, date, …

• 206 core property terms– name of person, birth date, birth country, …

• Multi format– rdf schema, xml schemaand documents for human	

http://imi.ipa.go.jp/ns/core/2/	Meaning of mapping between
core data models	• Semantic mapping– Showing relationship between elements
which are semantically equivalent– Syntactical mapping can be generated byusing Semantic mapping as a guide• Syntactical mapping– Data can be transferred through the mappingMapping!

The result of mapping	• Has exact match: 30• Has close match: 7• Has broad match: 8• Has narrow match: 11• Has related match: 8• Has no match: 46	

Interpretation of “sematic mapping”	
• Two views– Conceptual equivalenceReal World	• Extension is the same
– Ex. Person• Most of classes, some properties• Criteria

Data World	– If extension is concrete, how strict range of extension isconsidered– If extension is abstract, how equivalence is interpreted– Data equivalence• Representation as data is the same in semantics– Ex. AddressPostCode• Most of properties, some classes• Criteria– How strict data structure (including type and value range) is
considered– cf. Syntactical mapping	Has exact match	
• Apparent equivalence	– Conceptual equivalence	• Well-known common
concepts (class andproperties)	

– Data equivalence	
• Common ranges	
• Data types	

– Simple cases fordifferences in structure
can be described 	• A = B.C	AddressAddressID	Link	Has exact match	

IMI	

ic:ID	

AddressFullAddress	Link	

Has exact match	

IMI	

ic:表記	

AddressPostCode	Link	

Has exact match	

IMI	

ic:郵便番号	

Agent	Link	Has exact match	

IMI	

ic:実体型	

Code	Link	

Has exact match	

IMI	

ic:コード型	

CodeContent	

Link	

Has exact match	

IMI	

ic:識別値	

CodeList	

Link	

Has exact match	

IMI	

ic:コード種別.名称	

DateTime	

Link	

Has exact match	

IMI	

xsd:dateTime	

Geometry	Link	Has exact match	

IMI	

ic:座標型	

GeometryCRS	Link	

Has exact match	

IMI	

ic:座標参照系	

GeometryType	Link	

Has exact match	

IMI	

ic:座標データ書式	

Identifier	Link	Has exact match	

IMI	ic:ID型	

IdentifierIdentifier	Link	Has exact match	

IMI	

ic:識別値	

LegalEntity	

Link	

Has exact match	

IMI	

ic:法人型	

LegalEntityCompanyType	Link	

Has exact match	

IMI	

ic:組織種別	LegalEntityIdentifier	Link	Has exact match	

IMI	

ic:ID	

Location	Link	Has exact match	

IMI	

ic:場所型	

LocationGeometry	Link	

Has exact match	

IMI	

ic:地理座標	

Person	Link	

Has exact match	

IMI	

ic:人型	

PersonAddress	Link	

Has exact match	

IMI	

ic:住所	

PersonCountryOfBirth	Link	Has exact match	

IMI	

ic:出生国	PersonDateOfBirth	Link	Has exact match	

IMI	

ic:生年月日	PersonDateOfDeath	

Link	Has exact match	

IMI	ic:死亡年月日	

PersonFamilyName	Link	

Has exact match	

IMI	

ic:氏名.姓	

PersonFullName	Link	

Has exact match	

IMI	

ic:氏名.姓名	

PersonGender	Link	Has exact match	

IMI	

ic:性別コード	PersonGivenName	Link	

Has exact match	

IMI	

ic:氏名.名	String	

Link	

Has exact match	

IMI	

xsd:string	

Text	

Link	

Has exact match	

IMI	

xsd:string	

URI	

Link	

Has exact match	

IMI	

xsd:anyURI	Has close match	
• Relaxation in two views– Conceptual equivalence• Range of extension is not exactly the same• ex) address in between Europe and Japan– Data equivalence• Range of value is not the same• Ex) AddressAdminUint1 <-> ic:国 (country)	
Address	Link	

Has close match	

IMI	

ic:住所型	

AddressAdminUnitL1	

Link	

Has close match	

IMI	ic:国	AddressAdminUnitL2	

Link	

Has close match	

IMI	

ic:都道府県	

GeometryCoordinates	

Link	

Has close match	

IMI	

ic:座標データ	

LegalEntityCompanyActivity	

Link	

Has close match	

IMI	

ic:事業種目	

LocationAddress	Link	

Has close match	

IMI	

ic:住所	LocationGeographicIdentifier	Link	

Has close match	

IMI	

ic:地理識別子	

Has broad match	• Interpretation of range– Conceptual equivalence• Class hierarchy– Data equivalence• Range subsumption• Structural subsumption	
IdentifierIssuingAuthorityURI	 Link	 Has broad match	
IMI	 ic:ID体系.URI	
LegalEntityAddress	

Link	 Has broad match	
IMI	 ic:住所	

LegalEntityLegalName	

Link	 Has broad match	
IMI	 ic:名称.表記	

LegalEntityRegisteredAddress	
Link	 Has broad match	
IMI	 ic:住所	
LocationGeographicName	

Link	 Has broad match	
IMI	 ic:名称	

PersonAlternativeName	

Link	 Has broad match	
IMI	 ic:氏名.姓名	

PersonBirthName	

Link	 Has broad match	
IMI	 ic:氏名.姓名	

PersonIdentifier	

Link	 Has broad match	
IMI	 ic:ID	

住所	The range of ic:ID種別 is ic:ID体系型 which
is a class whose property ic:URIcorresponds this property. But it means a
URI either for the issuer or ID system.		

It represents a name in Japanese. Ic:名称.	
ローマ字表記 is a name in roman alfabet	
It is exact match if the value of ic:住所.種	別 should be "登記住所".	
名称	Compatible	A person has multiple names '種別' of '氏
名' shows the category of the name.	
A person has multiple names '種別' of '氏
名' shows the category of the name.		

Has narrow match	• Multiple correspondence	

AddressAddressArea	Link	Has narrow match	IMI	ic:町名	

AddressAddressArea	

Link	

Has narrow match	

IMI	ic:丁目	

AddressAddressArea	

Link	

Has narrow match	

IMI	ic:番地補足	

AddressAddressArea	

Link	

Has narrow match	

IMI	ic:番地	

AddressAddressArea	

Link	

Has narrow match	

IMI	

ic:号	

AddressLocatorDesignator	

Link	

Has narrow match	

IMI	

ic:ビル番号	AddressLocatorDesignator	

Link	

Has narrow match	

IMI	

ic:部屋番号	AddressLocatorName	Link	

Has narrow match	

IMI	

ic:ビル名	AddressPostName	Link	

Has narrow match	

IMI	

ic:市区町村	

AddressPostName	Link	

Has narrow match	

IMI	

ic:区	

PersonPlaceOfBirth	Link	Has narrow match	

IMI	ic:出生地	

Has related match	• Complicated relationship– It can be matched with some conditions• Ex) structure is different• Vague relationship– Difficult to explain the relationship in thescheme	

Has no match	• No conceptual equivalence	

IMI	

PublicService	
PublicServiceChannel	
PublicServiceDescription	PublicServiceFollows	
PublicServiceHomepage	
PublicServiceInput	

Link	
Link	
Link	
Link	
Link	
Link	

Has no match	Has no match	Has no match	Has no match	Has no match	Has no match	

IMI	
IMI	
IMI	
IMI	
IMI	IMI	

IMI	

PublicServiceLanguage	Link	Has no match	

IMI	

Has no match	

IMI	

Has no match	

IMI	

Link	

Has no match	

IMI	

PublicServiceName	PublicServicePhysicallyAvailableAt	
PublicServiceProduces	

Link	
Link	
Link	

Has no match	Has no match	Has no match	

IMI	
IMI	
IMI	

PublicServiceRelated	

Link	

Has no match	

IMI	

IdentifierType	Link	

Has no match	

IMI	

Input	
InputDescription	

Link	
Link	

Has no match	Has no match	

IMI	
IMI	

PublicServiceRequires	Link	

Has no match	

IMI	

InputName	Link	

Has no match	

IMI	

PublicServiceSpatial	Link	Has no match	

IMI	

InputType	
Jurisdiction	
LegalEntityAlternativeName	LegalEntityLegalIdentifier	
Output	

Link	
Link	
Link	
Link	
Link	

Has no match	Has no match	Has no match	Has no match	Has no match	

IMI	
IMI	
IMI	
IMI	
IMI	

PublicServiceTemporal	

Link	

Has no match	

IMI	

OutputDescription	

Link	

Has no match	

IMI	

PublicServiceType	
Rule	
RuleCreator	

Link	
Link	
Link	

Has no match	Has no match	Has no match	

IMI	
IMI	
IMI	

RuleImplements	

Link	

Has no match	

IMI	

OutputName	OutputType	PeriodOfTime	
PersonCitizenship	
PersonCountryOfDeath	PersonPatronymicName	
PersonPlaceOfDeath	PersonResidency	

Link	
Link	
Link	
Link	
Link	
Link	
Link	
Link	

Has no match	Has no match	Has no match	Has no match	Has no match	Has no match	Has no match	Has no match	

IMI	
IMI	
IMI	
IMI	
IMI	
IMI	
IMI	
IMI	

TextContent	

Link	

Has no match	

IMI	

TextLanguage	Link	Has no match	

IMI	

AddressThoroughfare	Link	

Has no match	

IMI	

AgentPlaysRole	Link	

Has no match	

IMI	

AgentProvides	
Channel	

Link	
Link	

Has no match	Has no match	

IMI	
IMI	

CodeListVersion	

Link	

Has no match	FormalFramework	Link	

Has no match	FormalFrameworkCreator	

Link	

FormalFrameworkRelated	Link	

IdentifierIssueDate	Summary	• Two views for mapping are not consistent– Need for specifying which view is used to map– Mapping for data type may be separated?

• Conditions for mapping type should be clarified– Exact matching vs. close matching– Exact matching vs. broad (narrow) matching• More detailed languages are needed to describe
complicated relationship (OWL?)• Another central core model is needed???