Notice: this Wiki will be going read only early in 2024 and edits will no longer be possible. Please see: https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/wikis/Wiki-shutdown-plan for the plan.
Difference between revisions of "Higgins 2.0"
m |
|||
| (30 intermediate revisions by the same user not shown) | |||
| Line 1: | Line 1: | ||
| − | {{#eclipseproject:technology.higgins|eclipse_custom_style.css}} | + | {{#eclipseproject:technology.higgins|eclipse_custom_style.css}} |
| − | Higgins 2.0 is the new code base to implement that | + | Higgins 2.0 is the new code base to implement a PDS. A PDS is a cloud-based service that works on behalf of you, the individual. It gives you a central point of control for personal information about a you. Things like your interests, contact information, addresses, profiles, affiliations, friends, and so on. A PDS is a place where you establish bi-directional data flows between external businesses and your PDS. Or between your friends' PDS and your PDS. |
| − | + | [[Image:Higgins2.0toplevel.png|center]] | |
| − | + | At 50,000 feet there are four major conceptual pieces: | |
| − | + | *'''PDS:''' Back-end services to support the web client | |
| − | + | *'''ADS:''' An RDF/OWL "quad" store holding the user's data described using the vocabularies of the [[Persona Data Model 2.0]]. It exposes these data to the Portal and the HBX (see below) via an HTTP/Comet messaging interface. It also exposes the data via a SPARQL endpoint for server-to-server integrations. | |
| − | *''' | + | *'''Client:''' Web HTML/JavaScript client UI. Lets the user see and edit attributes. |
| − | *''' | + | |
*'''Higgins Browser Extension (HBX):''' Loads JavaScript programs from the PDS and runs them within the browser. It also provides an API that allows it to read and write to the PDS. This locally running code could, for example scrape data from a web page and store it in the PDS. | *'''Higgins Browser Extension (HBX):''' Loads JavaScript programs from the PDS and runs them within the browser. It also provides an API that allows it to read and write to the PDS. This locally running code could, for example scrape data from a web page and store it in the PDS. | ||
| − | + | == Details == | |
| − | + | * [[PDS_Architecture | Architecture]] - top-level components | |
| − | + | * [[Persona Data Model 2.0 | Data Model]] - main persona vocabulary and supporting sub-vocabularies | |
| − | + | * [[Build Instructions]] - source code & build instructions | |
| − | + | * [[PDS Vision | Vision]] - long term goals; big picture | |
| + | * [[PDS Use Cases | Use Cases]] - most important use cases | ||
| + | * [[PDS UI]] - a few notes about the structure of the PDS app | ||
| + | * [https://bugs.eclipse.org/bugs/enter_bug.cgi?product=Higgins Enter a bug] | ||
| + | * [https://bugs.eclipse.org/bugs/query.cgi?product=Higgins Search for a bug] | ||
| + | * [https://dev.eclipse.org/mailman/listinfo/higgins-dev higgins-dev], [http://dev.eclipse.org/mhonarc/lists/higgins-dev/maillist.html archive] - developer list | ||
| + | * [https://dev.eclipse.org/mailman/listinfo/higgins-announce higgins-announce], [http://dev.eclipse.org/mhonarc/lists/higgins-announce/maillist.html archive] - announcement list, very low volume | ||
| − | == | + | == Milestones == |
| + | * [[Higgins 2.0M1]] - first 2.0 milestone (done) | ||
| + | * [[Higgins 2.0M2]] - under development | ||
| − | |||
| − | |||
[[Category:Higgins_2]] | [[Category:Higgins_2]] | ||
Latest revision as of 16:23, 18 January 2014
{{#eclipseproject:technology.higgins|eclipse_custom_style.css}}
Higgins 2.0 is the new code base to implement a PDS. A PDS is a cloud-based service that works on behalf of you, the individual. It gives you a central point of control for personal information about a you. Things like your interests, contact information, addresses, profiles, affiliations, friends, and so on. A PDS is a place where you establish bi-directional data flows between external businesses and your PDS. Or between your friends' PDS and your PDS.
At 50,000 feet there are four major conceptual pieces:
- PDS: Back-end services to support the web client
- ADS: An RDF/OWL "quad" store holding the user's data described using the vocabularies of the Persona Data Model 2.0. It exposes these data to the Portal and the HBX (see below) via an HTTP/Comet messaging interface. It also exposes the data via a SPARQL endpoint for server-to-server integrations.
- Client: Web HTML/JavaScript client UI. Lets the user see and edit attributes.
- Higgins Browser Extension (HBX): Loads JavaScript programs from the PDS and runs them within the browser. It also provides an API that allows it to read and write to the PDS. This locally running code could, for example scrape data from a web page and store it in the PDS.
Details
- Architecture - top-level components
- Data Model - main persona vocabulary and supporting sub-vocabularies
- Build Instructions - source code & build instructions
- Vision - long term goals; big picture
- Use Cases - most important use cases
- PDS UI - a few notes about the structure of the PDS app
- Enter a bug
- Search for a bug
- higgins-dev, archive - developer list
- higgins-announce, archive - announcement list, very low volume
Milestones
- Higgins 2.0M1 - first 2.0 milestone (done)
- Higgins 2.0M2 - under development