diff --git a/isp/model_generic_signal.go b/isp/model_generic_signal.go
index 21fd8fb..8b66a14 100644
--- a/isp/model_generic_signal.go
+++ b/isp/model_generic_signal.go
@@ -19,7 +19,7 @@ var _ MappedNullable = &GenericSignal{}
 // GenericSignal struct for GenericSignal
 type GenericSignal struct {
 	// Splice duration (ms). If no duration or a duration of 0 then the default duration for the segment type is used.
-	Duration *int32 `json:"duration,omitempty" format:"int32" default:"0" minimum:"1000" doc:"Splice duration (ms). If no duration or a duration of 0 then the default duration for the segment type is used."`
+	Duration *int32 `json:"duration,omitempty" format:"int32" default:"0" doc:"Splice duration (ms). If no duration or a duration of 0 then the default duration for the segment type is used."`
 	// Identifies the active signaling segment. Use the same event_id for both START and END to reference the same segment. When signaling two STARTs with the same event_id, the second one will result in an error (ALREADY_EXISTS). Signaling a second start with a different event_id will end a previous active segment of the same type. After a segment has ended, its event_id can be reused. IDs are namespaced by segment type. E.g. it is allowed to have an active Chapter and an active Program with the same event_id. This field corresponds to SCTE-35 segmentation_event_id and splice_event_id.
 	EventId int32 `json:"event_id" format:"int32" minimum:"0" doc:"Identifies the active signaling segment. Use the same event_id for both START and END to reference the same segment. When signaling two STARTs with the same event_id, the second one will result in an error (ALREADY_EXISTS). Signaling a second start with a different event_id will end a previous active segment of the same type. After a segment has ended, its event_id can be reused. IDs are namespaced by segment type. E.g. it is allowed to have an active Chapter and an active Program with the same event_id. This field corresponds to SCTE-35 segmentation_event_id and splice_event_id."`
 	// The signaling segment type which is going to start/end/etc. This is used to mark programs, chapters, ad insertion points, video slating, etc.
diff --git a/spec/isp.yaml b/spec/isp.yaml
index 06488ee..7d1dd09 100644
--- a/spec/isp.yaml
+++ b/spec/isp.yaml
@@ -3500,7 +3500,6 @@ components:
           format: int32
           default: 0
           example: 30000
-          minimum: 1000
         event_id:
           type: integer
           description: Identifies the active signaling segment. Use the same event_id for both START and END to reference the same segment. When signaling two STARTs with the same event_id, the second one will result in an error (ALREADY_EXISTS). Signaling a second start with a different event_id will end a previous active segment of the same type. After a segment has ended, its event_id can be reused. IDs are namespaced by segment type. E.g. it is allowed to have an active Chapter and an active Program with the same event_id. This field corresponds to SCTE-35 segmentation_event_id and splice_event_id.