Organisation
Thursday 5 January 2012, 14-17:00 CET (UTC+1)
Audio connection: Dial Belgium (toll) +32 (0)24015454 Participant PIN: 77057383#
Web connection: https://www.anywhereconference.com Web Login: 105382020 Participant PIN: 77057383#
Click here for further instructions on using the conference system.
Agenda
- European Commission: Vassilios Peristeras
- Core Person Task Force Chair: Greg Potterton
- Core Business Task Force Chair: Piotr Madziar
- Core Location Task Force co-chairs: Andrea Perego, Michael Lutz, Paul Smits
- Scribe: Niels van Hee, Débora Di Giacomo
- Editor: Phil Archer
Core Person
Agenda Item | Owner | Subject |
---|---|---|
1 | GP | Roll call/welcome new members |
2 | GP/PA | Adoption of minutes of previous meeting |
3 | PA | Brief discussion of the goals of the Core Quick presentation of evolving spec (Word doc, v0.03) |
4 | GP | Issue 137 are a person and his identity different concepts?Proposal: Close Issue 137 - yes, identity and natural person are different concepts and we're dealing with the latter |
5 | GP | Birth name (Issue 100)Proposal: Include this (see spec for text) |
6 | GP | Representation of birth place, birth country, birth date (Issue 101) Proposal: Include time and place of death details (noting that all fields are optional from a Core Voc point of view). No obvious proposal on inclusion of cause of death. |
7 | GP | Alternative names (Issue 102)Proposal: Include this (see spec for text that makes it clear that we're not talking about informal/familiar nick names) |
8 | PA |
Timeline to February Public Review 12 Jan
19 Jan
26 Jan
|
9 | SG | Signing of the Collaborator Licence Agreement |
Core Business
Agenda Item | Owner | Subject |
---|---|---|
1 | PM | Roll call/welcome new members |
2 | PM | Adoption of minutes of previous meeting |
3 | PM | Issue 149 Is there a controlled vocabulary for company status (active, in receivership etc.)?Proposal: keep 'status' field but allow any text as value. |
4 | PM | Issue 126 Identifiers. Lots of very useful input on this. EBR/REID system seems to provide exactly what's required but existing identifiers are preserved and remain important. Proposal: have specific fields for 'legal entity identifier and REID identifier, then additional field of "other identifier" that points to a separate concept that includes issuing authority as well as the ID itself. |
5 | PM | Issue 127 which links toFINANCIAL INSTITUTION REGISTER (European Banking Authority) Proposal: include a "hasLicenceFor" property which can be used to state that a given business has a licence to operate as a bank, to mine, export weapons etc. Proposal: include new field of "holds licence for" that links to a concept of a licence that has fields for issuing authority and licensed activity |
6 | PM | Issue 123 (alternative name). Lots of good discussion around this. Proposal: maintain field for alternative name but emphasise that, from a Core Vocabulary point of view, all fields are optional. In some countries, alternative names are not recognised and their provision may be seen as bad practice. |
7 | PA |
Timeline to February Public Review 12 Jan (aim to finalise conceptual model)
19 Jan (aim to ensure feedback received from registries)
26 Jan
|
Core Location
Agenda Item | Owner | Subject |
---|---|---|
1 | ML/AP | Roll call/welcome new members |
2 | ML/AP | Adoption of minutes of previous meeting |
3 | PA | Discussion of instance data and how it reflects (or not) the conceptual model |
4 | ML/AP | Finalising of concepts |
5 | ML/AP | Issue 178 Does/will ISO 19160-1 provide the necessary fields for an address? Should we not use INSPIRE? |
6 | ML/AP | Issue 177 - Identification of location by textual description. |
7 | PA |
Timeline to February Public Review 12 Jan (aim to finalise conceptual model including properties)
19 Jan (aim is to have advanced draft of spec)
26 Jan
|
Meeting Minutes
CV WG Virtual Meeting 2012.01.05 - Minutes - v0.02.pdf
Meeting Documents
INSPIRE_DataSpecification_AD_v3.0.1.pdf
Nature of documentation: Conference-seminar-meeting proceeding
Categorisation
Type of document
Document
Login or
create an account to comment.