-
Notifications
You must be signed in to change notification settings - Fork 1
/
test.jade
73 lines (73 loc) · 4.75 KB
/
test.jade
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
html
body
section
h3 Welcome to the RDA Element Vocabularies in GitHub
p
| As of January 2014 the RDA Element Vocabularies are available in published form in the namespace
a(href='http://rdaregistry.info') http://rdaregistry.info
| . This new version of the elements has been
| extensively rearranged and updated to reflect recent decisions by the Joint Steering Committee for the Development
| of RDA (JSC).
p
| The published vocabularies are currently available in several sets which reflect the underlying FRBR conceptual
| model. There is also a version for library and other users who prefer properties not constrained by FRBR. These
| ‘unconstrained’ elements are in a separate set, but they have the same internal relationships as the elements in
| the ‘constrained’ sets. The links to the published element sets below will take you to a page that will provide direct access to various representations of each Element Set. The number of elements in each set is given in brackets.
ul
li
a(href='http://www.rdaregistry.info/Elements/c') Classes
| (8)
li
a(href='http://www.rdaregistry.info/Elements/w') Work properties
| (232)
li
a(href='http://www.rdaregistry.info/Elements/e') Expression properties
| (236)
li
a(href='http://www.rdaregistry.info/Elements/m') Manifestation properties
| (213)
li
a(href='http://www.rdaregistry.info/Elements/i') Item properties
| (54)
li
a(href='http://www.rdaregistry.info/Elements/a') Agent properties
| (226)
li
a(href='http://www.rdaregistry.info/Elements/u') Unconstrained properties
| (698)
p
| The HTML pages for each Element hosted at the Open Metadata Registry, maintain a balance between human-friendly and machine-friendly identifiers, so you will see a mix
| of identifiers with opaque numerics and more human readable labels. Documentation currently in preparation will
| provide more explanation for these decisions and their intended utility. Note that the constrained elements are
| related to their unconstrained versions so that data created in an RDA application can be re-used by a non-RDA
| application.
p
| If you discover a problem with the representations of the vocabularies, or have a question, or even wish to engage in a philosophical or practical discussion, please
a(href='https://github.com/RDARegistry/RDA-Vocabularies/issues') raise an issue!
h5 What’s different from the previous version?
p
| The work on a draft version began in 2008, and since then a significant amount of discussion and learning has
| occurred. The new RDA Vocabularies reflect that understanding.
p
| The draft version of the elements available at
a(href='http://rdvocab.info') http://rdvocab.info
| were never
| officially published, so those elements will be deprecated and users and applications redirected to the current
| official versions at
a(href='http://rdaregistry.info') http://rdaregistry.info
| .
h5 What about the RDA value vocabularies?
p
| The RDA Value Vocabularies agreed by the JSC are published in the original namespace at
a(href='http://rdvocab.info') http://rdvocab.info
| . The JSC has no plans to move them to the new namespace, but
| the situation will be reviewed in due course as part of the ongoing development of RDA documentation for users and
| application developers. Any changes will be carried out with minimum disruption and will not affect the semantics
| of the vocabulary concepts and terms.
h5 Next Steps
p
| The JSC, Metadata Management Associates (MMA), and the American Library Association Publishing division will
| continue to collaborate on extensions and refinements of the RDA element sets and value vocabularies. Some
| additional functionality will be added to the RDA Vocabularies as improvements are made in the OMR software. We
| are always happy to discuss current and future requirements of users or potential users of the vocabularies.
| This is Blog Post #2