Re: [w3c/FileAPI] Fold File and Directory Entries API into File API (PR #222)

@jcayzac commented on this pull request.



> +A <dfn export id=file-concept>file</dfn> consists of binary data and a <dfn
+for=file>name</dfn> (a non-empty [=/name=]).
+
+A <dfn export>directory</dfn> consists of a <dfn for=directory>name</dfn> (a
+[=/name=]) and an ordered list of members. Each member is either a
+[=file=] or a [=/directory=]. Each member of a [=/directory=] must have
+a distinct non-empty [=/name=].
+
+A <dfn export>root directory</dfn> is a [=/directory=] that is not a member of
+a [=/directory=]. A [=root directory=]'s [=/name=] is empty.
+
+The <dfn export>parent</dfn> of a [=file=] or [=/directory=] is the
+[=/directory=] it is a member of. A [=root directory=] has no
+[=parent=].
+
+Issue: Should [=/directory=] be defined as a special type of [=file=]

@marcoscaceres not yet. Should I move issues currently in the entries-api repo over here, by the way, or should we keep existing ones there and point to them?

-- 
Reply to this email directly or view it on GitHub:
https://github.com/w3c/FileAPI/pull/222#discussion_r3618501474
You are receiving this because you are subscribed to this thread.

Message ID: <w3c/FileAPI/pull/222/review/4740053667@github.com>