Digital assets

I'm a new member of the working group.   I joined this group as I'm working
on solutions for Alzheimers disease and seeking to address the needs for
providing useful memory queues to help with coping.  The data represented
in this regard, would serve to rekindle memories (IE provide a way to help
associate and remember events, facts, images, recordings, etc) for
Alzheimers sufferers.

The ultimate goal would be provide a means to catalog any kind of digital
data as cursory steps to the development of all sorts of technologies and
memory aid solutions that could be developed; provided that archives of
digital assets could yield such information in a searchable semantic way.

So simply, I would like to develop a way to offer schema.org friendly
digital assets stored in repositories on the web.  All of the content needs
to be crawl-able and index-able.

I have had a chance to review the proposals presented to date.  I do like
the second proposal as it lends nicely to adoption into the schema.org
graph.

After reading the proposals, its seems clear that the requirements for
digital assets have not been addressed as far as I can tell in regards to:

   - Digital Access Rights (authentication and authorization)... basically
   the same requirements necessary for access permission of web resources for
   securing any other type of content... think acess tokens (OAuth, SAML, or
   OpenID) as well as claims to control access.
   - authority -  the establishment of the archived content's nature as
   authoritative (content owners/official record bearer repositories) versus
   unauthoritative (available collections that serve as alternate repositories
   of the same content)
   - related content archives - collection of one or more other locations
   of similar or related content
   - trustworthiness (the accuracy of the content) - perhaps where the
   content originally came from
   - urls - collection of one or more locations of the online repos (CDNs)
   - tags - useful keyword identifiers that would promote filtering
   abilities  and allow data ETL into searchable data stores

These are just some initial thoughts, but I would like to bring them up for
discussion.  Perhaps the architypes schema may not be the best fit for this
kind of need... but it appears to be the most closely matched in terms of
relevance.

I appreciate all feedback.

Regards,

Mark Chipman