Ticket #880 (closed task: duplicate)

Opened 14 years ago

Last modified 13 years ago

CSML Read method registry

Reported by: lawrence Owned by: domlowe
Priority: required Milestone: NDG2 Cleanup
Component: CSML Version:
Keywords: Cc: awoolf, lawrence


It seems that it will be quite straightforward to create new CSML read methods, but I don't think they should all end up in the CSML software stack itself. Read methods that end up in the stack should be generic. Arguably even the OCCAM read method shouldn't be part of the stack, and the GRAPE read method definitely should not. So how should we use them?

I think there should be a method which allows one to associate a reading class with the internal read methods.

For example, you could have code that looks like this

class MyReader:
    def __init__(self):
        ''' Stuff'''
    def openFile(self,filename):
        ''' Stuff '''

and use it by having

import MyReader.MyReader
import csml

See also the CSMLReadMethods page for current instructions on how to do this.

Change History

comment:1 Changed 14 years ago by lawrence

  • Cc awoolf, lawrence added

Dom has just pointed out that this might have issues for the schema, there may need to be an entry for a file format *and* an entry for the read method name ... (which could be populated by the read method itself if there were a new method in the required methods).

comment:2 Changed 14 years ago by domlowe

  • Status changed from new to assigned

comment:3 Changed 13 years ago by lawrence

  • Summary changed from [WG] CSML Read method registry to CSML Read method registry

comment:4 Changed 13 years ago by domlowe

  • Status changed from assigned to closed
  • Resolution set to duplicate

Moved to CSML Trac  ticket:5

Note: See TracTickets for help on using tickets.