(almost) anything is a resource

Registered by Tomás Vírseda García

Vazaar should be able to handle as many resources as user can imagine. But what is a resource? Summing up, a resource is anything you can reference with a URI. Check RFC 3986 (URI Generic Syntax):

"""
This specification does not limit the scope of what might be a resource; rather, the term 'resource' is used in a general sense for whatever might be identified by a URI. Familiar examples include an electronic document, an image, a source of information with a consistent purpose (e.g., "today's weather report for Los Angeles"), a service (e.g., an HTTP-to-SMS gateway), and a collection of other resources. A resource is not necessarily accessible via the Internet; e.g., human beings, corporations, and bound books in a library can also be resources. Likewise, abstract concepts can be resources, such as the operators and operands of a mathematical equation, the types of a relationship (e.g., "parent" or "employee"), or numeric values (e.g., zero, one, and infinity).
"""

Blueprint information

Status:
Started
Approver:
None
Priority:
Essential
Drafter:
None
Direction:
Needs approval
Assignee:
None
Definition:
Drafting
Series goal:
None
Implementation:
Good progress
Milestone target:
None
Started by
Tomás Vírseda García

Related branches

Sprints

Whiteboard

Until now, Vazaar can handle these resources:

   - files and directories in a local file system (images, sound, video)
   - any text-based content from clipboard
   - collections
   - remote resources (webpages, ftp sites)
   - notes: simple text-based notes
   - projects,
   - organizations,
   - contacts,
   - tasks

Common metadata for all resources:

- RDF.type: a specific nepomuk resource class
- NAO['created']: resource created date in Vazaar
- NIE['title']: resource title
- NIE['mimeType']: resource mimetype
- NFO['fileUrl']: URL of the file. It points at the location of the file. In cases where creating a simple file:// or http:// URL for a file is difficult (e.g. for files inside compressed archives) the applications are encouraged to use conventions defined by Apache Commons VFS Project at http://jakarta.apache.org/commons/vfs/filesystems.html.

Optional:
- NAO['lastModified']: resource last modfied date in Vazaar

Relations:
- NAO['hasTag']

(?)

Work Items

This blueprint contains Public information 
Everyone can see this information.

Subscribers

No subscribers.