On page 2-18 the local interface XMLParser contains two operations with
the same name 'parse'. According to appendix B.6 page B-30 the second
of these operations should instead be called 'parse_custom'.

see above

These are probably editorial and don't deserve full issue
treatment, but since there's no XML/Value FTF, they have to be
archived in the issues database until an FTF is formed and can
deal with them.

In orbos/2000-08-10, Section 7.2.6, page 7-76,

valuetype EmployeeShelf : ...

should be

valuetype Employees : ...

to agree with the DTD example just given. (Or change "Employees" to
"EmployeeShelf" in the DTD.)

(The example on the previous page used "CardShelf" and "Card". This example
uses "Employees" and "Employee". I bet this was set up as
"EmployeeShelf" initially and changed at the last minute, but
not consistently. Maybe someone didn't want to give the impression
that their employees were just sitting on a shelf somewhere

Also, in the third-from-last line of the mapped IDL, the argument
list appears as

(long index)

and should properly be

(in long index).

Correct the interface name (that means, release the poor employees from the shelf…)

Page 2.21 contains the sentence "The DOMStrings for element/attribute
names and values are managed using the flyweight design pattern". This
is inconsistent with the rest of the specification, including IDL,
where only names but not values are optionally managed as flyweights.

see above

Section 2.4.2 on page 2-19 claims that by selecting a particular
implementation of local interface XMLFactory it can 'return a Car
valuetype when an element named "Car" is found in the document'. It is
not at all clear how this can be possible given that the createType
operation only has a 'type' parameter but not an element name
parameter. How does the createType operation discover the element name?

Add a name input argument to the signature of the XMLFactory createType operation.

Hopefully this can be fixed editorially as a typo, but there's no
place to archive it except the issues list until we have an
XML/value FTF. This is an XML/Value issue.

On page 4-42 of orbos/2000-08-10, for const 32,
UNEXPECTED_SQUARE_OPEN is misspelled as
UNEXPETED_SQUARE_OPEN

Apply the typo correction to two places in the IDL

Section 5.2.2 has a copy-and-paste error: Instead of a paragraph about
set<DocumentName>Root(in <DocumentName> docRoot) it duplicates the
get<DocumentName>Root() paragraph.

see above

On page 5-17 the IDL produced by the mapping tool for the example only
includes one parse operation, the one that takes a factory parameter is
not shown. IDL for the factory is missing too.

The missing factory and custom parse method should be added.

Similar to issue 2 above, on page 5-16 the createType operation of
InvoiceFactory does not take a name parameter, hence it is not clear
how it can create different types of element nodes for different
elements. Besides, the createType operation in InvoiceFactory does not
need to be specified because it is inherited from XMLFactory anyway.

see above