unify Feature vs Attribute;

[VladimirAlexiev]

As currently defined, OML has a number of related things that are not defined the same:

• oml:Feature: incoming hasFeature, targetFeature; attributes name, type, description`
• oml:PredictionFeature: incoming hasPredictionFeature; attributes name, type
• oml:defaultTargetAttribute: comma-separated string don't use comma-separated multiple values #13
• oml:ignoreAttribute: strings
• oml:rowIDAttribute: string

Questions:

• Is it Attribute or Feature?
• Why PredictionFeature cannot have a description?
• Isn't PredictionFeature a subset of Feature so shouldn't there be some link between them?

And I have a more in-depth question:

• All these are assumed to be columns in a dataset (I assume name refers to a column)
• But a dataset may include multiple CSVs; if the same col name is used in several tables, how do you distinguish it?
• Shouldn't you link up to CSVW for a more formal description of CSV columns? Eg it has a lot more specific description of col types than your "feature type" codelist
• Furthermore, some datasets are not tabular. Eg can OML describe ML over semantic datasets?