Update vicav_data_architecture.md

changing `@xml:id` of project member list to "projectTeam" (formerly: "team")
acdh-oeaw · Jan 7, 2025 · efc2348 · efc2348
1 parent f70452e
commit efc2348
Showing 1 changed file with 3 additions and 3 deletions.
diff --git a/docs/vicav_data_architecture.md b/docs/vicav_data_architecture.md
@@ -54,7 +54,7 @@ The main principle of this architecture is that information common to all data i
 
 ### Team Members and their responsibilities
 
-Each team member is represented in the corpus document by a `<person>` element in the **Team Member List** at `/teiCorpus/standOff/listPerson[@type="team"]`. This is the authoratitve place where other documents point to when referencing the person in question and where the application is fetching labels and other metadata for display.
+Each team member is represented in the corpus document by a `<person>` element in the **Team Member List** at `/teiCorpus/standOff/listPerson[@type="projectTeam"]`. This is the authoratitve place where other documents point to when referencing the person in question and where the application is fetching labels and other metadata for display.
 
 The `<person>` element …
 
@@ -73,7 +73,7 @@ Each `<respStmt>` …
 
 ```xml
 <!-- In the Corpus document -->
-<listPerson type="team">
+<listPerson type="projectTeam">
    <head>Team Members</head>
    <person xml:id="VRB">
       <forename>Veronika</forename>
@@ -262,4 +262,4 @@ It may be necessary that a new type of data needs to be defined which can then b
 
 ## How VICAV App uses the data 
 
-**TODO** Add pointers to documentation how the data is processed / consumed by VICAV app both in the backend and frontend.
+**TODO** Add pointers to documentation how the data is processed / consumed by VICAV app both in the backend and frontend.