Changes between Version 2 and Version 3 of URIScheme


Ignore:
Timestamp:
05/26/09 09:09:56 (7 years ago)
Author:
bdarcus
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • URIScheme

    v2 v3  
    1515Suggested scheme, then: 
    1616 
    17  * users [base]/user/[user name or id] 
    18  * groups [base]/group/[group name slug or id] 
    19  * libraries [base]/[user or group]/library 
    20  * collections [base]/collection/[collection id] 
    21  * notes [base]/note/[note id] 
     17 * users - [base]/user/[user name or id] 
     18 * groups - [base]/group/[group name slug or id] 
     19 * libraries - [base]/[user or group]/library 
     20 * collections - [base]/collection/[collection id] 
     21 * notes - [base]/note/[note id] 
    2222 * attachments - probably not needed (can be a blank node in the RDF?) 
    23  * items 
    2423 
     24= On Zotero Items = 
     25 
     26The big question is how to model and identify the items, and thus relate them to the above resources. Treating them as effectively bookmarks about related resources seems to fit best, as it allows specifically user-related content (notes and tags, say) to be separated from the metadata about the source per se. That may suggest; 
     27 
     28 * items - [base]/user/[user name or id]/[item id] 
     29 
     30IF there's value in Zotero minting new URIs for all the resource these items reference (e.g. the sources), then maybe: 
     31 
     32 * sources - [base]/sources/[item id] 
     33 
     34If Zotero were to do this, it'd be important to include owl:sameAs references to the primary source URIs. In any case, before choosing a particular route, I'd like to suggest posting a note on the BIBO list to see if people there have any thoughts.