Changes between Version 10 and Version 11 of ApertureSimpleDataCrawler

Timestamp:

10/17/05 14:32:21 (19 years ago)

Author:

anonymous

Comment:

--

ApertureSimpleDataCrawler

@@ -75 +75 @@
 In our use case this also facilitates metadata indexing in because currently our !MetadataFetcher (the class transforming the information inside a !DataObject to RDF statements) interprets the document URIs and "reinvents" the folder hierarchy, modeling it as Resources with a partOf relation. This would then no longer be necessary, the Folder instance would already contain all necessary information.
 
-Leo: ok, the idea of having a kind of "Sub-Class" sounds good. I would make ApertureDataObject the parent of ApertureDataFolderObject, so that ApertureDataFolderObject has all properties of DataObject and more.
+Leo: ok, the idea of having a kind of "Sub-Class" sounds good. I would make !ApertureDataObject the parent of !ApertureDataFolderObject, so that !ApertureDataFolderObject has all properties of !DataObject and more.
 
-Chris: I don't think so, as a DataObject also has properties that a Folder does not have. For example, a Folder has no InputStream, no byte size, etc. I think DataSources and Folders are really something different. They surely do share characteristics (they both have a URI and metadata) but this should be expressed by their super type. One should not inherit from the other.
+Chris: I don't think so, as a !DataObject also has properties that a Folder does not have. For example, a Folder has no !InputStream, no byte size, etc. I think !DataSources and Folders are really something different. They surely do share characteristics (they both have a URI and metadata) but this should be expressed by their super type. One should not inherit from the other.