A little review …

Match up the actions on the left with the correct encoding snippet on the right (hint: sometimes the snippet won’t tell the whole story):

  <moduleRef key="namesdates"/>

  <attDef ident="type" mode="delete"/>

  <classSpec type="atts" ident="att.naming" mode="delete"/>

  <attDef ident="rendition" mode="change"> <!-- ... --> </attDef>

  <elementSpec module="namesdates" ident="addName" mode="delete"/>

Now that we’ve gotten this far, let’s do a quick review of the elements we’ve learned up to this point. Match up the ODD customizations with their corresponding elements, and check your answers against the explanations below.

In order to delete an element for the schema, you would use <elementSpec mode="delete"/>, specifying the module="" and element name (with ident=""). In this case the <addName> element from the namesdates module was deleted. You can also delete elements with the exclude= attribute on <moduleRef />

This next one’s a bit tricky, since we don’t have all of the necessary information. If we wanted to constrain attribute values, we would need to use the <attDef> element. As you can see, there are two possible answers. Now we need to look at the attribute values to give us a hint as to what the element is doing. Specifically, we want to look at the mode= attribute. Since we want to specify values, what we are doing is changing the definition of the attribute. So, in this case, we would use <attDef ident="rendition" mode="change" />.

In order to delete an attribute, we would use the other example of <attDef> - <attDef ident="type" mode="delete" />

In order to include a module in the schema, we would use <moduleRef key="namesdates" /> (with the value of @key being the name of the module we want to include).

In order to delete a whole attribute class, we would use <classSpec type="atts" ident="att.naming" mode="delete" />