Arthit Suriyawongkul

> This is cool, I'll run it on 2.2 later. I think this is taking all the RDF outputs and checking which terms occur (anywhere) in examples? Yes. Since the...

> What do you mean by full form? They should be valid as turtle - except the name spaces which are taken from the csvs. Sorry. I should use another...

I prefer 2.3. No rush since it will take more time to actually have more examples anyway.

The code is updated to cover a case like in #371. This is what it reports from 2.2 draft: ```text ==== Terms used in examples but NOT defined in vocabulary...

I think so. Mind that some of them are false positives, due to limitations of regex matching. For example, "policy:1" is from `odrl:uid ` which I think should be fine.

I can take some of these. Already look at legal-eu:GDPR, pd:Email, and few more at PR #373. The rest looks more complicated.

I will move the unresolved ones to #372 to better track that. Update: Done. All remaining undefined terms are here: https://github.com/w3c/dpv/issues/372#issuecomment-3205734700

The numbering of the script (2xx) is a bit confusing though since there is one part (the check of possible undefined terms in HTML) that should be run after the...

What about - 1xx data retrieval from source - 2xx RDF generation (for machine) - 3xx HTML generation (for human) - 4xx Test - 41x Test retrieved data - 42x...

You're right. Keep it 4xx simple. Thanks.