<commit_before>There will be one ResourceProperty exposed for ALL services: caGridMetadata (or something similarly named)

The "Service" element is the main entrypoint, which other metadata hangs off of.
Core services (which aren't necessarily Gold compatible, as they don't expose operations 
over caDSR-registered data types) will just not have any Operations defined.  The Operations
will just represent the offical caBIG operations on the service.  All caBIG services will have
some operations that aren't modeled in this metadata (such as ResourceProperty related operations), for core
services, all operations may fall under that category.  This is a generalization of previous  (0.5) analytical
metadata.  Now all services will have ServiceMetadata (0.5 equivalent to commom and analytical metadata).
Specific common service types, such as data or vocabulary serivices, will have additional metadata types
and those will be exposed as separate Resource Properties.


TODO:
====================
- Should we support referencing objects instead of replicating? (such as for UMLClass in input, output, and associations)
  - don't really want to replicate identical object definitions (in XML, as its verbose), but want APIs to be as is (e.g. inputParameter.getUMLClass() -> UMLClass).
  - used to use caDSR public id, and do attribute refID
    - we don't really need the public ID for our use cases and its more work to include it
    - breaks the API (you get an ID, not the object) 


XSD/Bean Generation
====================
UML to XSD:
http://www.xml.com/lpt/a/2001/08/22/uml.html
http://www.xml.com/lpt/a/2001/09/19/uml.html
http://www.xml.com/lpt/a/2001/10/10/uml.html
In EA:
http://www.sparxsystems.com.au/resources/xml_schema_generation.html


To Use Enterprise Architect (preferred)<commit_msg>*** empty log message ***<commit_after>There will be one ResourceProperty exposed for ALL services: caGridMetadata (or something similarly named)

The "Service" element is the main entrypoint, which other metadata hangs off of.
Core services (which aren't necessarily Gold compatible, as they don't expose operations 
over caDSR-registered data types) will just not have any Operations defined.  The Operations
will just represent the offical caBIG operations on the service.  All caBIG services will have
some operations that aren't modeled in this metadata (such as ResourceProperty related operations), for core
services, all operations may fall under that category.  This is a generalization of previous  (0.5) analytical
metadata.  Now all services will have ServiceMetadata (0.5 equivalent to commom and analytical metadata).
Specific common service types, such as data or vocabulary serivices, will have additional metadata types
and those will be exposed as separate Resource Properties.


TODO:
====================
-(DONE) Should we support referencing objects instead of replicating? (such as for UMLClass in input, output, and associations)
  - don't really want to replicate identical object definitions (in XML, as its verbose), but want APIs to be as is (e.g. inputParameter.getUMLClass() -> UMLClass).
  - used to use caDSR public id, and do attribute refID
    - we don't really need the public ID for our use cases and its more work to include it
    - breaks the API (you get an ID, not the object) 


XSD/Bean Generation
====================
UML to XSD:
http://www.xml.com/lpt/a/2001/08/22/uml.html
http://www.xml.com/lpt/a/2001/09/19/uml.html
http://www.xml.com/lpt/a/2001/10/10/uml.html
In EA:
http://www.sparxsystems.com.au/resources/xml_schema_generation.html


To Use Enterprise Architect (preferred)
{'fraction_non_alphanumeric': 0.0881057268722467, 'fraction_numerical': 0.015418502202643172, 'mean_word_length': 4.529680365296803, 'pattern_counts': {'":': 0, '<': 3, '<?xml version=': 0, '>': 5, 'https://': 0, 'lorem ipsum': 0, 'www.': 8, 'xml': 8}, 'pii_count': 0, 'substrings_counts': 0, 'word_list_counts': {'cursed_substrings.json': 0, 'profanity_word_list.json': 0, 'sexual_word_list.json': 0, 'zh_pornsignals.json': 0}}
{'dir': 'git-commits-cleaned', 'id': '3226083', 'n_tokens_mistral': 1028, 'n_tokens_neox': 942, 'n_words': 466}