-
Notifications
You must be signed in to change notification settings - Fork 3
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
catgryGrp attributes #21
Comments
These 2 attributes have existed in this format since the beginning.
Retaining this limit disallows the use of 0 | 1. Maybe something for a
future discussion of structural change to Codebook but not for 2.6
I'll add documentation on catgry attribute.
…On Sat, Jul 20, 2024, 10:11 Adrian Dușa ***@***.***> wrote:
Two of this element's attributes, compl and excls are defined as
xs:NMTOKEN, with only two values: true and false.
Many other attributes are defined as xs:boolean, shouldn't these
attributes be the same?
The attribute catgry is listed but no description of it can be found in
the element's documentation, and there are no examples to at least infer
its purpose.
—
Reply to this email directly, view it on GitHub
<#21>, or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAJT47KX3UNLHIAN5XQN2TTZNJ4ZVAVCNFSM6AAAAABLGAKL22VHI2DSMVQWIX3LMV43ASLTON2WKOZSGQZDAOJTHA3TQOA>
.
You are receiving this because you are subscribed to this thread.Message
ID: ***@***.***>
|
Source verification: these attributes were added in the 2.0 version of the DTD and transformed into the schema using a restriction base of NMTOKEN for all internal enumerations. Later additions to the schema brought in the use of xs:boolean. Added documentation on the use of the attributes "catgry" and "catGrp". THIS WILL BE IN NEXT PULL REQUEST FOR JULY 23 |
ISSUE ddialliance#15 If the attribute "agentIdentifier" is used, "typeOfAgentIdentifier" should also be provided. An agent may be an organization or individual. Use "isPersistantIdentifier" (true|false) to indicate if this is intended to be a persistent identifier. Use "agentType" to indicate if the agent is an organization or an individual. Corrected examples to reflect revised attribute names agentIdentifier and typeOfAgentIdentifier contact distrbtr metadataAccs origArch othID ISSUE ddialliance#17 check...add standard documenation Corrected misspelling of typeOfAccess in documentation text dataAccs metadataAccs Updated the documentation of the following typeOfAccess, digitalFingerprintValue, Provide the digital fingerprint in digitalFingerprintValue and identify the algorithm specification used (add version as a separate entry if it is not part of the specification entry). [changed to add proper element/attribute name in quotations] algorithmSpecification, [see digitalFingerprintValue] algorithmVersion, [see digitalFingerprintValue] description, added "" as needed outcome, added "" as needed otherQualityStatement, added "" as needed complianceDescription, added "" as needed ADDED elements and documentation for: typeOfExPostEvaluation typeOfCodingInstruction, typeOfOtherMaterial, typeOfSetAvailability, typeOfDataSrc, typeOfDevelopmentActivity, ISSUE ddialliance#19 In software element CHAGE Software used to produce the work. Supprts TO Software used to produce the work. Supports ISSUE ddialliance#21 Added documenation to catGrp Use the attribute "catgry" (IDREFS type) to provide a space delimited list of the ID of each category in the parent category group. The attribute "catGrp" (IDREFS type) is used to indicate all the subsidiary category groups which nest underneath the current category group. This allows for the encoding of a hierarchical structure of category groups. Do not list the categories contained in a listed "catGrp" within the attribute "catgry". These two IDREFS attributes should list ONLY the direct children of the parent category group. ISSUE ddialliance#23 11 instances CHANGED documenation FROM "an "vocabAgencyName" and "vocabAgencyID" to specify the agency managing" TO "a "vocabAgencyName" to specify the agency managing" in all documentation ISSUE ddialliance#24 Revised documentation to: The focus of this element is on the original archive, differentiating between the designated depository and any locally held copies obtained to support local use. ISSUE ddialliance#25 REMOVED as redundant "An agent may be an organization or individual." holdover from when there was no indictor for individual or ogranization status. ISSUE ddialliance#26 CHANGED documentation on all conceptType or extension base conceptType FROM "The string content of "concept"..." TO "The string content of the element..." ISSUE ddialliance#27 typeOfAccs now has documentation on use and this documentation has been removed from parents metadataAccs and dataAccs
Two of this element's attributes,
compl
andexcls
are defined as xs:NMTOKEN, with only two values: true and false.Many other attributes are defined as xs:boolean, shouldn't these attributes be the same?
The attribute
catgry
is listed but no description of it can be found in the element's documentation, and there are no examples to at least infer its purpose.The text was updated successfully, but these errors were encountered: