EAN-139780328006656   EAN-13 barcode 9780328006656
Product NameReading 2000 Grammar Practice Book Gr 2
CategoryBook / Magazine / Publication
Short DescriptionHeight:0 inches / Length:0 inches / Weight:0 pounds / Width:0 inches
Amazon.comA Buy on Amazon ~ 0328006653
Price New3.00 US Dollars    (curriencies)
Price Used2.09 US Dollars    (curriencies)
Width0.13 inches    (convert)
Height10.8 inches    (convert)
Length8.3 inches    (convert)
Weight4 ounces    (convert)
AuthorScott Foresman
Page Count60
FeaturesGreat product!
Long DescriptionScott Foresman Reading Street - Elementary Reading Comprehension Program 2008(c) is an all-new reading instruction program for Grades PreK-6. Reading Street is designed to help teachers build readers through motivating and engaging literature, scientifically research-based instruction, and a wealth of reliable teaching tools. The reading program takes the guesswork out of differentiating instruction with a strong emphasis on ongoing progress-monitoring and an explicit plan to help with managing small groups of students. In addition, Reading Street prioritizes skill instruction at each grade level, so teachers can be assured they will focus on the right reading skill, at the right time, and for every student.
Similar Items9780153196133: Harcourt Math: Practice Workbook: Grade 2 (National Version)
9780153237171: Harcourt Science, Grade 2, Workbook
9780153131790: Harcourt Science, Grade 2, Workbook
9780328022496: Scott Foresman Reading
9780673596413: Scott Foresman Reading: New Beginnings 2.1
9780673611123: Reading 2000 Practice Book With Selection Tests Grade 2.1
9780673275011: Reading 2000 Practice Book With Selection Tests Grade 2.1
9780673596420: Scott Foresman Reading: My Time To Shine
9780022800352: Mcgraw Hill Science Grade 2
9780673611130: Scott Foresman Reading (Practice Book, 2.2)
View 7 more similar items
Created02-05-2013 6:51:13am
Modified04-30-2020 6:34:21pm
Search Googleby EAN or by Title
Query Time0.0201669

Article of interest

This describes how to use version 3.x of the data feed. Version 2.x of the feed is still supported. Version 1.x of the feed is no longer supported in any way.

IMPORTANT: Starting with version 3.2, we have a new property and a new way of dealing with product images. Read about it here.

Accessing the data requires your account to have an active data feed. This switch can be turned on or off on the data feed page. This is also where you will be able to view your KEYCODE which is required to make calls to the feed.

Main changes from version 2.x to 3.x include (but not limited to)...

Calls to the data feed are made via HTTP GET or HTTP POST requests. There are only a few required parameters when making a call.

Most other parameters are optional and they will alter the way data is returned to you and how your request is processed. You can also pass in your own values that you need carried through. Any parameter that the system doesn't recognize will be returned AS-IS in the status block. This can be handy in situations where you are pulling the data in an asyncronus manor and need extra information passed into your callback routine.

When performing a lookup...

When updating data...

When deleting data...

There are some special "get" operations that need no other parameters. You would not use "find" or "update" when using these. Only use the "keycode", "mode" and "get" for these items. These operations are important because many of our elements are data driven and that data changes over time. We normally don't remove attributes or categories but we do often add to the collection.

The returned data can come back in JSON or XML format. In either case the structure of the data is the same. Because it is easier to read, we will be using XML to demonstrate the layout of the result. Here is the data layout. Notice that this is a complex object and some elements have child elements and some elements may be arrays with repeating content.

The easiest way to get the feel of the data is to make several requests using your web browser and ask for the data in XML format. Although JSON is often easier to work with in code, the XML output is often easier for people to read because of the nice markup tags that wrap around each element and the web browser will usually do a nice job of indenting to make it clear which elements are stored within other elements.