When N-Spec reports claim dependency issues, these typically fall into three specific categories:
1. Self-Referential Dependencies
This occurs when N-Spec detects that a claim appears to depend from itself. For example, if Claim 2 contains language suggesting it depends from Claim 2, N-Spec will flag this as an error since a claim cannot depend from itself.
2. Invalid Claim References
N-Spec will flag two types of invalid claim references:
- Dependencies referencing claims with numbers less than 1
- Dependencies referencing claim numbers higher than the total number of claims in the application
3. Circular Dependencies
N-Spec checks for circular dependency chains where claims form a loop. For example, if Claim 1 depends on Claim 2, while Claim 2 depends on Claim 1, this creates an invalid circular dependency.
Troubleshooting Tips:
- If N-Spec reports unexpected dependency issues, first verify your claims section is properly identified with a standard header (e.g., "CLAIMS:")
- Check that claim numbering is explicit rather than using Word's automatic numbering
- Verify that claim dependencies use standard U.S. patent practice formatting
- Ensure your claims each end with a period, and preferably are separated from each other by one or more blank lines
- Make sure cancelled claims are properly indicated (e.g., "1-7 (Cancelled)"). N-Spec does not use the visible numbers next to claims to count them, but instead relies on the actual presence of claims or cancellation indicators in the document. This means if earlier claims are cancelled but not properly indicated, N-Spec will treat later claims as having lower claim numbers than intended
- Note that N-Spec can handle standard dependencies like "The method of claim 1", multiple explicit dependencies like "The method of claims 1, 2 and 3" or "The method of any of claims 1-4", and several types of implicit dependencies like "The method according to any of the above claims" or "The method of any preceding claim"
Note: When N-Spec detects dependency issues, it may disable certain features like antecedent basis checking and literal support analysis until the dependency issues are resolved.