-
Look in datatypes page for normatives: Check for that have href="versions.html#std-process", title="Standards Status = Normative" Get the id of the table (greatgrandparent of the element) => output/t1-normativedatatypes.yaml
-
Look in documentation page for normatives: Check for all that have href="versions.html#std-process", title="Normative Content") Get the content of the preceding element => output/t2-normativesindocumentation.yaml
-
Look in resourcelist for normatives: Check for all that have href="versions.html#std-process", title="Normative Content"), Get the text of the parent element - and remove the extra stuff because the s are nested here. => output/t3-normativesinreslist.yaml
-
Put those all together => 1-NormativesInPages.yaml
-
Find the Normative resources: Go through the package JSONs, identify the SDs with Normative status => output/2-normativeSDs.yaml
-
Compare the entries in the two lists (normative SDs and normatives found in docs) and create a new YAML file with three lists: Entries that can be found in both files Entries that can be found in the pages but not in the SDs Entries that can be found in the SDs but not in the pages => output/R3-comparison.yaml
-
Find ValueSets that should not be normative Go through the StructureDefs that have Normative status, For all valueset bindings, get the normative status from the corresponding ValueSet JSON => output/2-Normative_sd_valuesets.yaml
-
List valuesets that need not be normative Go through all the ValueSet JSONs that are Normative (from 1) List those that are not referenced in the normative resources => output/3-unexpected_normative_valuesets.yaml
-
Notifications
You must be signed in to change notification settings - Fork 0
costateixeira/qascripts
Folders and files
Name | Name | Last commit message | Last commit date | |
---|---|---|---|---|
Repository files navigation
About
No description, website, or topics provided.
Resources
Stars
Watchers
Forks
Releases
No releases published
Packages 0
No packages published