Comments for CC:DA https://alcts.ala.org/ccdablog Committee on Cataloging: Description & Access Thu, 20 Oct 2016 13:47:18 +0000 hourly 1 https://wordpress.org/?v=4.9.9 Comment on Expanding RDA 6.29.1.3, Laws Governing More Than One Jurisdiction by Kathy Glennan https://alcts.ala.org/ccdablog/?p=3031#comment-15031 Thu, 20 Oct 2016 13:47:18 +0000 http://alcts.ala.org/ccdablog/?p=3031#comment-15031 FYI, I am working with Robert Bratton to create a revised proposal. The desired outcome from AALL’s perspective is to create the AAP for these laws using: 1) the title and 2) the names of the governed jurisdictions, enclosed in parentheses.

]]>
Comment on Adding Controlled Vocabulary to RDA 3.19.6, Regional Encoding, and to the Glossary by Amanda Ros https://alcts.ala.org/ccdablog/?p=3029#comment-15026 Tue, 18 Oct 2016 21:25:23 +0000 http://alcts.ala.org/ccdablog/?p=3029#comment-15026 I like the second option with changing the second “encoding” to “device”

]]>
Comment on Adding Controlled Vocabulary to RDA 3.19.6, Regional Encoding, and to the Glossary by Amanda Ros https://alcts.ala.org/ccdablog/?p=3029#comment-15025 Tue, 18 Oct 2016 21:20:56 +0000 http://alcts.ala.org/ccdablog/?p=3029#comment-15025 Agree

]]>
Comment on Adding Controlled Vocabulary to RDA 3.19.6, Regional Encoding, and to the Glossary by Amanda Ros https://alcts.ala.org/ccdablog/?p=3029#comment-15024 Tue, 18 Oct 2016 21:20:19 +0000 http://alcts.ala.org/ccdablog/?p=3029#comment-15024 I agree with Nancy’s comment

]]>
Comment on Adding Controlled Vocabulary to RDA 3.19.6, Regional Encoding, and to the Glossary by Amanda Ros https://alcts.ala.org/ccdablog/?p=3029#comment-15023 Tue, 18 Oct 2016 21:18:25 +0000 http://alcts.ala.org/ccdablog/?p=3029#comment-15023 I agree with limiting the scope

]]>
Comment on Providing Greater Flexibility in Creating Variant Access Points (RDA Chapters 5, 6, 8, 9, 10, and 11) by Yoko Kudo https://alcts.ala.org/ccdablog/?p=3033#comment-15021 Tue, 18 Oct 2016 17:39:09 +0000 http://alcts.ala.org/ccdablog/?p=3033#comment-15021 As for the name portion in non-Latin script, I personally think it’s something that the system should be able to infer and process in the future, because the AR for the name should already have a non-Latin variant AAP.

]]>
Comment on Adding Controlled Vocabulary to RDA 3.19.6, Regional Encoding, and to the Glossary by Tina Shrader https://alcts.ala.org/ccdablog/?p=3029#comment-15020 Tue, 18 Oct 2016 13:19:58 +0000 http://alcts.ala.org/ccdablog/?p=3029#comment-15020 I like this wording much better.

]]>
Comment on Adding Controlled Vocabulary to RDA 3.19.6, Regional Encoding, and to the Glossary by Yoko Kudo https://alcts.ala.org/ccdablog/?p=3029#comment-15019 Mon, 17 Oct 2016 22:55:05 +0000 http://alcts.ala.org/ccdablog/?p=3029#comment-15019 Yes I do like it better than “intended to be…”

]]>
Comment on Adding Controlled Vocabulary to RDA 3.19.6, Regional Encoding, and to the Glossary by Kathy Glennan https://alcts.ala.org/ccdablog/?p=3029#comment-15018 Mon, 17 Oct 2016 21:46:54 +0000 http://alcts.ala.org/ccdablog/?p=3029#comment-15018 Or yet another option:

“Regional encoding is a designation for one or more regions of the world for which a videodisc or video game carrier has been formatted, restricting the playback to a device with compatible encoding.”

]]>
Comment on Adding Controlled Vocabulary to RDA 3.19.6, Regional Encoding, and to the Glossary by Kathy Glennan https://alcts.ala.org/ccdablog/?p=3029#comment-15017 Mon, 17 Oct 2016 21:36:57 +0000 http://alcts.ala.org/ccdablog/?p=3029#comment-15017 It might be better to keep this as one sentence:

“Regional encoding is a designation for one or more regions of the world for which a videodisc or video game carrier has been encoded for playback on a device with compatible encoding.”

Wordsmithing suggestions welcomed. (Can we replace one of those “encodings”?)

Maybe: “… encoded for playback on a compatible device.” ??

]]>
https://alcts.ala.org/ccdablog/?feed=comments-rss2
alcts.ala.org
crawl=CC-MAIN-2019-09
8948
application/http; msgtype=response
sha1:EIQKX2Q4XRWNIQO75INPIFINOLCTCN4U
<urn:uuid:8b5f41e2-0f7f-4157-94f3-6b1eac165664>
2019-02-23T05:21:01Z
216.80.72.149
application/rss+xml
sha1:B7MRNEU2HJ2A4NLKYVFM5ERX4ZTVHAA6
<urn:uuid:963bd10d-681d-4fdc-9a36-66651525a867>
https://alcts.ala.org/ccdablog/?feed=comments-rss2
response
<urn:uuid:25356169-b114-4cf8-9fe0-3ce682ef7a0b>
isPartOf: CC-MAIN-2019-09
publisher: Common Crawl
description: Wide crawl of the web for February 2019
operator: Common Crawl Admin (info@commoncrawl.org)
hostname: ip-10-141-110-199.ec2.internal
software: Apache Nutch 1.15 (modified, https://github.com/commoncrawl/nutch/)
robots: checked via crawler-commons 0.11-SNAPSHOT (https://github.com/crawler-commons/crawler-commons)
format: WARC File Format 1.1
conformsTo: http://iipc.github.io/warc-specifications/specifications/warc-format/warc-1.1/