andrew2net
commented
4 years ago @ronaldtse we support all of then except CP. I'll add it. POL-NTS is presented in JSON as POLNTS. I've just checked the lastest JSON. There are additional types in it:
"ATB"
"P"
"Praft"
"RP"How should we treat them?
@opoudjis in the ogc.rng we have:
<define name="DocumentType">
<choice>
<value>standard</value>
<value>standard-with-suite</value>
<value>abstract-specification</value>
<value>community-standard</value>
<value>profile</value>
<value>best-practice</value>
<value>engineering-report</value>
<value>discussion-paper</value>
<value>reference-model</value>
<value>user-guide</value>
<value>policy</value>
<value>guide</value>
<value>amendment</value>
<value>technical-corrigendum</value>
<value>administrative</value>
</choice>
</define>shouldn't we fix the list of allowed types?
ronaldtse
opoudjis
@andrew2net can you help confirm that we now support all these document types? Can you add them to documentation? Thanks!
AS => Abstract Specification BP => Best Practice CAN => Candidate Standard CC => Conformance Class CR => Change Request CS => Community Standard CP => Community Practice DP => Discussion Paper DP-Draft => Draft Discussion Paper IPR => Interoperability Program Report-Engineering Specification IS => Implementation Standard ISC => Implementation Standard Corrigendum ISx => Extension Package Standard Notes => Notes ORM => OGC Reference Model PC => Profile Corrigendum PER => Public Engineering Report POL => Policy POL-NTS => Policy - Name Type Specification Primer => Primer Profile => Profile RFC => Request for Comment Retired => Retired document SAP => Standard Application Profile TS => Test Suite WhitePaper => Whitepaper