[wg11] RE: Specification of the AP Binding

[Martin Hardwick]

At 03:21 PM 7/16/2004 -0400, Radack, Gerald wrote:
>Martin:
>
>The header also needs to be specified.  Will there be HEADER and DATA elements?  What will be the name of the top-level element?  Something like "ISO-10303-29"?

Yes we need to discuss the header(s). One of the differences in the XML world
is that the data may be distributed between many files. Therefore, for data
exchange we need to define what files need to be searched for entities.

I would also like to define another kind of header that can be used for
ARM objects (incomplete data sets). The goal is to let users start
building libraries of reusable objects.

I would like to leave this until we have finished discussing the data.


>Also, you should probably define a namespace for the keywords, (ISO-10303-29, HEADER, DATA, EXTERNAL-MAPPING, AGGREGATE, etc.).

We are trying to pick keywords that are EXPRESS keywords so there will be no
scope for conflicts. This is the reason for choosing <AGGREGATE> instead
of the shorter <AGG> and for choosing <NVL> as the null value.

We can put them into a namespace if that is the consensus.


>Should a namespace (generated from the schema name) be used for the entity and attribute names, also?

Schema specific namespaces will get in the way of interoperability between the
AP's and could be hard for the users to remember. I prefer to continue with
the current STEP solution which is for the AIM to register each entity
name so that there will be no conflict or ambiguity.

Opinions?

Martin


>                        Gerry
>
>> 
>> 6. External mapping
>> 
>>    Tagged using the Part 23 name generation algorithm but
>>    with a "-" replacing the "_and_". 
>> 
>>    For example, an AND/OR of foo and bar, is foo_and_bar 
>>    in Part 23 and is foo-bar in the AP Binding
>> 
>>    There is no requirement to generate the external mapping 
>>    names in advance.
>> 
>>    AP developers can use the generated names to make assertions 
>>    about the AND/OR instance in XML Schema at their discretion.
>> 
>>    Early bound implementations can choose to generate the names 
>>    in advance, or process the type using late bound External mapping
>>    software by recognizing the hyphen.
>>  
>>    #28=(LENGTH_UNIT() 
>>    NAMED_UNIT(*) 
>>    SI_UNIT(.MILLI.,.METRE.) 
>>    ); 
>> 
>>    <NAMED_UNIT-SI_UNIT id="id-28" > 
>>       <prefix>milli</prefix> 
>>       <name>metre</name> 
>>    </NAMED_UNIT-SI_UNIT >
>
>Why was LENGTH_UNIT included in the Part 21 but not the XML?
>
>Why not:
>
><EXTERNAL-MAPPING id="id-28">
>  <LENGTH_UNIT/>
>  <NAMED_UNIT/>
>  <SI_UNIT> 
>        <prefix>milli</prefix> 
>        <name>metre</name> 
>  </NAMED_UNIT-SI_UNIT>
><EXTERNAL-MAPPING>
>
>This would be closer to the Part 21, and would be easier to process in XSLt.
> 
>
>> 10. href
>> 
>>    The form of an href is "document#id"
>> 
>>    Document shall be the URL of a file. Id shall be the id of 
>>    an entity instance in that file. Document may be omitted 
>>    if the instance is in the current file.
>> 
>>    The id must be a valid XML NMTOKEN (must begin with a 
>>    a letter)
>> 
>It might be better if the id were mappable to a number, for compatibility with Part 21.
>
>
>!DSPAM:40f82ac9217561907218332!