Re: Suggestion for Aero-ML

[Bruce Jackson]

At 9:29 PM -0500 9/22/06, Jon S. Berndt wrote:

I believe it would be desirable to have a text field in AERO-ML to specify a
license for the file, and also to have a field for specifying the
sensitivity (secret, classified, proprietary, etc.).

I suppose that the license field could look like this:

license name=GNU GPL/

-or-

license name=GNU GPL
  For more information, see www.gnu.org/gpl
/license

I expect that the sensitivity field would simply be something like:

sensitivity type=proprietary/

-or-

sensitivity type=proprietary
  This file should only be distributed in accordance with company policy
THX1138.
/sensitivity

Comments?

Jon Berndt



Would there be merit to having an optional subelement to sensitivity, 
such as classification?  This would allow, if sensitivity was 
'classified' to indicate the level of classification (confidential, 
secret, top secret) (at least in the US, that's how this works).


-- Bruce

Re: The use of Provenance

[Bruce Jackson]

At 10:13 AM +1000 9/22/06, Brian, Geoff wrote:
Hi all,

We have been having some discussion here about the use of the 
Provenance definition for detailing the source of data used to build 
data sets.


Currently Provenance provides information on the author, function 
creation data, and links to reference and modification definitions. 
We have been pondering what is the best technique for detailing where 
in a reference data may be sourced from (the page/paragraph/figure or 
table of reference documents). One consideration was to include this 
information as a standard XML comment; however, the information would 
then only be available to someone visually reading the dataset file. 
Another consideration was to at add content attribute tags to 
Provenance to allow page number, paragraph  number, figure 
number and  table number, etc to be defined explicitly, although 
this adds many attribute tags over complicates the provenance 
definition. The other option discussed was to included a description 
attribute to store the additional information.


The Provenance definition is only associated with tabular data and 
function tables. We were also thinking that it would be useful to 
associated provenance (optionally) with variableDefs and check data. 
We commonly use VariableDefs  to store constants (wing area, span 
etc) as well as being used for MathML expressions. We can store the 
information on the data source in the description attribute, but 
would prefer to use a technique like the provenance definition as it 
would provide a consistent way of defining source information for all 
data/equations included in a dataset.


I am keen to here others ideas?

Regards
Geoff Brian


Geoff,

I'm at a loss as to how to best proceed. We could make provenance or 
provenanceRef a sub-element of varDef; this would let you write the 
provenance in the file header and then cite it wherever necesssary.


Regarding the need to cite page, number and verse, we should perhaps 
flesh out the reference element to include more complete citation 
information. Since a provenance points to a reference, would this 
suffice?


-- Bruce

RE: Suggestion for Aero-ML

[Jon S. Berndt]

 Would there be merit to having an optional subelement to sensitivity,
 such as classification?  This would allow, if sensitivity was
 'classified' to indicate the level of classification (confidential,
 secret, top secret) (at least in the US, that's how this works).

 -- Bruce

Actually, perhaps classification would be a better element name than
sensitivity. I had thought of sensitivity as serving the purpose you
describe, to cover the level of classification. I prefer simplicity. For
example:

classification type=proprietary/
classification type=top secret/
classification type=public/

Is there a need for more detail?

Jon