It has been a while, but we have a few small updates that are in preparation for the next version of myUMBC. These are mostly procedural/administrative changes to get things more inline with some larger changes in the pipeline.

• Community Spotlights limited to Institutional and Student Org groups - Spotlights are a useful and popular way to promote things to the campus, but they're almost too popular. Because each spotlight is approved by multiple people, a huge amount of time is spent validating that only the appropriate groups are submitting them. We've limited the ability to post Community Spotlights to only student orgs and institutional groups to make it easier to identify these groups.
• If you don't have a group for your department or student org, you should get one. It's quick and easy. Start a Group
• Make sure everyone who needs to post spotlights is an admin of the group.
• All groups are still free to post News, Events, Discussions, and Media.
• Image Permission - when posting an image to myUMBC, it is important to only use ones that you have permission to repost. You are now asked to confirm this permission before you can upload images.
• Rich Content in Notifications - Your email notifications from myUMBC now include the full post and richer formatting. No more having to log in to myUMBC just to read something.
• Notifications OFF by default on new posts - myUMBC was generating a LOT of email to people, which sorta goes against one of our core goals to minimize the number of times you're interrupted throughout the day. Now, if you're posting something important that you want people to know about, put a check in the Send Notifications checkbox.
• Group Access changes - We've disabled the ability to change the access level of their groups to and from Private. This is to ensure that content and conversations made within groups retain intended audience.
• Category Deprecation - There is a little known feature in Groups called Categories. We would strongly encourage people not to use this feature because it may be removed in a future update. It is still enabled so that anyone using the tool has a chance to stop.

The Device APIs Working Group invites implementation of the Candidate Recommendation of Vibration API. This specification defines an API that provides access to the vibration mechanism of the hosting device. Vibration is a form of tactile feedback. Learn more about the Ubiquitous Web Applications Activity.

The RDF Working Group has published two Last Call Working Drafts today:

• A Last Call Working Draft of RDF 1.1 Concepts and Abstract Syntax. The Resource Description Framework (RDF) is a framework for representing information in the Web. Comments are welcome through 6 September.
• A Last Call Working Draft of RDF 1.1 Semantics. This document describes a precise semantics for the Resource Description Framework 1.1 and RDF Schema. It defines a number of distinct entailment regimes and corresponding patterns of entailment. It is part of a suite of documents which comprise the full specification of RDF 1.1. Comments are welcome through 6 September.

Learn more about the Semantic Web Activity.