Wilbert et al (apologies for cross-posting)
I have not entered a statement in the spreadsheet as requested as I
would rather this was discussed with the relevant communities first.
What seems to be missing (and I am afraid that the density of
language makes a little unclear) are references to issues of subject
consent.
This is particularly an issue in domains where materials may contain
images of, or other kinds of references to, individuals from whom
informed and fairly precise consent is required to use such
materials. Examples include clinical photographs or even scans,
patient cases, diagnostic video and so on. Although I am speaking
mostly from a medical perspective I would expect there to be similar
issues for education, social work and so on. The DREL s/s contains
'permissions' references but no direct reference to 'consent'.
In that such expressions of the range and forms of consent given at
the point of origination are essential in a DREL, how should these
best be structured and represented?
best
Rachel Ellaway
eLearning Manager
MVM Learning Technology Section
The University of Edinburgh
===================================================================
>Dear All,
>
>As you may know, the IEEE Learning Technology Sub-Committee (LTSC) has
>been working on the standardisation of a Digital Rights Expression
>Language (DREL) for six months or so.
>
>At this stage, it is most important to have as complete a set of
>e-learning specific requirements on a DREL. Though requirements will
>continue to be collected for ongoing work on the future IEEE DREL, the
>first tranche will close by October 3d, and will form the basis of the
>standard.
>
>At the moment, more requirements are still needed from as diverse a set
>of e-learning stakeholders as possible.
>
>To facilitate the requirements gathering process, the IEEE DREL working
>group has made a spreadsheet
><http://ltsc.ieee.org/wg4/DREL_Requirements_draft3.xls> with all the
>requirements that have been gathered so far.
>
>What the spreadsheet indicates is
>- the person or organisation who submitted the requirement
>- the domain category of the requirement (HE, FE, Secondary, training,
>etc. or 'General', if it's across the board)
>- 'Education/Training Requirement'; a brief use-case-like outline of the
>requirement from an educational point of view
>- 'REL Requirement'; a translation of the Education/Training Requirement
>from the point of view of the DREL itself
>
>'Technical suggestions' and 'Disposition' are for the benefit of the
>requirement evaluators. The colour bands indicate the domain category.
>
>To submit a requirement, all you need to do is check whether the
>requirement has been included in the spreadsheet already. If it hasn't,
>just add a row to the spreadsheet, and fill in the 'SOURCE' 'DOMAIN' and
>'Education/Training Requirement' columns in a red font. The whole
>spreadsheet can then be sent to either me or the working group's editor,
>Jon Mason ([log in to unmask]), and it'll be merged into the
>master spreadsheet that will be maintained on the LTSC website.
>
>Please bear in mind that the group is focussed on gathering requirements
>on a digital requirements language, as opposed to a complete digital
>rights management (DRM) system. The main difference is that a DREL just
>expresses exactly what rights an author or other rightsholder wishes to
>grant to users. It doesn't get involved in enforcing these rights.
>
>You can read more about the IEEE DREL work on
><http://cetis.ac.uk/content/20030710051134>.
>
>Any submissions would be greatly appreciated, but, more importanty, it
>will help ensure that the digital content of the future can express the
>rights you need it to express as an author, a consumer or custodian.
>
>--
>Wilbert Kraan
>Web Journalist
>Centre For Educational Technology Interoperability Standards (CETIS)
>+44 (0)1248 383645
>web: http://www.cetis.ac.uk newsfeed: http://www.cetis.ac.uk/news.xml
|