Hi Yaron and Yury.
I was just about to point that. Moreover, I could, for example, importing
foaf vocabulary to define the user pages, so I could make the wiki articles
available in a more massive way through linked open data, with the export
rdf feature. I believe this can only be done if there's a semantic
realtionship defined. (correct me if im wrong please).
Yury, I meant something like this: let's suppose I have a page, and I can
difference two or more types of contents within it (for example, content
itself, and metadata or something like that). So in every revision, I could
say "this revision was for content only", or "this revision was for
metadata only".
I'll give a check to those links, thanks a lot.
Marcelo.
2013/4/21 Yury Katkov <katkov.ju...@gmail.com>
> To Yaron:
>
> > The whole point of a wiki is to be able to collaboratively create
> content, where it doesn't really matter who added what.
>
> I would say that this is very dogmatic point of view. That's not always
> true. Just to name a few, knowing the authorship can boost the author's
> motivation, it can help you to figure out the one's usefulness and
> reputation. I think that all the wikis presented today disregard the
> question of the authorship not because of the original wiki philosophy but
> because of inertia of thinking.
>
> To Marcelo:
>
> What do you mean by classify the contribution? I've once done a simple
> extension CollaborationDiagram [1] that visualizes the contributions of the
> authors of the wikipage do you want to do anything similar? There was a
> great project of analyzing contributions called WikiTrust: they have
> measured the quality of an edit based on how much time did this edit
> existed without being replaced/roll-backed. They have also measured the
> reputation of the authors of the wikis [2].
>
> Also why do you need the data in semantic format? Maybe it would be easier
> to just count the data in PHP?
>
> [1] http://www.mediawiki.org/wiki/Extension:CollaborationDiagram
> [2] http://www.wikitrust.net/
>
> -----
> Yury Katkov, WikiVote
>
>
>
> On Sun, Apr 21, 2013 at 9:15 PM, Yaron Koren <ya...@wikiworks.com> wrote:
>
>> The more relevant question, to me, is *why* you would want to do any of
>> this. The whole point of a wiki is to be able to collaboratively create
>> content, where it doesn't really matter who added what. So why you need to
>> query on this data?
>>
>>
>> On Sun, Apr 21, 2013 at 1:03 PM, Marcelo Chiaradía <
>> chiaradiamarc...@gmail.com> wrote:
>>
>>> Yeah, I know. I've been checking the Semantic Extra Special Properties
>>> extension, but it only solves half of my problem.
>>>
>>> This is my situation:
>>>
>>> I need to save somehow the author that made a contribution to a page,
>>> and somehow classify it regarding the information modified by him. First I
>>> thought an easy solution including a checkbox in the semantic form for the
>>> classification problem (like "is minor edit"), but it looks a lot more
>>> complex.
>>>
>>> So now Im considering the develop of my own extension to semantify this
>>> information, following the Semantic Extra Special Properties and s13n
>>> approach.
>>>
>>> I guess there's no easier way to do it, rigth?
>>>
>>> Cheers,
>>> Marcelo.
>>>
>>>
>>> 2013/4/21 Yaron Koren <ya...@wikiworks.com>
>>>
>>>> Hi,
>>>>
>>>> This seems like a bad hack. I assume this is part of your effort to
>>>> have the page store the usernames of all its contributors? If so, the
>>>> Semantic Extra Special Properties extension may be the better approach - I
>>>> believe it stores that information using the "Page author" property:
>>>>
>>>>
>>>> https://www.mediawiki.org/wiki/Extension:Semantic_Extra_Special_Properties
>>>>
>>>> -Yaron
>>>>
>>>>
>>>>
>>>> On Sat, Apr 20, 2013 at 3:05 PM, Marcelo Chiaradía <
>>>> chiaradiamarc...@gmail.com> wrote:
>>>>
>>>>> Hi everyone,
>>>>>
>>>>> I have saved an internal object which has several properties:
>>>>>
>>>>> {{#set_internal:isInternalObjectOf
>>>>> |property1=value1
>>>>> |property2=value2
>>>>> |name=object_name
>>>>> }}
>>>>>
>>>>> I have a situation where eventually I need to define a new internal
>>>>> object using the properties of the object saved before as values.
>>>>>
>>>>> The way I found to do this is through semantic queries:
>>>>>
>>>>> {{#set_internal:isInternalObjectOf
>>>>> |property1={{#ask: [[-property1::[[name::object_name]] ]]}}
>>>>> |property2={{#ask: [[-property2::[[name::object_name]] ]]}}
>>>>> }}
>>>>>
>>>>> The sintax may be not quite correct, just to show the idea.
>>>>>
>>>>> The problem with this approach is that for every property, I have to
>>>>> make a new query. Is there some way to do this with only one query?
>>>>>
>>>>> Thanks in advance.
>>>>>
>>>>> Marcelo.
>>>>>
>>>>>
>>>>> ------------------------------------------------------------------------------
>>>>> Precog is a next-generation analytics platform capable of advanced
>>>>> analytics on semi-structured data. The platform includes APIs for
>>>>> building
>>>>> apps and a phenomenal toolset for data science. Developers can use
>>>>> our toolset for easy data analysis & visualization. Get a free account!
>>>>> http://www2.precog.com/precogplatform/slashdotnewsletter
>>>>> _______________________________________________
>>>>> Semediawiki-devel mailing list
>>>>> Semediawiki-devel@lists.sourceforge.net
>>>>> https://lists.sourceforge.net/lists/listinfo/semediawiki-devel
>>>>>
>>>>>
>>>>
>>>>
>>>> --
>>>> WikiWorks · MediaWiki Consulting · http://wikiworks.com
>>>>
>>>
>>>
>>
>>
>> --
>> WikiWorks · MediaWiki Consulting · http://wikiworks.com
>>
>>
>> ------------------------------------------------------------------------------
>> Precog is a next-generation analytics platform capable of advanced
>> analytics on semi-structured data. The platform includes APIs for building
>> apps and a phenomenal toolset for data science. Developers can use
>> our toolset for easy data analysis & visualization. Get a free account!
>> http://www2.precog.com/precogplatform/slashdotnewsletter
>> _______________________________________________
>> Semediawiki-devel mailing list
>> Semediawiki-devel@lists.sourceforge.net
>> https://lists.sourceforge.net/lists/listinfo/semediawiki-devel
>>
>>
>
------------------------------------------------------------------------------
Precog is a next-generation analytics platform capable of advanced
analytics on semi-structured data. The platform includes APIs for building
apps and a phenomenal toolset for data science. Developers can use
our toolset for easy data analysis & visualization. Get a free account!
http://www2.precog.com/precogplatform/slashdotnewsletter
_______________________________________________
Semediawiki-devel mailing list
Semediawiki-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/semediawiki-devel
