Page 3 of 3 FirstFirst 123
Results 21 to 24 of 24

Thread: AppStream: What Problem Does It Solve?

  1. #21
    Join Date
    Jun 2008
    Location
    San Diego, Ca, USA
    Posts
    13,295
    Blog Entries
    2

    Default Re: AppStream: What Problem Does It Solve?

    Quote Originally Posted by wolfi323 View Post
    ???
    I think you are talking about something completely different...

    The official AppStream specification and documentation (http://www.freedesktop.org/software/appstream/docs/) doesn't mention anything about code-writing or version tracking at all.

    Here's the "Abstract", btw:
    I guess this is an example of seeing the forest for the trees.
    Yes, you can look only at the types of metadata tags that are specified narrowly and might I note that the specifications are intentionally fairly loose, to likely give Users latitude for real world implementation. I don't see anything that would be considered for example "syntax" -- ie. if not constructed in a very strict way, it would be a violation.

    Or, you can look at the "Why?" and "How do we use this stuff?" and "What are people actually doing with it?" of how those metadata tags are used.
    I prefer looking at technology this latter way to understand the <practical use> of the technology rather than only what is in a basic specification.

    TSU

  2. #22

    Default Re: AppStream: What Problem Does It Solve?

    Quote Originally Posted by tsu2 View Post
    I guess this is an example of seeing the forest for the trees.
    Yes, you can look only at the types of metadata tags that are specified narrowly and might I note that the specifications are intentionally fairly loose, to likely give Users latitude for real world implementation. I don't see anything that would be considered for example "syntax" -- ie. if not constructed in a very strict way, it would be a violation.
    And what about this e.g.?
    http://www.freedesktop.org/software/...plication.html

    AppStream is exactly about specifying how to provide the metadata and what metadata to provide. That's the main point.

    Of course you can use a similar syntax (it's just XML anyway) with different tags and metadata for completeley different things, but don't call it AppStream then.

    Or, you can look at the "Why?" and "How do we use this stuff?" and "What are people actually doing with it?" of how those metadata tags are used.
    I prefer looking at technology this latter way to understand the <practical use> of the technology rather than only what is in a basic specification.
    The practical use of this technology (as intended by the designers) is to allow software centers to present more information about applications available for installation to the user.

    But if you wanted to implement such a system you talked of, using AppStream as a base would be plain non-sense IMHO.
    It is intended for something completely different.

    And metadata tags that describe an application on a user level, provide screenshots of it, ... have nothing to do with (and cannot be used for) code-writing and version control, regardless of how you look at it...

  3. #23
    Join Date
    Jun 2008
    Location
    San Diego, Ca, USA
    Posts
    13,295
    Blog Entries
    2

    Default Re: AppStream: What Problem Does It Solve?

    Quote Originally Posted by wolfi323 View Post
    And what about this e.g.?
    http://www.freedesktop.org/software/...plication.html

    AppStream is exactly about specifying how to provide the metadata and what metadata to provide. That's the main point.

    Of course you can use a similar syntax (it's just XML anyway) with different tags and metadata for completeley different things, but don't call it AppStream then.


    The practical use of this technology (as intended by the designers) is to allow software centers to present more information about applications available for installation to the user.

    But if you wanted to implement such a system you talked of, using AppStream as a base would be plain non-sense IMHO.
    It is intended for something completely different.

    And metadata tags that describe an application on a user level, provide screenshots of it, ... have nothing to do with (and cannot be used for) code-writing and version control, regardless of how you look at it...
    I don't know how much value continuing to disagree is,
    But it's pretty simple to do a Google search using "appstream" with optionally any of the products I listed in my earlier post, and then reading how they implemented appstream. Whether you would consider those as unauthorized *******ization of the original intent of the appstream developers is opinion.

    TSU

  4. #24

    Default Re: AppStream: What Problem Does It Solve?

    Quote Originally Posted by tsu2 View Post
    I don't know how much value continuing to disagree is,
    But it's pretty simple to do a Google search using "appstream" with optionally any of the products I listed in my earlier post, and then reading how they implemented appstream. Whether you would consider those as unauthorized *******ization of the original intent of the appstream developers is opinion.
    Can you please provide examples? You never listed any particular "products".
    And I doubt that those "appstream"s you mean have any relation to the "AppStream" this thread is about.

    When I do a google search for "appstream" the only other product that shows up is "Amazon AppStream" which definitely is something completely different...
    And I don't find anything to do with code writing and version control at all.
    Last edited by wolfi323; 15-May-2015 at 07:57.

Page 3 of 3 FirstFirst 123

Tags for this Thread

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •