DOCSLIB.ORG

Mopidy Documentation Release 3.2.0-3-Gb10f3115

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text

Load more

Mopidy Documentation Release 3.2.0-3-gb10f3115 Stein Magnus Jodal and contributors 2021 USAGE 1 Installation 3 1.1 Debian/Ubuntu..............................................3 1.2 Arch Linux................................................4 1.3 Fedora..................................................5 1.4 macOS..................................................6 1.5 Install from PyPI.............................................7 1.6 Raspberry Pi...............................................9 2 Running 11 2.1 Running in a terminal.......................................... 11 2.2 Running as a service........................................... 12 3 Configuration 17 3.1 Configuration file location........................................ 17 3.2 Editing the configuration......................................... 17 3.3 View effective configuration....................................... 17 3.4 Core configuration............................................ 18 3.5 Extension configuration......................................... 21 3.6 Adding new configuration values.................................... 21 4 Clients 23 4.1 Web clients................................................ 23 4.2 MPD clients............................................... 24 4.3 MPRIS clients.............................................. 24 5 Troubleshooting 25 5.1 Getting help............................................... 25 5.2 Show effective configuration....................................... 25 5.3 Show installed dependencies....................................... 25 5.4 Debug logging.............................................. 26 5.5 Track metadata.............................................. 26 5.6 Debugging deadlocks.......................................... 27 5.7 Debugging GStreamer.......................................... 27 6 Mopidy-File 29 6.1 Configuration............................................... 29 7 Mopidy-M3U 31 7.1 Editing playlists............................................. 31 7.2 Configuration............................................... 31 i 8 Mopidy-Stream 33 8.1 Configuration............................................... 33 9 Mopidy-HTTP 35 9.1 Hosting web clients............................................ 35 9.2 Configuration............................................... 35 10 Mopidy-SoftwareMixer 37 10.1 Configuration............................................... 37 11 Audio sinks 39 12 Icecast 41 12.1 Known issues............................................... 42 12.2 Fallback stream.............................................. 42 13 UPnP 43 13.1 UPnP MediaRenderer.......................................... 43 13.2 UPnP clients............................................... 44 14 Changelog 45 14.1 v3.2.0 (2021-07-08)........................................... 45 14.2 v3.1.1 (2020-12-26)........................................... 45 14.3 v3.1.0 (2020-12-16)........................................... 45 14.4 v3.0.2 (2020-04-02)........................................... 46 14.5 v3.0.1 (2019-12-22)........................................... 46 14.6 v3.0.0 (2019-12-22)........................................... 46 15 History 51 15.1 Changelog 2.x series........................................... 51 15.2 Changelog 1.x series........................................... 58 15.3 Changelog 0.x series........................................... 71 16 Versioning 109 16.1 Release schedule............................................. 109 17 Authors 111 18 Sponsors 115 18.1 Discourse................................................. 115 19 Contributing 117 19.1 Asking questions............................................. 117 19.2 Helping users............................................... 117 19.3 Issue guidelines............................................. 117 19.4 Pull request guidelines.......................................... 118 20 Development environment 119 20.1 Initial setup................................................ 120 20.2 Running Mopidy from Git........................................ 123 20.3 Running tests............................................... 123 20.4 Writing documentation.......................................... 125 20.5 Working on extensions.......................................... 126 20.6 Contribution workflow.......................................... 127 ii 21 Extension development 129 21.1 Anatomy of an extension......................................... 129 21.2 cookiecutter project template...................................... 130 21.3 Example README.rst.......................................... 130 21.4 Example setup.py............................................. 131 21.5 Example __init__.py........................................... 132 21.6 Example frontend............................................ 134 21.7 Example backend............................................. 134 21.8 Example command............................................ 135 21.9 Example web application......................................... 135 21.10 Running an extension.......................................... 135 21.11 Python conventions............................................ 135 21.12 Use of Mopidy APIs........................................... 136 21.13 Logging in extensions.......................................... 136 21.14 Making HTTP requests from extensions................................. 136 21.15 Testing extensions............................................ 138 22 Code style 143 23 Release procedures 145 23.1 Releasing extensions........................................... 145 23.2 Releasing Mopidy itself......................................... 146 24 API reference 149 24.1 Concepts................................................. 149 24.2 Basics................................................... 159 24.3 Web/JavaScript.............................................. 181 24.4 Audio................................................... 186 24.5 Utilities.................................................. 192 25 mopidy command 199 25.1 Synopsis................................................. 199 25.2 Description................................................ 199 25.3 Options.................................................. 199 25.4 Built in commands............................................ 200 25.5 Extension commands........................................... 200 25.6 Files................................................... 200 25.7 Examples................................................. 200 25.8 Reporting bugs.............................................. 201 26 Glossary 203 27 Indices and tables 205 Python Module Index 207 Index 209 iii iv Mopidy Documentation, Release 3.2.0-3-gb10f3115 Mopidy is an extensible music server written in Python. Mopidy plays music from local disk, Spotify, SoundCloud, Google Play Music, and more. You edit the playlist from any phone, tablet, or computer using a variety of MPD and web clients. Stream music from the cloud Vanilla Mopidy only plays music from files and radio streams. Through extensions, Mopidy can play music from cloud services like Spotify, SoundCloud, and Google Play Music. With Mopidy’s extension support, backends for new music sources can be easily added. Mopidy is just a server Mopidy is a Python application that runs in a terminal or in the background on Linux computers or Macs that have network connectivity and audio output. Out of the box, Mopidy is an HTTP server. If you install the Mopidy-MPD extension, it becomes an MPD server too. Many additional frontends for controlling Mopidy are available as extensions. Pick your favorite client You and the people around you can all connect their favorite MPD or web client to the Mopidy server to search for music and manage the playlist together. With a browser or MPD client, which is available for all popular operating systems, you can control the music from any phone, tablet, or computer. Mopidy on Raspberry Pi The Raspberry Pi is an popular device to run Mopidy on, either using Raspbian, Ubuntu, or Arch Linux. Pimoroni recommends Mopidy for use with their Pirate Audio audio gear for Raspberry Pi. Mopidy is also a significant building block in the Pi Musicbox integrated audio jukebox system for Raspberry Pi. Mopidy is hackable Mopidy’s extension support and Python, JSON-RPC, and JavaScript APIs make Mopidy a perfect base for your projects. In one hack, a Raspberry Pi was embedded in an old cassette player. The buttons and volume control are wired up with GPIO on the Raspberry Pi, and is used to control playback through a custom Mopidy extension. The cassettes have NFC tags used to select playlists from Spotify. Getting started To get started with Mopidy, begin by reading Installation. Getting help If you get stuck, you can get help at the our Discourse forum or in the #mopidy-users stream on Zulip chat. If you stumble into a bug or have a feature request, please create an issue in the issue tracker. If you’re unsure if it’s a bug or not, ask for help in the forum or the chat first. The source code may also be of help. If you want to stay up to date on Mopidy developments, you can follow the #mopidy-dev stream on Zulip chat or watch out for announcements on the Discourse forum. USAGE 1 Mopidy Documentation, Release 3.2.0-3-gb10f3115 2 USAGE CHAPTER ONE INSTALLATION There are several ways to install Mopidy. What way is best depends upon your operating system and/or distribution: 1.1 Debian/Ubuntu If you run a Debian based Linux distribution, like Ubuntu or Raspbian, the easiest way to install Mopidy
Recommended publications
  • Mdns/Dns-Sd Tutorial

    Mdns/Dns-Sd Tutorial

    MDNS/DNS-SD TUTORIAL In this tutorial, we will describe how to use mDNS/DNS-SD on Raspberry Pi. mDNS/DNS-SD is a protocol for service discovery in a local area network. It is standardized under RFCs 6762 [1] and 6763[2]. The protocol is also known by the Bonjour trademark by Apple, or Zeroconf. On Linux, it is implemented in the avahi package. [1] http://tools.ietf.org/html/rfc6762 [2] http://tools.ietf.org/html/rfc6763 About mDNS/DNS-SD There are several freely available implementations of mDNS/DNS-SD: 1. avahi – Linux implementation (http://www.avahi.org/) 2. jmDNS – Java implementation (http://jmdns.sourceforge.net/) 3. Bonjour – MAC OS (installed by default) 4. Bonjour – Windows (https://support.apple.com/kb/DL999?locale=en_US) During this course, we will use only avahi. However, any of the aforementioned implementations are compatible. Avahi installation avahi is available as a package for Raspbian. Install it with: sudo apt-get install avahi-deamon avahi-utils Avahi usage avahi-daemon is the main process that takes care of proper operation of the protocol. It takes care of any configuration of the interfaces and network messaging. A user can control the deamon with command line utilities, or via D-Bus. In this document, we will describe the former option. For the latter one, please see http://www.avahi.org/wiki/Bindings. Publishing services avahi-publish-service is the command for publishing services. The syntax is: avahi-publish-service SERVICE-NAME _APPLICATION- PROTOCOL._TRANPOSRT-PROTOCOL PORT “DESCRIPTION” --sub SUBPROTOCOL For instance, the command: avahi-publish-service light _coap._udp 5683 “/mylight” --sub _floor1._sub._coap._udp will publish a service named ‘light’, which uses the CoAP protocol over UDP on port 5683.
  • A High-Level Programming Language for Multimedia Streaming

    A High-Level Programming Language for Multimedia Streaming

    Liquidsoap: a High-Level Programming Language for Multimedia Streaming David Baelde1, Romain Beauxis2, and Samuel Mimram3 1 University of Minnesota, USA 2 Department of Mathematics, Tulane University, USA 3 CEA LIST – LMeASI, France Abstract. Generating multimedia streams, such as in a netradio, is a task which is complex and difficult to adapt to every users’ needs. We introduce a novel approach in order to achieve it, based on a dedi- cated high-level functional programming language, called Liquidsoap, for generating, manipulating and broadcasting multimedia streams. Unlike traditional approaches, which are based on configuration files or static graphical interfaces, it also allows the user to build complex and highly customized systems. This language is based on a model for streams and contains operators and constructions, which make it adapted to the gen- eration of streams. The interpreter of the language also ensures many properties concerning the good execution of the stream generation. The widespread adoption of broadband internet in the last decades has changed a lot our way of producing and consuming information. Classical devices from the analog era, such as television or radio broadcasting devices have been rapidly adapted to the digital world in order to benefit from the new technologies available. While analog devices were mostly based on hardware implementations, their digital counterparts often consist in software implementations, which po- tentially offers much more flexibility and modularity in their design. However, there is still much progress to be done to unleash this potential in many ar- eas where software implementations remain pretty much as hard-wired as their digital counterparts.
  • Tamil Flac Songs Free Download Tamil Flac Songs Free Download

    Tamil Flac Songs Free Download Tamil Flac Songs Free Download

    tamil flac songs free download Tamil flac songs free download. Get notified on all the latest Music, Movies and TV Shows. With a unique loyalty program, the Hungama rewards you for predefined action on our platform. Accumulated coins can be redeemed to, Hungama subscriptions. You can also login to Hungama Apps(Music & Movies) with your Hungama web credentials & redeem coins to download MP3/MP4 tracks. You need to be a registered user to enjoy the benefits of Rewards Program. You are not authorised arena user. Please subscribe to Arena to play this content. [Hi-Res Audio] 30+ Free HD Music Download Sites (2021) ► Read the definitive guide to hi-res audio (HD music, HRA): Where can you download free high-resolution files (24-bit FLAC, 384 kHz/ 32 bit, DSD, DXD, MQA, Multichannel)? Where to buy it? Where are hi-res audio streamings? See our top 10 and long hi-res download site list. ► What is high definition audio capability or it’s a gimmick? What is after hi-res? What's the highest sound quality? Discover greater details of high- definition musical formats, that, maybe, never heard before. The explanation is written by Yuri Korzunov, audio software developer with 20+ years of experience in signal processing. Keep reading. Table of content (click to show). Our Top 10 Hi-Res Audio Music Websites for Free Downloads Where can I download Hi Res music for free and paid music sites? High- resolution music free and paid download sites Big detailed list of free and paid download sites Download music free online resources (additional) Download music free online resources (additional) Download music and audio resources High resolution and audiophile streaming Why does Hi Res audio need? Digital recording issues Digital Signal Processing What is after hi-res sound? How many GB is 1000 songs? Myth #1.
  • State of Linux Audio in 2009 Linux Plumbers Conference 2009

    State of Linux Audio in 2009 Linux Plumbers Conference 2009

    State of Linux Audio in 2009 Linux Plumbers Conference 2009 Lennart Poettering [email protected] September 2009 Lennart Poettering State of Linux Audio in 2009 Who Am I? Software Engineer at Red Hat, Inc. Developer of PulseAudio, Avahi and a few other Free Software projects http://0pointer.de/lennart/ [email protected] IRC: mezcalero Lennart Poettering State of Linux Audio in 2009 Perspective Lennart Poettering State of Linux Audio in 2009 So, what happened since last LPC? Lennart Poettering State of Linux Audio in 2009 RIP: EsounD is officially gone. Lennart Poettering State of Linux Audio in 2009 (at least on Fedora) RIP: OSS is officially gone. Lennart Poettering State of Linux Audio in 2009 RIP: OSS is officially gone. (at least on Fedora) Lennart Poettering State of Linux Audio in 2009 Audio API Guide http://0pointer.de/blog/projects/guide-to-sound-apis Lennart Poettering State of Linux Audio in 2009 We also make use of high-resolution timers on the desktop by default. We now use realtime scheduling on the desktop by default. Lennart Poettering State of Linux Audio in 2009 We now use realtime scheduling on the desktop by default. We also make use of high-resolution timers on the desktop by default. Lennart Poettering State of Linux Audio in 2009 2s Buffers Lennart Poettering State of Linux Audio in 2009 Mixer abstraction? Due to user-friendliness, i18n, meta data (icons, ...) We moved a couple of things into the audio server: Timer-based audio scheduling; mixing; flat volume/volume range and granularity extension; integration of volume sliders; mixer abstraction; monitoring Lennart Poettering State of Linux Audio in 2009 We moved a couple of things into the audio server: Timer-based audio scheduling; mixing; flat volume/volume range and granularity extension; integration of volume sliders; mixer abstraction; monitoring Mixer abstraction? Due to user-friendliness, i18n, meta data (icons, ...) Lennart Poettering State of Linux Audio in 2009 udev integration: meta data, by-path/by-id/..
  • FAA-STD-075, Creating Service Identifiers

    FAA-STD-075, Creating Service Identifiers

    FAA-STD-075 June 29, 2021 SUPERSEDING FAA-STD-063 May 1, 2009 U.S. Department of Transportation Federal Aviation Administration U.S. Department of Transportation Federal Aviation Administration Standard Practice CREATING SERVICE IDENTIFIERS FAA-STD-075 June 29, 2021 FOREWORD This standard is approved for use by all Departments of the Federal Aviation Administration (FAA). This standard sets forth requirements for creating globally-unique identifiers for FAA service-oriented architecture (SOA)-based services. This standard has been prepared in accordance with FAA-STD-068, Department of Transportation Federal Aviation Administration, Preparation of Standards [STD068]. Comments, suggestions, or questions on this document shall be addressed to: Federal Aviation Administration System Wide Information Management (SWIM) Program Office, AJM-316 800 Independence Avenue, SW Washington, DC 20591 https://www.faa.gov/air_traffic/technology/swim/contacts/ i FAA-STD-075 June 29, 2021 Table of Contents 1 SCOPE ..................................................................................................................................................1 1.1 INTRODUCTION ...........................................................................................................................................1 1.2 INTENDED AUDIENCE ....................................................................................................................................1 1.3 BASIC CONCEPTS .........................................................................................................................................2
  • Opus, a Free, High-Quality Speech and Audio Codec

    Opus, a Free, High-Quality Speech and Audio Codec

    Opus, a free, high-quality speech and audio codec Jean-Marc Valin, Koen Vos, Timothy B. Terriberry, Gregory Maxwell 29 January 2014 Xiph.Org & Mozilla What is Opus? ● New highly-flexible speech and audio codec – Works for most audio applications ● Completely free – Royalty-free licensing – Open-source implementation ● IETF RFC 6716 (Sep. 2012) Xiph.Org & Mozilla Why a New Audio Codec? http://xkcd.com/927/ http://imgs.xkcd.com/comics/standards.png Xiph.Org & Mozilla Why Should You Care? ● Best-in-class performance within a wide range of bitrates and applications ● Adaptability to varying network conditions ● Will be deployed as part of WebRTC ● No licensing costs ● No incompatible flavours Xiph.Org & Mozilla History ● Jan. 2007: SILK project started at Skype ● Nov. 2007: CELT project started ● Mar. 2009: Skype asks IETF to create a WG ● Feb. 2010: WG created ● Jul. 2010: First prototype of SILK+CELT codec ● Dec 2011: Opus surpasses Vorbis and AAC ● Sep. 2012: Opus becomes RFC 6716 ● Dec. 2013: Version 1.1 of libopus released Xiph.Org & Mozilla Applications and Standards (2010) Application Codec VoIP with PSTN AMR-NB Wideband VoIP/videoconference AMR-WB High-quality videoconference G.719 Low-bitrate music streaming HE-AAC High-quality music streaming AAC-LC Low-delay broadcast AAC-ELD Network music performance Xiph.Org & Mozilla Applications and Standards (2013) Application Codec VoIP with PSTN Opus Wideband VoIP/videoconference Opus High-quality videoconference Opus Low-bitrate music streaming Opus High-quality music streaming Opus Low-delay
  • The Semantic Web

    The Semantic Web

    The Semantic Web Ovidiu Chira IDIMS Report 21st of February 2003 1. Introduction 2. Background 3. The structure of the Semantic Web 4. Final Remarks 1 1. Introduction One of the most successful stories of the information age is the story of the World Wide Web (WWW). The WWW was developed in 1989 by Tim Berners-Lee to enable the sharing of information among geographically dispersed teams of researchers within the European Laboratory for Particle Physics (CERN). The simplicity of publishing on WWW and the envisioned benefits attracted an increasing number of users from beyond the boundaries of the research community. The WWW grew rapidly to support not only information sharing between scientists (as it was intended), but to support information sharing among different kind of people communities, from simple homepages to large business applications. The Web became an “universal medium for exchanging data and knowledge: for the first time in history we have a widely exploited many-to-many medium for data interchange” [Decker, Harmelen et al. 2000]. The WWW is estimated to consist from around one billion documents and more than 300 millions users access them, and these numbers are growing fast [Fensel 2001; Benjamins, Contreras et al. 2002]. Soon, as a ”medium for human communication, the Web has reached critical mass […] but as a mechanism to exploit the power of computing in our every-day life, the Web is in its infancy” [Connolly 1998; Cherry 2002]. On one hand it became clear that while the Web enables human communication and human access to information it lacks of tools or technologies to ease the management of Web’s resources [Fensel 2000; Fensel 2001; Palmer 2001].
  • VNC User Guide 7 About This Guide

    VNC User Guide 7 About This Guide

    VNC® User Guide Version 5.3 December 2015 Trademarks RealVNC, VNC and RFB are trademarks of RealVNC Limited and are protected by trademark registrations and/or pending trademark applications in the European Union, United States of America and other jursidictions. Other trademarks are the property of their respective owners. Protected by UK patent 2481870; US patent 8760366 Copyright Copyright © RealVNC Limited, 2002-2015. All rights reserved. No part of this documentation may be reproduced in any form or by any means or be used to make any derivative work (including translation, transformation or adaptation) without explicit written consent of RealVNC. Confidentiality All information contained in this document is provided in commercial confidence for the sole purpose of use by an authorized user in conjunction with RealVNC products. The pages of this document shall not be copied, published, or disclosed wholly or in part to any party without RealVNC’s prior permission in writing, and shall be held in safe custody. These obligations shall not apply to information which is published or becomes known legitimately from some source other than RealVNC. Contact RealVNC Limited Betjeman House 104 Hills Road Cambridge CB2 1LQ United Kingdom www.realvnc.com Contents About This Guide 7 Chapter 1: Introduction 9 Principles of VNC remote control 10 Getting two computers ready to use 11 Connectivity and feature matrix 13 What to read next 17 Chapter 2: Getting Connected 19 Step 1: Ensure VNC Server is running on the host computer 20 Step 2: Start VNC
  • Tiny Disco: a Cost-Effective, High-Fidelity Wireless Audio System ​ Quarter / Year Submitted: Winter 2020 ​ Student: (Print Name) ______(Sign) ______

    Tiny Disco: a Cost-Effective, High-Fidelity Wireless Audio System ​ Quarter / Year Submitted: Winter 2020 ​ Student: (Print Name) ______(Sign) ______

    Tiny Disco: A Cost-Effective, High-Fidelity Wireless Audio System A Senior Project Report presented to the Faculty of California Polytechnic State University San Luis Obispo In Partial Fulfillment of the Requirements for the Degree Bachelor of Science in Computer Engineering By Luke Liberatore February 2020 Date of Submission: February 25, 2020 Senior Project Advisor: Hugh Smith Abstract The Tiny Disco is a WiFi based concert system, featuring improvements on popular “Silent Disco” concerts. Rather than being tied to compression and bandwidth restrictions present in traditional silent disco systems, the Tiny Disco system can deliver 320kbps+ audio quality, and allows listeners to bring their own headphones, further lending to the high quality audio experience. Tiny Disco uses a Raspberry Pi as the audio server, and Espressif ESP32 microcontrollers as audio receivers/clients. The Tiny Disco is primarily geared toward smaller concerts and niche events where audio quality is valued, though due to its WiFi-based architecture, it can be expanded to events of a few hundred people fairly easily. The Tiny Disco system was developed and tested, and performed successfully using a test setup. Only one client was tested due to cost constraints, but load testing was performed against the Raspberry Pi server, as well as bandwidth/audio quality analysis. 2 Table of Contents Abstract 2 Table of Contents 3 Introduction 5 Stakeholders 7 Project Goals and Objectives 7 Project Deliverables 8 Project Outcomes 8 Background 9 Experimentation to help develop
  • RZ/G Verified Linux Package for 64Bit Kernel Version 1.0.5-RT R01TU0278EJ0105 Rev

    RZ/G Verified Linux Package for 64Bit Kernel Version 1.0.5-RT R01TU0278EJ0105 Rev

    RZ/G Verified Linux Package for 64bit kernel Version 1.0.5-RT R01TU0278EJ0105 Rev. 1.05 Component list Aug. 31, 2020 Components listed below are installed to the rootfs which is used for booting target boards by building the Verified Linux Package according to the Release Note. Each image name corresponds to the target name used when running bitbake commands such as “bitbake core-image- weston”. Column “weston (Gecko)” corresponds to the building procedure for HTML5 described in the Release Note for HTML5. Versions of some packages installed for HTML5 are different from the other images. In the cases where a version of a specific package installed for HTML5 is different, it is written like as “(Gecko: x.x.x)” in column “version”. weston minimal bsp weston qt version (Gecko) acl ✓ 2.2.52 adwaita-icon-theme-symbolic ✓ ✓ ✓ 3.24.0 alsa-conf ✓ ✓ ✓ ✓ 1.1.4.1 alsa-plugins-pulseaudio-conf ✓ 1.1.4 alsa-states ✓ ✓ ✓ ✓ 0.2.0 alsa-tools ✓ ✓ ✓ 1.1.3 alsa-utils ✓ ✓ ✓ ✓ 1.1.4 alsa-utils-aconnect ✓ ✓ ✓ ✓ 1.1.4 alsa-utils-alsactl ✓ ✓ ✓ ✓ 1.1.4 alsa-utils-alsaloop ✓ ✓ ✓ ✓ 1.1.4 alsa-utils-alsamixer ✓ ✓ ✓ ✓ 1.1.4 alsa-utils-alsatplg ✓ ✓ ✓ ✓ 1.1.4 alsa-utils-alsaucm ✓ ✓ ✓ ✓ 1.1.4 alsa-utils-amixer ✓ ✓ ✓ ✓ 1.1.4 alsa-utils-aplay ✓ ✓ ✓ ✓ 1.1.4 alsa-utils-aseqdump ✓ ✓ ✓ ✓ 1.1.4 alsa-utils-aseqnet ✓ ✓ ✓ ✓ 1.1.4 alsa-utils-iecset ✓ ✓ ✓ ✓ 1.1.4 alsa-utils-midi ✓ ✓ ✓ ✓ 1.1.4 alsa-utils-speakertest ✓ ✓ ✓ ✓ 1.1.4 at ✓ 3.1.20 attr ✓ 2.4.47 audio-init ✓ ✓ ✓ ✓ 1.0 avahi-daemon ✓ ✓ ✓ 0.6.32 avahi-locale-en-gb ✓ ✓ ✓ 0.6.32 base-files ✓ ✓ ✓ ✓ ✓ 3.0.14 base-files-dev ✓ ✓ ✓ 3.0.14 base-passwd ✓ ✓ ✓ ✓ ✓ 3.5.29 bash ✓ ✓ ✓ ✓ ✓ 3.2.57 bash-dev ✓ ✓ ✓ 3.2.57 bayer2raw ✓ ✓ ✓ 1.0 bc ✓ 1.06 bc-dev ✓ 1.06 bluez5 ✓ ✓ ✓ ✓ 5.46 bluez-alsa ✓ ✓ ✓ ✓ 1.0 bt-fw ✓ ✓ ✓ ✓ 8.7.1+git0+0ee619b598 busybox ✓ ✓ ✓ ✓ ✓ 1.30.1 (Gecko: 1.22.0) busybox-hwclock ✓ ✓ ✓ ✓ ✓ 1.30.1 (Gecko: 1.22.0) busybox-udhcpc ✓ ✓ ✓ ✓ ✓ 1.30.1 (Gecko: 1.22.0) bzip2 ✓ ✓ ✓ 1.0.6 R01TU0278EJ0105 Rev.
  • Meditative Story Transcript – Kaywin Feldman

    Meditative Story Transcript – Kaywin Feldman

    Meditative Story Transcript – Kaywin Feldman Click here to listen to the full Meditative Story episode with Kaywin Feldman. KAYWIN FELDMAN: I don’t even change my clothes. I just head out to make it there in time. It’s close to the center of town, so I don’t have to walk far. I pay my entrance fee and walk in. There are hardly any visitors. The chapel is small and attached to a monastery. The building itself is tall but nothing terribly special. But suddenly I see it: Every inch of wall, floor to ceiling, is painted with a narrative cycle. The first thing I notice is the stillness. I can’t even hear my sneakers on the stone floor. It’s cool inside. Then the glow. The whole room, even the arched ceiling, glows lapis blue from the paint. Inside this still room, my body stills, too. I am in need of sanctuary, and here it is. It feels safe, sacred. It lets me emotionally and intellectually clear my mind, so that I can really look at the frescoes. I’m hardly breathing. My heart rate slows. I can feel my mouth open as I take in the room. ROHAN GUNATILLAKE: Kaywin Feldman grew up in a military family, and her childhood memories are dominated by visits to art museums in the various cities and towns where her family moved. You might say she was destined to become a museum director, and at the young age of 28, she achieves just that. Today, Kaywin presides over the National Gallery of Art in Washington, DC.
  • RDF and the Semantic Web.(Database and Network Journal-Intelligence) © COPYRIGHT 2003 A.P

    RDF and the Semantic Web.(Database and Network Journal-Intelligence) © COPYRIGHT 2003 A.P

    Database and Network Journal Oct 2003 v33 i5 p3(2) Page 1 RDF and the Semantic Web.(Database And Network Journal-Intelligence) © COPYRIGHT 2003 A.P. Publications Ltd. that developing a consistent universal data format would not be too great a task. However, it has proved in the past Part 1--The Semantic Web that it is almost impossible to get two companies to agree on a specific definition of "data". There has never been The World Wide Web’s simplicity was a key factor in its complete agreement as to data exchange formats. The rapid adoption. But as it grows ever larger and more arrival of XML offers hope of a wide acceptance of its complex, that simplicity has begun to hinder our ability to syntax or syntactic rules which no one faction can claim. make intelligent use of the vast store of data on the Web. In response to that challenge, the Worm Wide Web The Semantic Web is generally built on syntaxes which Consortium (W3C) has spearheaded an effort to create an use URIs to represent data, usually in triples based extension of the Web that brings meaning and order to structures: i.e. many triples of URI data that can be held in web data. It’s called the Semantic Web, and at its core is databases, or interchanged on the world Wide Web using the Resource Description Framework (RDF), an a set of particular syntaxes developed especially for the application of XML. However, whilst the creation of the task. These syntaxes are called "Resource Description Semantic Web is dependant on RDF, it is conceivable that Framework" syntaxes.