[
http://jira.dspace.org/jira/browse/DS-358?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=10833#action_10833
]
Stuart Lewis commented on DS-358:
---------------------------------
Mark H. Wood:
Well, there are various aspects of HTML5 that I think we need to
consider separately.
There are new elements we can use to mark portions of the page as
headers or footers or sidebars or the like. They don't greatly affect
the experience of most users, at least not right away, and it doesn't
greatly matter to most users if they don't yet have browsers that can
understand those elements. We can start working out appropriate uses
of them and using them without much worry. Yes, let's begin taking
advantage of more-meaningful markup and let the benefits be realized
as the client tools fill in.
HTML5 attempts to give less of the sort of room for interpretation
that has resulted in the worst cross-browser compatibility horrors of
previous versions. We will need to pay attention to such matters, to
avoid surprising or inconveniencing the user of a more strictly
compliant browser.
Other elements bear still more scrutiny. There is a long-felt need
for better support of audio and video material, and the new audio and
video elements might be used to meet that need. But here the user's
browser makes the difference between "it works" and "it fails, and
perhaps chides you for not upgrading daily". We also need to
understand the performance characteristics of embedded media
vs. streaming vs. magic Flash widgets. We need to think just a bit
about how we count downloads of something that could be started and/or
stopped in the middle. We need to examine the different codec bundles
provided by the browsers that implement these elements at all. (Do we
provide multiple encodings, or point to add-on codec packages, or some
of each, or...?) This stuff will affect and be affected by our sites'
acceptable-formats policies.
--
Mark H. Wood, Lead System Programmer [email protected]
> Discuss implications of HTML5 for DSpace
> ----------------------------------------
>
> Key: DS-358
> URL: http://jira.dspace.org/jira/browse/DS-358
> Project: DSpace 1.x
> Issue Type: Task
> Components: JSPUI, XMLUI
> Reporter: Stuart Lewis
> Priority: Minor
>
> The possible implications of HTML5 on DSpace need to be discussed. Please use
> this JIRA ticket to add comments and discussion.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.dspace.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
------------------------------------------------------------------------------
Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day
trial. Simplify your report design, integration and deployment - and focus on
what you do best, core application coding. Discover what's new with
Crystal Reports now. http://p.sf.net/sfu/bobj-july
_______________________________________________
Dspace-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/dspace-devel
