Changes between Version 36 and Version 37 of PhyloWS_workgroup

Show
Ignore:
Timestamp:
2008/02/13 12:15:58 (11 years ago)
Author:
hlapp
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • PhyloWS_workgroup

    v36 v37  
    6969There are essentially two ways to represent node metadata: 
    7070 * Using a metadata schema (for example, an XML Schema, or a XML document definition, similar to metadata schemas in use in the library sciences such as DC, MARC21, etc). 
    71   * Pros: provides a clear expectation for clients as to what metadata to expect, and the meaning of those elements can be (hard-)coded into applications. 
     71  * Pros: provides a clear expectation for clients as to what metadata to expect, and the meaning of those elements can be (hard-) coded into applications. 
    7272  * Cons: limited to whatever the metadata schema allows for, and any new metadata elements deemed useful by emerging research cannot be readily expressed (and rectifying that requires a metadata schema update, which in turn affects client applications rather directly). In addition, the meaning of metadata elements cannot be dynamically inferred or stated; it is implicit from the XML DTD or Schema definition. 
    7373 * Using attribute/value pairs, where attribute names are drawn from a controlled vocabulary.