文档介绍：Functional Requirements
A presentation to the final InterParty Seminar
The Hague
13 June 2003
David Martin
InterParty
Functional requirements
Essential first step, alongside analysis of existing schemes
Undertaken, therefore, during the first and second quarters of the project
Leading to a statement of the minimum functional requirements that an work would need to support
No preconceptions at this stage as to how they should be delivered
As it turned out, a process of seeking to simplify as far as possible (but no further)
InterParty
Some working hypotheses
InterParty is an alliance of independent bodies - InterParty Members or IPMs
Each maintains its own identification and metadata system in its own domain
IPMs participate because they see benefits
From being able to see and mon Metadata from other IPMs: data sharing
municating between their own domain and those of other (selected) IPMs by mapping across domains: mon Metadata includes
A certain level of metadata about “public identities”
Assertions made about relationships between public identities in different domains
InterParty
Party and public identity
Party
An individual anisation involved in the creation or dissemination of intellectual property
Public Identity
An identity that is associated with and is used publicly by a party (or a group of parties)
Public Identity Identifier - PIDI
An identifier assigned to a public identity by an IPM and designed to be unique within the domain of that IPM: a PIDI may be a number, or it may be a controlled form of name (eg in a library name authority system)
InterParty Link
An assertion about a relationship between two PIDIs in two different IPM domains - ie, between two public identities
InterParty
Party and public identity
Party
Sensitive
Not
publicly known
Publicly known
“Party” metadata
Public Identity
InterParty is concerned with “public identities” not “persons” or “parties”
InterParty
InterParty Links
PIDI
NSC: 876X54
PIDI
NSA:123456
is
is