8 Jan
2011
8 Jan
'11
6:01 p.m.
On Jan 8, 2011, at 4:07 PM, Thibaut DEVERAUX wrote:
What is "the metadata about the entity
represented by the URL. / not a
visual object" ??
I'll list some:
- content data
- creation date
- last modified date
- tags
- objects
- class
- versions
etc
I think this discussion should be replaced in the
average user persona point
of view.
A document is NOT a page. For example when you the XMLRPC or REST API you don't get a
"page" as a result. A page is a user-oriented representation of a document.
In some cases it makes sense to talk about pages (especially when you refer to HTML
representations of documents), in other cases you should talk about documents.
They're both valid and just don't represent the same thing IMO.
- Can the average user understand what it is ?
- Will understanding what it is change his maneer of using the interface ?
I'm not sure what you are asking. Are you implying that I've said that we
shouldn't use page in user documentation or UI? I've definitely not said this.
All I've said is that I would be -1 to say that we never use document and that we
always use page everywhere since they're not the same thing again. Again in a page
you'll have for ex skin & panels that you have in a document.
Regarding "Document Index" both are valid: "Document Index" or
"Page Index". And I'm fine to use Page Index if that's what we want.
To summarize:
* In most cases when we're doing user documentation we'll refer to pages
* In some cases, when we write developer documentation we'll refer to documents when
we don't mean the page but the document... :)
Thanks
-Vincent
Should this be simplified in the user side ?
Thibaut DEVERAUX
Tel : 06 75 51 20 80
thibaut.deveraux(a)gmail.com
http://www.thib-d.com
Skype : thibaut.deveraux
@ Bricks, design et accompagnement projet
t.deveraux(a)bricks-studio.com
Découvrir Bricks : bricks-studio.com
L'actualité du studio sur notre blog : bricks-it.com
Se renseigner sur le design : design-keys.org
2011/1/8 Vincent Massol <vincent(a)massol.net>
> We've had this discussion in the past (unfortunately I cannot find the mail
> thread again).
>
> AFAIR this was my POV:
> * A page is the whole UI associated with a URL: content + skin + panels +
> etc
> * A document is the metadata about the entity represented by the URL. It's
> a non visual object.
>
> For ex "Document Index" is thus valid if you consider not the visual thing
> but that it's an index about the metadata. "Document Information" is
also
> very valid.
>
> Thanks
> -Vincent
>
> On Jan 7, 2011, at 4:53 PM, Ecaterina Moraru (Valica) wrote:
>
>> Hi,
>>
>> We are using mixed naming when referring to a document/page, not only on
>> different pages, but also in the same context (Rename step for example).
>> There is also an issue referring to this problem
>> XWIKI-5401<http://jira.xwiki.org/jira/browse/XWIKI-5401>and we need to
>> find an answer in order to move forward consistency.
>>
>> So the question is which version we prefer: "Page" or
"Document" ?
>>
>> I'm voting +1 for "Page".
>>
>> "Page" is more used IMO, especially in the
"Space"/"Page" context.
>> "Page" is more general than "Document" and better fitted for
a platform
> that
>> encapsulates all kind of content (not just documents).
>>
>> Please cast your vote.
>> Thanks,
>> Caty