The document discusses master data management in the city of Gothenburg. It describes challenges around managing structured and unstructured data from multiple systems. It then demonstrates a pilot project that uses semantic standards, models and open vocabularies to link and query master data. Entities like people, organizations, locations and services are modeled. The pilot shows how data can be accessed through a SPARQL endpoint or API to enable interoperability.

1. Master Data…
In the city service
Models, challenges, effects and solutions

2. Information management @ Göteborg
2HÅLLBAR STAD – ÖPPEN FÖR VÄRLDEN

3. 3HÅLLBAR STAD – ÖPPEN FÖR VÄRLDEN

4. 4
Standards, Domain, Exchange,
interoperability
Standard
Domain
Exchange

5. Models
5HÅLLBAR STAD – ÖPPEN FÖR VÄRLDEN

6. ISA2
Core Vocabularies
Jurisdiction
+ name: text
+ id: URI
Geometry
+ wkt: string
+ lat: string
+ long: string
+ xmlGeometry: XML
Code
+ content: string
+ list: string
+ list agency: string
+ list version: XML
ConceptDocumentImageObject
«abstract»
Alternative Address Representation
+ addressID: string
Geometry
(alternative representation)
+ coordinates: CoordinateList
+ crs: CRSIdentifier
+ geometryType: Geometry Type: [0 .. 1]
Formal Framework
+ name: literal
+ identifier: identifier
ChangeEvent
Agent
Opening Hours
Specification
+ dayOfWeek: URI
+ validForm: DateTime
+ validThrough: DateTime
Location
+ geographicName: string
+ geographicIdentifier: URI
Person
+ fullName: string
+ familyName: string
+ givenName: string
+ patronymicName: string
+ alternativeName: string
+ gender: code
+ birthName: string
+ DateOfBirth: dateTime
+ DateOfDeath: dateTime
FoundationEvent
Organization
Organizational Unit
Contact Point
+ hasEmail: literal
+ hasTelephone: literal
+ openingHours: structured literal
Administrative
Territorial Units
Licence
Legal Entity
+ legalName: text [0..*]
+ alternativeName: text [0..*]
Address
+ fullAddress: string
+ poBox: string
+ thoroughfare: string
+ locatorDesignator: string
+ locatorName: string
+ addressArea: string
+ postName: string
+ adminUnitL2: string
+ adminUnitL1: string
+ postCode: string
+ adressID: string
Identifier
+ identifier: string [1 .. 1]
+ identifierType: string [0 .. 1]
+ DatOflssue: dateTime [0 .. 1]
+ issuingAuthority: string [0 .. 1]
+ issuingAuthorityUri: URI [0 .. 1]
+countryOfBirth
+ residency
+ identifies
+ change
+has
FormalFramework
+implements
+change
+ heldBy
+ availabilityRestriction
+ prev
+ next
+ memberOf
+ hasMember
+ unitOf
+ hasUnit
+ resultedFrom, changedBy
+ hasSubOrganization
+ subOrganizationOf
+ holdsLicence
0..1
0..1
+ legalIdentifier
+ identifier
+identifies
+ companyType 0..1
+ geometry
+spatial
+address
+logo
+homepage
+purpose,classification
0..1+registeredAddress
+companyStatus0..1
+ companyActivity 0..1
+ change
+ originalOrganization, resultingOrganization
+ identifier
+ citizenship
+ geometry
+ geometry
+ address
+countryOfDeath
+placeOfBirth
+placeOfDeath
Public Organization
+ preferredLabel: literal
+ alternativeLabel: literal
+ identifier: literal (typed)
+ description: literal
The Core Vocabularies have been developed under the ISA² Programme of the European
Commission, namely the action “Improving semantic interoperability”. ISA² is a EUR 131 million
programme supporting the modernisation of public administrations in Europe through the
development of eGovernment solutions. More than 20 solutions are already available, with more to
come soon. All solutions are open source and available free of charge to any interested public
administration in Europe.
Interoperability for Public Administration
(ISA2)
6HÅLLBAR STAD – ÖPPEN FÖR VÄRLDEN

7. Public Service
7HÅLLBAR STAD – ÖPPEN FÖR VÄRLDEN

8. Master Classes
8HÅLLBAR STAD – ÖPPEN FÖR VÄRLDEN
Service
cpsv:provides
Organization
Location
Organizational Unit
dcterms:spatial
Site
org:hasSite
locn:location
dcterms:isPartOf
cpsv:related
cpsv:requires
Person
org:subOrganizationOf
org:unitOf
org:hasMembership
org:role
cpsv:hasCompetentAuthority

9. Definitions (eng)
9HÅLLBAR STAD – ÖPPEN FÖR VÄRLDEN
• Master data represents the business objects which are agreed on and
shared across the enterprise. It can cover relatively static reference
data, transactional, unstructured, analytical, hierarchical and meta data
• Semantics is the linguistic and philosophical study of meaning, in
language, programming languages, formal logics, and semiotics. It is
concerned with the relationship between signifiers—like words,
phrases, signs, and symbols—and what they stand for, their denotation
• Information governance, or IG, is the management of information at
an organization. Information governance balances the use and
security of information. Information governance helps with legal
compliance, operational transparency, and reducing expenditures
associated with legal discovery

10. Challenges

11. SISO

12. Landfill

13. Data today L
13HÅLLBAR STAD – ÖPPEN FÖR VÄRLDEN
Structured and unstructured data
RDBS
Agresso
Personec
Notes
ServiceNow
ISIM

14. 14HÅLLBAR STAD – ÖPPEN FÖR VÄRLDEN

15. 15HÅLLBAR STAD – ÖPPEN FÖR VÄRLDEN

16. Demonstration of the pilot
16HÅLLBAR STAD – ÖPPEN FÖR VÄRLDEN

17. Demo of Gothenburg pilot
● Terms, terminologies, and reference data (SKOS ,W3C, Simple
Knowledge Organising System)
○ Code System, Taxonomies, Glossaries, Thesauri, Ontologies
○ Ex. SNI code, Företagsform, AID-code, Befattningar, Integrated
Public Service Vocab (ISPV)
● Workbench, manage object (with properties) and domain-models (
RDF-scheman, alt Web Ontologier, OWL)
○ ISA2 Core Vocabularies, W3C Organisation Ontology, Location,
Inspire Spatial Data etc.
● Quality data through use of open standards, and models reaching
interoperability, and effective information management.

18. The model
Person
Medlemskap
Organisation
personName
Site
orgName
siteName
foaf:name
skos:prefLabel
skos:prefLab
el
org:organisation
org:hasSite
org:hasMembership
foaf:Personrdf:type

19. Terminologies (SKOS)
Reference data
(bolagsverket)
företagsform
Glossaries, code systems
Befattning (SKL)
Open standards, taxonomies.
thesauri

20. Models and entities
● Master data entiteties from standards as
ISA2 core vocabularies
● Person (individuals)
● Organisation (entiteties with vat.nb)
○ Enhet (OrgUnit)
● Place (address alt geo-code)
● Location, spatial area
● Service, (internal/external) [CPSV-AP]

21. Person
● A model to cover all type of person types.
● A individual have several facets (member
of staff, citizen, pupil, politician etc)
● A member of staff might have multi
employments, and roles.
● Word identification code (AID-code) and
postions Befattningar code with
terminologies from www.SKL.se

22. Organisation
● Organisation is the super class that
define any organisation, that the
municipality interact with.
● Organisation is classificied with
företagsform, and SNI-code (NACE)
● All orgnisations are linked to organistional
unites. There are also inter-linking
betwenn organisation in networks.
● Göteborgs Stad is the top node and
classifice as #kommun / municipality ;-)

23. Enhet (orgUnit)
● A municipality have a multitude of
organising principles, as governance,
political steering, city parts, departments,
sectors, areas, and groups
● The organisation have many hierarchical
levels, as well as links into a network
(graph)
● Org Units provision many serviuces
● A Unit can also be acting out of many
places.

24. Place and area
● Place is either a address, or a
geographical position where a Unit
provision services.
● All places are part spatial areas, or
geographical locations, as postal code,
city part, area etc..
● Locations is managed with the cities GIS-
systems, with unique identifiers and
spatial services.

25. Service
● Tjänst / Service kan antingen vara intern
eller extern (riktad mot ex invånare)
● Klassificering och beskrivning av service
är tillämpning av CPSV-AP
● Instansiering av en tjänst, kan antingen
vara virtuell (e-tjänster) eller fysisk.
● Service ingår i olika hierarkier av service
förpackningar / erbjudanden.
● Processer, rutiner och arbetssätt för att
genomföra en service sker i olika
verksamhetsstödjande system.

26. Utility of Master Data
● Information management with master data platform:
○ Asynchronous (enterprise service bus) via
informations contrakt v using the integration engine
○ Syncron via RestfulAPI eller Queries
○ Visualisation in a graph
● Independent if the actor is another system or an
individual, the service opens up to many ways to
interact, and re-use the information in
interoperatible manner.

27. API alternative
Alternative 1 – Linked data + Solr
● Each response is a “metadata record”.
● Connecting the entiteties, either via Solr search or links
● Access control respected
Alternative 2 – graph search (SPARQL)
● Express specific statements
● Connect via relations and entities
● Access control not respected, only public information

28. Alt 1 - Linked data
In general:
BAS/{contextId}/metadata/{entryId}
Get metadata, that describes a entity in ex. Person in
Turtle format:
https://goteborg.entryscape.net/store/27/metadata/5?
format=text/turtle

30. Alt 1 cont. - Solr
In general:
BAS/search?type=solr&query=uttryck
Exemple:
● Search for entities that are type person
● Limit to one “context”
BAS/search?type=solr&query=rdfType:<URI1>+AND+context:<URI2>
URI:s have to be urlencodade, below search in context 27
https://goteborg.entryscape.net/store/search?type=solr&query
=rdfType:http%5C%3A%2F%2Fxmlns.com%2Ffoaf%2F0.1%2FPerson+AND
+context:https%5C%3A%2F%2Fgoteborg.entryscape.net%2Fstore%2F
27

32. Alt 2 - SPARQL
SELECT DISTINCT ?personNamn ?orgNamn ?siteNamn WHERE {
GRAPH <https://goteborg.entryscape.net/store/27> {
?p rdf:type foaf:Person ;
foaf:name ?personNamn ;
org:hasMembership ?m .
?m org:organization ?o .
}
?o skos:prefLabel ?orgNamn ;
org:hasSite ?s .
?s skos:prefLabel ?siteNamn .
}
LIMIT 10

33. SPARQL – Query pattern
?p rdf:type foaf:Person ; //Search for persons (?p)
foaf:name ?personNamn ; //that have a name (?personName)
org:hasMembership ?m . //that are member of (?m)
?m org:organization ?o . //In a organisation (?o)
?o skos:prefLabel ?orgNamn ; //that has a name (?orgNamn)
org:hasSite ?s . //that exist in a place (?s)
?s skos:prefLabel ?siteNamn . //that has a name (?siteNamn)

34. SPARQL – Limit to a graph
GRAPH <https://goteborg.entryscape.net/store/27> {
… //En massa graf påståenden
}
// Limit to the named graph “27”

36. Graph visualisation

38. Future data interoperability vision
38HÅLLBAR STAD – ÖPPEN FÖR VÄRLDEN
Structured and unstructured data
RDBS
Agresso
Personec
Notes
ServiceNow
ISIM

39. Information Lifecycle
• Different levels & granularities along each data/information lifecycle
• Framework needed for IG & the different roles/levels
Creator/author
Owner
User
Administrator
Information Steward
Department/Process owner
IG Dteering Group

40. Contact: Fredric.Landqvist@intraservice.goteborg.se
Fredric.landqvist@findwise.com