SVS-PS is incompatible with SVS v3

[yoursunny]

SVS v3 spec suggests:
Data Interest name: /<node-prefix>/<group-prefix>/t=<bootstrap-time>/seq=<seq>

SVS-PS 2025-01-04 spec suggests:
Segment (outer): /<node-prefix>/<sync-prefix>/<seq-num>/v=0/seg=<seg>

Notably, t=<bootstrap-time> is not in SVS-PS naming convention.

I'd suggest changing it to:
Segment (outer): /<node-prefix>/<group-prefix>/t=<bootstrap-time>/seq=<seq>/v=0/seg=<seg>

[yoursunny]

Another incompatibility is in "Name Mapping Delivery Optimization" section:

StateVectorSync/PubSubSpec.md

Lines 95 to 99 in ca2e04c

	### Name Mapping Delivery Optimization
	To optimize the delivery of mapping data, SVS-PS implementations MAY piggyback mapping data in the Sync Interest's `ApplicationParameters`. If present, the mapping data SHOULD be appended as a single block after the StateVector in the `ApplicationParameters`. The mapping data MUST be encoded as a TLV block of type `MappingData` as defined above.
	When this optimization is implemented, Mapping Data SHOULD be inserted in every outgoing Sync Interest sent as a result of new data production. On receiving a Sync Interest, this mapping data can be utilized only after the Interest signature has been validated.

In SVS v3, AppParameters contains Sync Data instead of StateVector, so that "after the StateVector" is no longer a valid anchor.
Placing the MappingData after Sync Data is unsafe because the Sync Interest is unsigned and the signature on the Sync Data cannot protect MappingData.
Hence, the logical resolution is placing MappingData after StateVector inside Sync Data.