XML Valuetype Language Mapping Avatar
  1. OMG Specification

XML Valuetype Language Mapping — All Issues

  • Acronym: XML
  • Issues Count: 8
  • Description: All Issues
Open Closed All
All Issues

Issues Descriptions

page 2-18 the local interface XMLParser:

  • Key: XML-3
  • Legacy Issue Number: 4434
  • Status: closed  
  • Source: NetAcquire Corporation ( Joachim Achtzehnter)
  • Summary:

    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'.

  • Reported: XML 1.0b1 — Thu, 26 Jul 2001 04:00 GMT
  • Disposition: Resolved — XML 1.0
  • Disposition Summary:

    see above

  • Updated: Fri, 6 Mar 2015 20:59 GMT

XML/Value editorials

  • Key: XML-2
  • Legacy Issue Number: 4149
  • Status: closed  
  • Source: Object Management Group ( Dr. Jon M. Siegel)
  • Summary:

    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).

  • Reported: XML 1.0b1 — Sat, 13 Jan 2001 05:00 GMT
  • Disposition: Resolved — XML 1.0
  • Disposition Summary:

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

  • Updated: Fri, 6 Mar 2015 20:59 GMT

only names but not values are optionally managed as flyweights.

  • Key: XML-5
  • Legacy Issue Number: 4436
  • Status: closed  
  • Source: NetAcquire Corporation ( Joachim Achtzehnter)
  • Summary:

    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.

  • Reported: XML 1.0b1 — Thu, 26 Jul 2001 04:00 GMT
  • Disposition: Resolved — XML 1.0
  • Disposition Summary:

    see above

  • Updated: Fri, 6 Mar 2015 20:59 GMT

How does the createType operation discover the element name?

  • Key: XML-4
  • Legacy Issue Number: 4435
  • Status: closed  
  • Source: NetAcquire Corporation ( Joachim Achtzehnter)
  • Summary:

    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?

  • Reported: XML 1.0b1 — Thu, 26 Jul 2001 04:00 GMT
  • Disposition: Resolved — XML 1.0
  • Disposition Summary:

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

  • Updated: Fri, 6 Mar 2015 20:59 GMT

Typo in XML/Value

  • Key: XML-1
  • Legacy Issue Number: 4138
  • Status: closed  
  • Source: Object Management Group ( Dr. Jon M. Siegel)
  • Summary:

    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

  • Reported: XML 1.0b1 — Fri, 5 Jan 2001 05:00 GMT
  • Disposition: Resolved — XML 1.0
  • Disposition Summary:

    Apply the typo correction to two places in the IDL

  • Updated: Fri, 6 Mar 2015 20:59 GMT

Section 5.2.2 has a copy-and-paste error

  • Key: XML-6
  • Legacy Issue Number: 4437
  • Status: closed  
  • Source: NetAcquire Corporation ( Joachim Achtzehnter)
  • Summary:

    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.

  • Reported: XML 1.0b1 — Thu, 26 Jul 2001 04:00 GMT
  • Disposition: Resolved — XML 1.0
  • Disposition Summary:

    see above

  • Updated: Fri, 6 Mar 2015 20:59 GMT

page 5-17 the IDL produced by mapping tool only includes one parse operatio

  • Key: XML-8
  • Legacy Issue Number: 4439
  • Status: closed  
  • Source: NetAcquire Corporation ( Joachim Achtzehnter)
  • Summary:

    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.

  • Reported: XML 1.0b1 — Thu, 26 Jul 2001 04:00 GMT
  • Disposition: Resolved — XML 1.0
  • Disposition Summary:

    The missing factory and custom parse method should be added.

  • Updated: Fri, 6 Mar 2015 20:59 GMT

createType operation of InvoiceFactory doesn't take name parameter

  • Key: XML-7
  • Legacy Issue Number: 4438
  • Status: closed  
  • Source: NetAcquire Corporation ( Joachim Achtzehnter)
  • Summary:

    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.

  • Reported: XML 1.0b1 — Thu, 26 Jul 2001 04:00 GMT
  • Disposition: Resolved — XML 1.0
  • Disposition Summary:

    see above

  • Updated: Fri, 6 Mar 2015 20:59 GMT