User profile management: reference model and web services implementation
Bibliographic record
Abstract
A user profile is a structured representation of an individual user's characteristics and personal preferences with respect to a software application or computing device. As the variety and complexity of applications and mobile devices increase, there is a growing need and interest in personalisation. This necessitates methods of managing user profile content such that it can be accessed, updated and potentially shared over communication networks. This research investigates User Profile Management (UPM) as a network-based service for managing user profile content. The major requirements for a good UPM service are defined. A reference model is proposed that includes an architecture, profile data schema, a protocol, basic command functions and security mechanisms. A prototype UPM service and four client applications based on the reference model are developed using Java and web services technologies. Scenarios are constructed to demonstrate the value of the UPM reference model and the web services implementation. We conclude that the proposed reference model provides a solid foundation for developing UPM services and that web services technologies are suitable for implementing the reference model in a distributed network environment.
Fetched live from OpenAlex and de-inverted. Abstracts are not stored in this database: the inverted indexes are 8.6 GB of the frame’s 9.3 GB of text, and the host has 13 GB free.
How this classification was reachedexpand
Full frame machine prediction
Teacher imitationNot calibrated prevalence, not ground truth. Human validation pending. The Gemma side is a direct model label for every work in the frame, read from the title-only record. The Codex side is a classifier learned from the 10,348 direct Codex labels and calibrated to design-weighted sample rates; fields without enough sample support carry no Codex call. Candidate is the union of the two sides; consensus is their intersection. These outputs are machine_predicted_unvalidated and are not human labels.
Distilled classifier scores by category (both heads)
| Category | Codex | Gemma |
|---|---|---|
| Metaresearch | 0.007 | 0.013 |
| Meta-epidemiology (narrow) | 0.001 | 0.001 |
| Meta-epidemiology (broad) | 0.001 | 0.001 |
| Bibliometrics | 0.002 | 0.003 |
| Science and technology studies | 0.001 | 0.001 |
| Scholarly communication | 0.006 | 0.008 |
| Open science | 0.005 | 0.002 |
| Research integrity | 0.003 | 0.002 |
| Insufficient payload (model declined to judge) | 0.004 | 0.004 |
Machine scores (provisional)
The two teacher heads of the student model, read on this work. A score orders the frame for review; it never asserts a category, and the validation status ships verbatim with every row.
Baseline scores from an immature model (maturity gate not passed, 7 training rounds). Scores rank; they never assert a category.
score_only:v0-immature-baseline · verbatim from the scoring run: score_only means the number may rank works, and no category label ships from itClassification
machine, unvalidatedMachine predicted; a candidate call from one source (direct Gemma or distilled Codex), not a consensus.
How this classification was reached, model by model and score by score, is at the end of the page under "How this classification was reached".