Before I dive into ideas for individual components for my social networking concept, I want to look at a generic component. This should give me an idea about how components could be structured. Since this is just a brainstorming project, I will not be concerning myself with the structure's format, syntax, terminology, and other details. This will just be a rough concept.
The primary purpose of this structure will be to show what should be shared between websites. Obviously, websites can manage their own data however they like. If they want to utilize proper cross-site content, however, there would need to embrace some form of standards. Those standards would start with the structure.
Example:
Head
Properties
/Head
Main
Component type
Contents
Properties
/Main
Alt 1
Component type
Contents
Properties
/Alt 1
Now for the explanation. Let's start with the head. The head could contain properties necessary for a component to function properly as well as any properties that a content developer wants to apply regardless of the component's form. In particular, it would likely need to include some form of ID for the content provider. This would probably be a social networking ID, but other forms could be possible. In other words, a news provider could either identify their information by a social networking ID of a reporter, a social networking ID shared by their reporters, or possibly a different ID type to identify the organization.
The Main section would identify what kind of content was created. This would most likely be type found in some form of registry. It would also be possible to create custom types as long as those types are identified as a custom type. A custom type should identify who is responsible for the type. Usually, custom types would remain internal, but there likely would be times in which websites are open to external websites working with their custom content.
Alt sections would be similar to the main. This would allow content to be formatted in multiple ways to allow sites that do not support one form to still accept the content. For example, a weather forecast taking a unique approach could have a Main showing a custom type. Alt 1 could be used for a more standard forecast type. If a website still lacked the tools to display, an image of the forecast could be used as an Alt 2.
Within the registry, there should be defined properties as well as information regarding how content should be stored. In some ways, these could be combined. For example, you could have a property to identify the format of a picture. As with the types, custom properties could be developed as long as they were properly identified as such.
Some properties could be viewed as generic. By that, I mean that they can apply to all content. One example that I have already made was an ID for the creator of the content. Among the most obvious would be tags.
There is a reason that I wanted to bring up tags is because they could be used differently from what we currently see. Yes, this can include standard tags. I will view all standard tags as hashtags since they can be entered as such to indicate the type of tag. There could also be some more advanced forms of tags. These tags could be used to identify more than just a word. It could include a sequence used to better identify the meaning of a word (if a word has multiple meanings). It could also be used to set up more official channels to prevent the use of different tags by different people. Such tags would generally need to identify who is controlling the tag, likely with a reserved symbol. For example, American natural disasters could use FEMA. This could include $FEMA.2019.06.FakeTownEarthquake or $FEMA.2005.Katrina. This could also be used for content generally associated with wikis. This can also enable mixed content between official and user generated tags (if the controlling business or organization supports it). For example: GamePublisher.Game.Character.Schedule
One last thing. With how a lot of tags are inputted, websites could utilize them to create shortcuts. Think of these as macros triggered by a tag. They can be identified by a reserved character. For example, a news item could have the following tags:
- #Breaking
- $FEMA.2019.06.FakeTownEarthquake
- !PromoteThis
Keep in mind that this kind of tag would be used strictly internally. It would not show in the structure that I have discussed. Even so, this seems like a potentially interesting use.
No comments:
Post a Comment