<?xml version="1.0" encoding="UTF-8"?>
<item xmlns="http://omeka.org/schemas/omeka-xml/v5" itemId="2108" public="1" featured="0" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://omeka.org/schemas/omeka-xml/v5 http://omeka.org/schemas/omeka-xml/v5/omeka-xml-5-0.xsd" uri="https://sleepyhollow.localarchives.org/items/show/2108?output=omeka-xml" accessDate="2026-09-19T09:44:23+00:00">
  <fileContainer>
    <file fileId="2108">
      <src>https://sleepyhollow.localarchives.org/files/original/92af6de5d76b77563bfd1902e4767d37.pdf</src>
      <authentication>3fd720983d1909f243583d800dad362a</authentication>
      <elementSetContainer>
        <elementSet elementSetId="4">
          <name>PDF Text</name>
          <description/>
          <elementContainer>
            <element elementId="52">
              <name>Text</name>
              <description/>
              <elementTextContainer>
                <elementText elementTextId="20595">
                  <text>Chairwoman Santo called the work session to order at 7:00pm
Present:

Lisa Santo, Chairwoman
Hugh Jones
Carl Aridas
Anthony DelVecchio
Isabel Mendez
Ed McCarthy
Sandra Spiro

Also Present:

Sean McCarthy, Village Architect
Clinton Smith, Village Attorney
James Natarelli (Dolph Rotfeld Engineering/Consulting Engineer)
David Smith, Village Planner
Anthony Giaccio, Recording Secretary

Agenda
1) Lighthouse Landing Venture LLC, Edge-on-Hudson - Resolution, 199 Beekman Avenue, phase I
site plan and subdivision
2) Shroba Vincent Living Trust - Preliminary presentation, 81 Sleepy Hollow Road, lot line adjustment

1) Lighthouse Landing Venture LLC, Edge-on-Hudson - Public Hearing, 199 Beekman Avenue, phase
I site plan and subdivision
The applicant is seeking site plan and sub-division approval for phase I of the Edge on Hudson project.
Phase I of the project consists of 306 housing units on approximately 24 acres of property. The Zoning
Board approved a height variance for three buildings. A public hearing was held on September 17, 2015
and closed on October 2, 2015. The applicant attempted to incorporate recommendations made during
the public comment period.
Planning consultant, David Smith started the discussion. Mr. Smith listed all of the proposed conditions
that will be included in the final resolution.
Peter Johnson represented the application and commented on some of the outstanding items. They
included Architectural Review Board approval, incorporating a request from the Environmental Advisory
Committee to have better connectivity and addressing the inflow and infiltration of storm water into the
public sewer system.

��</text>
                </elementText>
              </elementTextContainer>
            </element>
          </elementContainer>
        </elementSet>
      </elementSetContainer>
    </file>
  </fileContainer>
  <collection collectionId="156">
    <elementSetContainer>
      <elementSet elementSetId="1">
        <name>Dublin Core</name>
        <description>The Dublin Core metadata element set is common to all Omeka records, including items, files, and collections. For more information see, http://dublincore.org/documents/dces/.</description>
        <elementContainer>
          <element elementId="50">
            <name>Title</name>
            <description>A name given to the resource</description>
            <elementTextContainer>
              <elementText elementTextId="14859">
                <text>Planning Board Minutes &amp; Resolutions-2015</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
  </collection>
  <itemType itemTypeId="1">
    <name>Text</name>
    <description>A resource consisting primarily of words for reading. Examples include books, letters, dissertations, poems, newspapers, articles, archives of mailing lists. Note that facsimiles or images of texts are still of the genre Text.</description>
  </itemType>
  <elementSetContainer>
    <elementSet elementSetId="1">
      <name>Dublin Core</name>
      <description>The Dublin Core metadata element set is common to all Omeka records, including items, files, and collections. For more information see, http://dublincore.org/documents/dces/.</description>
      <elementContainer>
        <element elementId="50">
          <name>Title</name>
          <description>A name given to the resource</description>
          <elementTextContainer>
            <elementText elementTextId="13059">
              <text>MINS_PLAN_2015-10-08</text>
            </elementText>
          </elementTextContainer>
        </element>
        <element elementId="49">
          <name>Subject</name>
          <description>The topic of the resource</description>
          <elementTextContainer>
            <elementText elementTextId="13060">
              <text>Planning Board Minutes &amp; Resolutions-2015</text>
            </elementText>
          </elementTextContainer>
        </element>
        <element elementId="40">
          <name>Date</name>
          <description>A point or period of time associated with an event in the lifecycle of the resource</description>
          <elementTextContainer>
            <elementText elementTextId="13061">
              <text>2015</text>
            </elementText>
          </elementTextContainer>
        </element>
        <element elementId="47">
          <name>Rights</name>
          <description>Information about rights held in and over the resource</description>
          <elementTextContainer>
            <elementText elementTextId="13062">
              <text>Village of Sleepy Hollow All Rights Reserved.</text>
            </elementText>
          </elementTextContainer>
        </element>
        <element elementId="51">
          <name>Type</name>
          <description>The nature or genre of the resource</description>
          <elementTextContainer>
            <elementText elementTextId="13063">
              <text>Text</text>
            </elementText>
          </elementTextContainer>
        </element>
      </elementContainer>
    </elementSet>
  </elementSetContainer>
</item>
